舉報 
會員
Cloud Native Development Patterns and Best Practices
John Gilbert 著
更新時間：2021-06-30 18:43:38
開會員，本書免費讀 >
Thisbookisfordeveloperswhowouldliketoprogressintobuildingcloud-nativesystemsandarekeentolearnthepatternsinvolved.Basicknowledgeofprogrammingandcloudcomputingisrequired.
最新章節(jié)
- Leave a review - let other readers know what you think
- Other Books You May Enjoy
- Summary
- Welcome polyglot cloud
- Evolutionary architecture
- Empower self-sufficient full-stack teams
品牌：中圖公司
上架時間：2021-06-30 18:25:58
出版社：Packt Publishing
本書數(shù)字版權(quán)由中圖公司提供，并由其授權(quán)上海閱文信息技術(shù)有限公司制作發(fā)行
- Leave a review - let other readers know what you think 更新時間：2021-06-30 18:43:38
- Other Books You May Enjoy
- Summary
- Welcome polyglot cloud
- Evolutionary architecture
- Empower self-sufficient full-stack teams
- Legacy change data capture
- Bi-directional synchronization and latching
- Strangler pattern
- Anti-pattern - synchronous anti-corruption layer
- Anti-pattern – Lift and Shift
- Risk mitigation
- Value Focused Migration
- Summary
- Regulatory compliance
- JWT assertion and filter patterns
- API gateway
- Federated identity management
- Application security
- Disaster recovery
- Domain events
- Tokenization
- Envelope encryption
- Data at rest
- Data in transit
- Encryption
- Data layer
- Component layer
- Edge layer
- Defense in depth
- Accounts as code
- Security by design
- Shared responsibility model
- Security
- Summary
- Performance
- Focus on recovery
- Alerting
- Telemetry
- Events
- Resource metrics
- Work metrics
- Measurements
- Observability
- Synthetic transaction monitoring
- Real-user monitoring
- Real and synthetic traffic
- Key performance indicators
- Shifting testing to the right
- Monitoring
- Summary
- Order submitted leg
- Submit order leg
- Example – end-to-end relay
- Manual testing
- End-to-end testing
- Contract testing
- Integration testing
- Transitive testing
- Component testing
- Unit testing
- Isolated testing
- Test engineering
- Shifting testing to the left
- Testing
- Summary
- Trilateral API per container
- Micro-frontend
- Asynchronous API
- Database schema
- Synchronous API
- Versioning
- Feature flags
- Multi-regional deployment
- Canary deployment
- Blue-green deployment
- Zero-downtime deployment
- Serverless Framework
- Infrastructure as Code services
- npm
- Modern CI/CD
- Deployment pipeline
- Task branch workflow
- Deployment roadmaps
- Story mapping
- Release roadmaps
- Multi-level roadmaps
- Decoupling deployment from release
- Deployment
- Summary
- Example – order orchestration with compensation
- Example – order collaboration with compensation
- Resulting context
- Solution
- Context problem and forces
- Saga
- Example – order orchestration
- Resulting context
- Solution
- Context problem and forces
- Event orchestration
- Example – order collaboration
- Resulting context
- Solution
- Context problem and forces
- Event collaboration
- Control Patterns
- Summary
- Example – user authentication integration
- Resulting context
- Inbound communication
- Outbound communication
- Solution
- Context problem and forces
- External Service Gateway
- Example – Manager BFF
- Example – Customer BFF
- Example – Worker BFF
- Example – Author BFF
- Resulting context
- Solution
- Context problem and forces
- Backend For Frontend
- Example – offline-first counter
- Resulting context
- Solution
- Context problem and forces
- Offline-first database
- Example – event sourced join
- Example – inverse oplock
- Resulting context
- Solution
- Context problem and forces
- Command Query Responsibility Segregation (CQRS)
- Example – CRUD service
- Resulting context
- Solution
- Context problem and forces
- API Gateway
- Boundary Patterns
- Summary
- Example – component anatomy
- Example – asynchronous API documentation
- Resulting context
- Solution
- Context problem and forces
- Trilateral API
- Example – stream processor flow control
- Resulting context
- Solution
- Context problem and forces
- Stream Circuit Breaker
- Example – Data Lake consumer component
- Resulting context
- Solution
- Context problem and forces
- Data Lake
- Example – database-first event sourcing
- Resulting context
- Database-First Variant
- Event-First Variant
- Solution
- Context problem and forces
- Event Sourcing
- Example – stream producer and consumer
- Resulting context
- Solution
- Context problem and forces
- Event Streaming
- Example – cloud-native database trigger
- Resulting context
- Solution
- Context problem and forces
- Cloud-Native Databases Per Component
- Foundation Patterns
- Summary
- Providers
- Accounts
- Data
- Components
- Regions and availability zones
- Technical isolation
- Single responsibility
- Data life cycle
- Component patterns
- Bounded context
- Functional boundaries
- Bounded isolated components
- Control patterns
- Boundary patterns
- Foundation patterns
- Cloud native patterns
- Cloud native database
- Polyglot Persistence
- Event streaming
- Bulkheads
- Turning the database inside out
- Reactive Manifesto
- The cloud is the database
- The Anatomy of Cloud Native Systems
- Summary
- Drives cultural change
- Empowers self-sufficient full-stack teams
- Welcomes polyglot cloud
- Leverages value-added cloud services
- Embraces disposable architecture
- Scales globally
- Composed of bounded isolated components
- Powered by disposable infrastructure
- Defining cloud-native
- Rewiring your software engineering brain
- Establishing the context
- Understanding Cloud Native Concepts
- Reviews
- Get in touch
- Conventions used
- Download the color images
- Download the example code files
- To get the most out of this book
- What this book covers
- Who this book is for
- Preface
- Packt is searching for authors like you
- About the reviewer
- About the author
- Contributors
- PacktPub.com
- Why subscribe?
- Packt Upsell
- Dedication
- Title Page
- coverpage
- coverpage
- Title Page
- 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 更新時間：2021-06-30 18:43:38
