Brian Renzenbrink

We're really, really happy with how we're doing local development with docker-compose on the microservices in the one of our internal teams. We're utilizing docker-compose and relying on working with our existing build pipelines to create an easy way to do local development. The goal is to be able to write code on a train, in a tunnel, and on a new laptop. We're not all the way there but we're moving in the right direction. Here's a blog post about a novel, but an important part of why local development is so seamless for us.

At Compass, we’re big proponents of using NPM and semver (semantic versioning) when distributing our shared components as packages. NPM provides us with an industry-standard platform to publish our internal dependencies. The tools and technologies someone learns while working on a package at Compass are the same ones they’ll use in projects in the open source community. Meanwhile, semantic versioning itself plays a huge role in providing peace of mind. Users of shared components know when updates are safe enough to upgrade to, and component authors can make big updates without the fear of silently breaking the contracts they’ve made with their users. We wanted to build out a way to provide these same benefits to more than just JS libraries, and we ended up creating a lightning-fast form of semantic versioning for our CSS implementation that utilized Lambda@Edge, NPM, and some clever work by our engineers.

AWS Lambda Amazon CloudFront npm #lambdaatedge #semver #serverless