Chapter 4. Conclusion
To infinity, and beyond!
Buzz Lightyear, Toy Story
In this report we have examined the application of the Reactive principles to tools and services for automating deployment, scaling, and management of containerized microservice applications across a distributed cluster.
We’ve identified important traits that you should look for across the application delivery pipeline. The deployment platform must be designed for distributed operation, and thus, like our own applications, the platform should also be Reactive.
You should seek to avoid introducing strongly consistent data management services into the critical layers of your service orchestration, service lookup, and overall cluster management. Teams need to be able to scale containers horizontally across numerous nodes with agility and confidence. Simply stated, it should be enjoyable to deliver your services to production.
From developer test to production delivery, there should be a simplification of the interfaces and concepts presented to users, developers, and operators alike. We should evaluate the developer library support so that our teams can focus on business problems and not on implementation details such as how to manage peer-node clusters. We need a continuous delivery pipeline to automate the process of deploying in order to enable teams to test and deliver updates quickly and reliably. The selection of standards, such as the OCI container image and runtime, continue to aid in mitigating vendor ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access