In the past few years, going cloud native has been a big advantage for many companies. But it's a tough technique to get right, especially for enterprises with critical legacy systems. This book examines effective architecture, design, and cultural patterns to help you migrate to cloud native system
Cloud Native Patterns: Designing change-tolerant software
β Scribed by Cornelia Davis
- Publisher
- Manning Publications Co
- Year
- 2019
- Tongue
- English
- Leaves
- 399
- Edition
- 1
- Category
- Library
No coin nor oath required. For personal study only.
β¦ Synopsis
Summary
Cloud Native Patternsis your guide to developing strong applications that thrive in the dynamic, distributed, virtual world of the cloud. This book presents a mental model for cloud-native applications, along with the patterns, practices, and tooling that set them apart.
About the Technology
Cloud platforms promise the holy grail: near-zero downtime, infinite scalability, short feedback cycles, fault-tolerance, and cost control. But how do you get there? By applying cloudnative designs, developers can build resilient, easily adaptable, web-scale distributed applications that handle massive user traffic and data loads. Learn these fundamental patterns and practices, and you'll be ready to thrive in the dynamic, distributed, virtual world of the cloud.
About the Book
With 25 years of experience under her belt, Cornelia Davis teaches you the practices and patterns that set cloud-native applications apart. With realistic examples and expert advice for working with apps, data, services, routing, and more, she shows you how to design and build software that functions beautifully on modern cloud platforms. As you read, you will start to appreciate that cloud-native computing is more about the how and why rather than the where.
What's inside
β’ The lifecycle of cloud-native apps
β’ Cloud-scale configuration management
β’ Zero downtime upgrades, versioned services, and parallel deploys
β’ Service discovery and dynamic routing
β’ Managing interactions between services, including retries and circuit breakers
About the Reader
Requires basic software design skills and an ability to read Java or a similar language.
About the Author
Cornelia Davis is Vice President of Technology at Pivotal Software. A teacher at heart, she's spent the last 25 years making good software and great software developers.
β¦ Table of Contents
PART 1 - THE CLOUD-NATIVE CONTEXT
1. You keep using that word: Defining "cloud-native"
2. Running cloud-native applications in production
3. The platform for cloud-native software
PART 2 - CLOUD-NATIVE PATTERNS
4. Event-driven microservices: It's not just request/response
5. App redundancy: Scale-out and statelessness
6. Application configuration: Not just environment variables
7. The application lifecycle: Accounting for constant change
8. Accessing apps: Services, routing, and service discovery
9. Interaction redundancy: Retries and other control loops
10. Fronting services: Circuit breakers and API gateways
11. Troubleshooting: Finding the needle in the haystack
12. Cloud-native data: Breaking the data monolith
β¦ Subjects
Cloud Computing; Internet of Things; Web Applications; Logging; Microservices; Redundancy; Design Patterns; Downtime; Troubleshooting; Continuous Delivery; Software Development Life Cycle; Routing
π SIMILAR VOLUMES
The way developers design, build, and run software has changed significantly with the evolution of microservices and containers. These modern architectures use new primitives that require a different set of practices than most developers, tech leads, and architects are accustomed to. With this focus
The way developers design, build, and run software has changed significantly with the evolution of microservices and containers. These modern architectures use new primitives that require a different set of practices than most developers, tech leads, and architects are accustomed to. With this focus
The way developers design, build, and run software has changed significantly with the evolution of microservices and containers. These modern architectures offer new distributed primitives that require a different set of practices than many developers, tech leads, and architects are accustomed to. W
The way developers design, build, and run software has changed significantly with the evolution of microservices and containers. These modern architectures offer new distributed primitives that require a different set of practices than many developers, tech leads, and architects are accustomed to. W
This second edition comes with a dedicated playlist of interactive Katacoda labs mapped to sections of the book. As you read through each chapter, you can practice the concepts covered by referring to the labs playlist or to the links provided at the end of applicable chapters. The way developers