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! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Cloud Native Development Patterns and Best Practices

You're reading from   Cloud Native Development Patterns and Best Practices Practical architectural patterns for building modern, distributed cloud-native systems

Arrow left icon
Product type Paperback
Published in Feb 2018
Publisher Packt
ISBN-13 9781788473927
Length 316 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
 Gilbert Gilbert
Author Profile Icon Gilbert
Gilbert
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Title Page
Dedication
Packt Upsell
Contributors
Preface
1. Understanding Cloud Native Concepts FREE CHAPTER 2. The Anatomy of Cloud Native Systems 3. Foundation Patterns 4. Boundary Patterns 5. Control Patterns 6. Deployment 7. Testing 8. Monitoring 9. Security 10. Value Focused Migration 1. Other Books You May Enjoy Index

Data Lake


Collect, store, and index all events in their raw format in perpetuity with complete fidelity and high durability to support auditing, replay, and analytics.

Context, problem, and forces

In our cloud-native system, we have chosen to leverage value-added cloud services to implement our event streaming and our databases. This empowers self-sufficient, full-stack teams to focus their efforts on the requirements of their components and delegate the complexity of operating these services to the cloud provider. We have also architected a topology of multiple event streams to connector our producer components to our consumer components in a well-reasoned manner, which provides proper bulkheads to ensure that a disruption in one stream does not impact the entire system. One side effect of using a cloud-streaming service is that these services only retain events in the stream for a short period of time, usually one to seven days.

In a reactive, cloud-native system, we are effectively turning...

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 $15.99/month. Cancel anytime
Visually different images