- Cloud Native Development Patterns and Best Practices
- John Gilbert
- 207字
- 2021-06-30 18:43:01
Foundation patterns
These patterns provide the foundation for reactive, asynchronous inter-component communication in cloud-native systems.

Cloud Native Databases Per Component: Leverage one or more fully managed cloud-native databases that are not shared across components and react to emitted events to trigger intra-component processing logic
Event Streaming: Leverage a fully managed streaming service to implement all inter-component communication asynchronously whereby upstream components delegate processing to downstream components by publishing domain events that are consumed downstream
Event Sourcing: Communicate and persist the change in state of domain entities as a series of atomically produced immutable domain events, using Event-First or Database-First techniques, to drive asynchronous inter-component communication and facilitate event processing logic
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
Stream Circuit Breaker: Control the flow of events in stream processors so that failures do not inappropriately disrupt throughput, by delegating the handling of unrecoverable errors through fault events
Trilateral API: Publish multiple interfaces for each component: a synchronous API for processing commands and queries, an asynchronous API for publishing events as the state of the component changes, and/or an asynchronous API for consuming the events emitted by other components
- Hands-On Internet of Things with MQTT
- 輕松學Java
- 數據產品經理:解決方案與案例分析
- 永磁同步電動機變頻調速系統及其控制(第2版)
- Machine Learning with Apache Spark Quick Start Guide
- Machine Learning with the Elastic Stack
- Pentaho Analytics for MongoDB
- Mastering Exploratory Analysis with pandas
- 大數據:引爆新的價值點
- Data Analysis with R(Second Edition)
- 設計模式
- 中老年人學電腦與上網
- 精通ROS機器人編程(原書第2版)
- Mastering SQL Server 2014 Data Mining
- 數據結構與算法(C++語言版)