In part one of this series, we started defining the problem we are solving. Essentially, we are trying to leverage Docker and DevOps tools to ensure our decentralized team can release faster and with less centralized synchronisation. Before we dive into software choices, we have to talk about the elephant in the room.
Tl;dr — Load Impact is growing, and one of the challenges with growth is making sure your infrastructure and development cycle mature with that success. This is Part 1 of our series, “The Road to Microservices.” Here’s what we’ll cover:
- Why we decided to make the change to a microservice-oriented approach
- We’re switching to Docker! (Isn’t everyone, at this point?)
- What we expect to get out of these changes
One of our favorite aspects of working in performance and load testing is that we have the privilege of working with great companies across every industry.
Every so often we make contact with a user who’s not only building great products with great success, but someone who really understands the value of DevOps and Continuous Testing.
The past few years have brought exciting developments for DevOps teams with the advent of "containers."
As long as your company is prepared for faster development sprints and a lot of testing, Continuous Delivery can increase product delivery and customer satisfaction.
Performance is paramount in today’s website world. Google has also included Website Performance as another key criteria in the search rank algorithm it uses (source).
Every decision we make regarding our website either affects performance, flexibility, or both.