Cargando…

Cloud Native Development Patterns and Best Practices : Practical architectural patterns for building modern, distributed cloud-native systems.

Build systems that leverage the benefits of the cloud faster than ever before with cloud-native development. This book focuses on patterns for building highly scalable cloud-native systems. You will learn how the combination of cloud, reactive principles, devops, and automation enable teams to conti...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Gilbert, John
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Birmingham : Packt Publishing, 2018.
Temas:
Acceso en línea:Texto completo
Tabla de Contenidos:
  • Cover; Title Page; Copyright and Credits; Dedication; Packt Upsell; Contributors; Table of Contents; Preface; Chapter 1: 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; Chapter 2: The Anatomy of Cloud Native Systems; The cloud is the database.
  • Reactive ManifestoTurning 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; Chapter 3: Foundation Patterns; Cloud-Native Databases Per Component; Context, problem, and forces; Solution; Resulting context.
  • Example â#x80;#x93; cloud-native database triggerEvent Streaming; Context, problem, and forces; Solution; Resulting context; Example â#x80;#x93; stream, producer, and consumer; Event Sourcing; Context, problem, and forces; Solution; Event-First Variant; Database-First Variant; Resulting context; Example â#x80;#x93; database-first event sourcing; Data Lake; Context, problem, and forces; Solution; Resulting context; Example â#x80;#x93; Data Lake consumer component; Stream Circuit Breaker; Context, problem, and forces; Solution; Resulting context; Example â#x80;#x93; stream processor flow control; Trilateral API.
  • Context, problem, and forcesSolution; Resulting context; Example â#x80;#x93; asynchronous API documentation; Example â#x80;#x93; component anatomy; Summary; Chapter 4: Boundary Patterns; API Gateway; Context, problem,  and forces; Solution; Resulting context; Example â#x80;#x93; CRUD service; Command Query Responsibility Segregation (CQRS); Context, problem, and forces; Solution; Resulting context; Example â#x80;#x93; inverse oplock; Example â#x80;#x93; event sourced join; Offline-first database; Context, problem, and forces; Solution; Resulting context; Example â#x80;#x93; offline-first counter; Backend For Frontend.
  • Context, problem, and forcesSolution; Resulting context; Example â#x80;#x93; Author BFF; Example â#x80;#x93; Worker BFF; Example â#x80;#x93; Customer BFF; Example â#x80;#x93; Manager BFF; External Service Gateway; Context, problem, and forces; Solution; Outbound communication; Inbound communication; Resulting context; Example â#x80;#x93; user authentication integration; Summary; Chapter 5: Control Patterns; Event collaboration; Context, problem,  and forces; Solution; Resulting context; Example â#x80;#x93; order collaboration; Event orchestration; Context, problem, and forces; Solution; Resulting context.