Chapter 87. Cloud Engineering Is About Culture, Not Containers
Holly Cummins
What makes an application a good cloud application? The 12 factors are a good start, but they address only a small part of the challenges of behaving well in the cloud.
There’s a story in my team of a bank that asked for help to convert an aging COBOL application to cloud native microservices. I imagine that the bank’s goals were to become more modern, more agile, and better meet customer needs—but its release board met only every six months. Another client developed an architecture with 68 microservices, but was a bit uneasy about how they’d interact. To ensure that changes in one microservice couldn’t negatively impact other services, the client designed its CI/CD pipeline to ensure that all 68 services could be deployed in a single atomic step. This allowed them to run a lengthy user acceptance testing (UAT) exercise before doing any releases.
There’s nothing wrong with doing releases this way, and for many years, this kind of release cadence was the norm in our industry. If the 68 microservices were distributed but not decoupled (an easy trap to fall into), releasing them in a block and carefully testing them as a unit might have been a sensible precaution. However, this pattern negates many of the benefits of the cloud.
Let’s step back and consider the (considerable) ...
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