Search icon CANCEL
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
Software Architecture Patterns for Serverless Systems

You're reading from   Software Architecture Patterns for Serverless Systems Architecting for innovation with event-driven microservices and micro frontends

Arrow left icon
Product type Paperback
Published in Feb 2024
Publisher Packt
ISBN-13 9781803235448
Length 488 pages
Edition 2nd Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
John Gilbert John Gilbert
Author Profile Icon John Gilbert
John Gilbert
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Architecting for Innovation 2. Defining Boundaries and Letting Go FREE CHAPTER 3. Taming the Presentation Tier 4. Trusting Facts and Eventual Consistency 5. Turning the Cloud into the Database 6. A Best Friend for the Frontend 7. Bridging Intersystem Gaps 8. Reacting to Events with More Events 9. Running in Multiple Regions 10. Securing Autonomous Subsystems in Depth 11. Choreographing Deployment and Delivery 12. Optimizing Observability 13. Don’t Delay, Start Experimenting 14. Other Books You May Enjoy
15. Index

Addressing intersystem differences

In Chapter 7, Bridging Intersystem Gaps, we covered the External Service Gateway (ESG) pattern. We deploy ESG services to multiple regions just like other autonomous services, but with one major difference. ESGs interact with external systems that may have different architectures with different regional approaches. The purpose of an ESG is to encapsulate these differences so that they do not corrupt the rest of the system. However, addressing these differences is a multi-dimensional problem that can make your head spin as you consider the challenges from all angles:

  • There is the perspective from your system and from the external system's.
  • Whether the flow is egress or ingress from your system's perspective.
  • Will your system be using a push or pull technique?
  • Is the regional disruption on your side or their side or both?
  • Is the external system in the same cloud, a different cloud or on-premises?
  • Is its topology primary/secondary or active/active...
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