Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Cloud Native Architectures

You're reading from   Cloud Native Architectures Design high-availability and cost-effective applications for the cloud

Arrow left icon
Product type Paperback
Published in Aug 2018
Publisher Packt
ISBN-13 9781787280540
Length 358 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (4):
Arrow left icon
Tom Laszewski Tom Laszewski
Author Profile Icon Tom Laszewski
Tom Laszewski
Kamal Arora Kamal Arora
Author Profile Icon Kamal Arora
Kamal Arora
Piyum Zonooz Piyum Zonooz
Author Profile Icon Piyum Zonooz
Piyum Zonooz
Erik Farr Erik Farr
Author Profile Icon Erik Farr
Erik Farr
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Introducing Cloud Native Architecture FREE CHAPTER 2. The Cloud Adoption Journey 3. Cloud Native Application Design 4. How to Choose Technology Stacks 5. Scalable and Available 6. Secure and Reliable 7. Optimizing Cost 8. Cloud Native Operations 9. Amazon Web Services 10. Microsoft Azure 11. Google Cloud Platform 12. What's Next? Cloud Native Application Architecture Trends 13. Other Books You May Enjoy

Two-pizza teams


The fundamental issue with large organizations is consensus-building. Consensus is needed to move forward on most projects due to the interdependent nature of how we build our technology systems. Since systems are typically large and span multiple teams, once one team makes changes to their part of the system, it may have upstream and downstream effects that they did not anticipate (on subsystems owned and maintained by other teams). The following are some examples:

  • Upstream effect: The updated subsystem now operates so quickly that it is straining the data feed with pulls for new data
  • Downstream effect: The updated subsystem is generating data much more quickly which is overwhelming the ability of the downstream consumer to process the feed

With the broad adoption of decoupled systems and SOAs, we solve this from a technology aspect, but the organization has yet to adapt to this new reality. If we have decoupled systems, why not decoupled organizational units? Enter the two...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime