Conclusion
In this book, we have shown how to architect and design applications that run well on the cloud and how to modernize an existing application as part of migrating it to the cloud. Applying the patterns in this book produces applications that work with the qualities of cloud computing such as universal access, shared resources, distributed computing, virtualized computing, elastic computing, multitenancy, self-service, API driven, and multicloud. Let’s review what we’ve learned, how to apply these patterns, and what comes next.
What We’ve Learned
Cloud computing works differently than traditional IT. Applications for the cloud need an architecture and design better suited for cloud computing, requiring application developers to adopt a mindset embodying a new set of practices. Our patterns have demonstrated these practices.
Applications that incorporate these patterns compensate for and take advantage of the characteristics that cloud computing embodies. These characteristics include unreliable infrastructure, eventual consistency, generic hardware, application mobility, multitenancy, horizontal scaling, statelessness, immutability, componentization, service catalogs, cloud databases, and self-provisioning. Given these characteristics, there is no one right way to architect Cloud Applications (Chapter 1); rather, there are numerous decisions that can help make an application work better or worse in the cloud.
The patterns help you with the decisions that make your applications ...
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