learned from building a greenfield project in an enterprise setting • An overview of best practices and tools that we have adopted in the past years • This talk is for you if: ◦ you'd like to be more familiar with building and evolving Node.js services - both from a technical and organizational view, ◦ you'd like to build greenfield projects in the near future using Node.js.
is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over, beginning with a working simple system. John Gall
false expectations / tell the wrong story on the status of the project • as a consequence, it may get incorporated into production systems • providing the functionality is not enough - it must be a viable application Proof of concept (2/2) April, 2017 April, 2018 April, 2016
small pyrotechnic charge in their base. Ignited by the burning powder, the pyrotechnic composition burns very brightly, making the projectile trajectory visible to the naked eye during daylight, and very bright during nighttime. This enables the shooter to make aiming corrections without observing the impact of the rounds fired and without using the sights of the weapon. Tracer code - where does the term come from? April, 2017 April, 2018 April, 2016
the main components built in the early stages of a project will be used in the production environment ◦ gives you an opportunity to test architecture, and an idea how difficult adding new functionality will be • later on, the architecture can be evolved, just like how the tracer bullet might change trajectory • the tracer code approach requires user stories to be in place, it does not allow exploration April, 2017 April, 2018 April, 2016
used by the application before termination like ◦ database connections, ◦ or file descriptors • Terminus ◦ Adds graceful shutdown and Kubernetes readiness / liveness checks for any HTTP applications https://www.npmjs.com/package/@godaddy/terminus
2016 • The need emerged for a CMS-like solution to manage cards • Requirements ◦ Version Card Schemas ◦ Browse all the Card Definitions in the system ◦ Track Card Definition state: has changes but not published; versus content is same as published content
2016 • Stands for Pre-Development Review • They are first and foremost discussions - pull requests where project members collaborate • We use them to ◦ investigate new technologies ◦ compare solutions ◦ in short: to learn.
2017 April, 2018 April, 2016 • Get the same type of data from different downstream services soon became an issue ◦ We had to implement custom logic for each new partner team to collect information (sometimes calling multiple endpoints) • Standardized Entity API ◦ Each partner team has to expose an endpoint that returns data in the same format ◦ Adding new partner teams became a single line of code change
the risk of introducing a new version in production by slowly rolling out the change ◦ Capture & monitor metrics, and rollback if needed ◦ Reduces user impact of changes https://martinfowler.com/bliki/CanaryRelease.html
to be used in automated environments ◦ npm ci can only install entire projects at a time: individual dependencies cannot be added with this command, ◦ npm ci will never write to package.json or any of the package-locks: installs are essentially frozen • as a result, performance is improved, can be 40% faster then npm install or yarn https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable
• Two clients running in OpenStack • Running the OpenVPN Servers in Amazon ECS • CloudWatch is used to monitor if the OpenVPN server is up and running ◦ If not, it triggers a Lambda function which replaces the OpenVPN master with the secondary ◦ The old primary will be recovered by ECS and put back in rotation
and restore your Kubernetes cluster resources and persistent volumes: ◦ Take backups of your cluster and restore in case of loss ◦ Copy cluster resources across cloud providers ◦ Replicate your production environment for development and testing environments https://github.com/heptio/ark
facilitates continuous development for Kubernetes applications ◦ Detect changes in your source code and automatically build/push/deploy ◦ Support for multiple application components. Build and deploy only the pieces of your stack that have changed ◦ Deploy regularly when saving files or run one off deployments using the same configuration April, 2018 April, 2017 April, 2018 April, 2016