Cloud Native Development Patterns and Best Practices电子书

Title Page

Copyright and Credits

Cloud Native Development Patterns and Best Practices

Dedication

Packt Upsell

Why subscribe?

PacktPub.com

Contributors

About the author

About the reviewer

Packt is searching for authors like you

Preface

Who this book is for

What this book covers

To get the most out of this book

Download the example code files

Download the color images

Conventions used

Get in touch

Reviews

Understanding Cloud Native Concepts

Establishing the context

Rewiring your software engineering brain

Defining cloud-native

Powered by disposable infrastructure

Composed of bounded, isolated components

Scales globally

Embraces disposable architecture

Leverages value-added cloud services

Welcomes polyglot cloud

Empowers self-sufficient, full-stack teams

Drives cultural change

Summary

The Anatomy of Cloud Native Systems

The cloud is the database

Reactive Manifesto

Turning the database inside out

Bulkheads

Event streaming

Polyglot Persistence

Cloud native database

Cloud native patterns

Foundation patterns

Boundary patterns

Control patterns

Bounded isolated components

Functional boundaries

Bounded context

Component patterns

Data life cycle

Single responsibility

Technical isolation

Regions and availability zones

Components

Data

Accounts

Providers

Summary

Foundation Patterns

Cloud-Native Databases Per Component

Context, problem, and forces

Solution

Resulting context

Example – cloud-native database trigger

Event Streaming

Context, problem, and forces

Solution

Resulting context

Example – stream, producer, and consumer

Event Sourcing

Context, problem, and forces

Solution

Event-First Variant

Database-First Variant

Resulting context

Example – database-first event sourcing

Data Lake

Context, problem, and forces

Solution

Resulting context

Example – Data Lake consumer component

Stream Circuit Breaker

Context, problem, and forces

Solution

Resulting context

Example – stream processor flow control

Trilateral API

Context, problem, and forces

Solution

Resulting context

Example – asynchronous API documentation

Example – component anatomy

Summary

Boundary Patterns

API Gateway

Context, problem, and forces

Solution

Resulting context

Example – CRUD service

Command Query Responsibility Segregation (CQRS)

Context, problem, and forces

Solution

Resulting context

Example – inverse oplock

Example – event sourced join

Offline-first database

Context, problem, and forces

Solution

Resulting context

Example – offline-first counter

Backend For Frontend

Context, problem, and forces

Solution

Resulting context

Example – Author BFF

Example – Worker BFF

Example – Customer BFF

Example – Manager BFF

External Service Gateway

Context, problem, and forces

Solution

Outbound communication

Inbound communication

Resulting context

Example – user authentication integration

Summary

Control Patterns

Event collaboration

Context, problem, and forces

Solution

Resulting context

Example – order collaboration

Event orchestration

Context, problem, and forces

Solution

Resulting context

Example – order orchestration

Saga

Context, problem, and forces

Solution

Resulting context

Example – order collaboration with compensation

Example – order orchestration with compensation

Summary

Deployment

Decoupling deployment from release

Multi-level roadmaps

Release roadmaps

Story mapping

Deployment roadmaps

Task branch workflow

Deployment pipeline

Modern CI/CD

npm

Infrastructure as Code services

Serverless Framework

Zero-downtime deployment

Blue-green deployment

Canary deployment

Multi-regional deployment

Feature flags

Versioning

Synchronous API

Database schema

Asynchronous API

Micro-frontend

Trilateral API per container

Summary

Testing

Shifting testing to the left

Test engineering

Isolated testing

Unit testing

Component testing

Transitive testing

Integration testing

Contract testing

End-to-end testing

Manual testing

Example – end-to-end relay

Submit order leg

Order submitted leg

Summary

Monitoring

Shifting testing to the right

Key performance indicators

Real and synthetic traffic

Real-user monitoring

Synthetic transaction monitoring

Observability

Measurements

Work metrics

Resource metrics

Events

Telemetry

Alerting

Focus on recovery

Performance

Summary

Security

Shared responsibility model

Security by design

Accounts as code

Defense in depth

Edge layer

Component layer

Data layer

Encryption

Data in transit

Data at rest

Envelope encryption

Tokenization

Domain events

Disaster recovery

Application security

Federated identity management

API gateway

JWT assertion and filter patterns

Regulatory compliance

Summary

Value Focused Migration

Risk mitigation

Anti-pattern – Lift and Shift

Anti-pattern - synchronous anti-corruption layer

Strangler pattern

Bi-directional synchronization and latching

Legacy change data capture

Empower self-sufficient, full-stack teams

Evolutionary architecture

Welcome polyglot cloud

Summary

Other Books You May Enjoy

Leave a review - let other readers know what you think