Электронная библиотека Финансового университета

     

Детальная информация

Gilbert, John. Cloud Native Development Patterns and Best Practices: Practical architectural patterns for building modern, distributed cloud-native systems. — Birmingham: Packt Publishing, 2018. — 1 online resource (311 pages). — Example â#x80;#x93; order orchestrationÂ. — <URL:http://elib.fa.ru/ebsco/1712734.pdf>.

Дата создания записи: 24.02.2018

Тематика: Cloud computing.; Application program interfaces.; Application software — Development.; Application software — Development.; Cloud computing.; COMPUTERS / Computer Literacy; COMPUTERS / Computer Science; COMPUTERS / Data Processing; COMPUTERS / Hardware / General; COMPUTERS / Information Technology; COMPUTERS / Machine Theory; COMPUTERS / Reference

Коллекции: EBSCO

Разрешенные действия:

Действие 'Прочитать' будет доступно, если вы выполните вход в систему или будете работать с сайтом на компьютере в другой сети Действие 'Загрузить' будет доступно, если вы выполните вход в систему или будете работать с сайтом на компьютере в другой сети

Группа: Анонимные пользователи

Сеть: Интернет

Аннотация

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 continuously deliver innovation with confidence.

Права на использование объекта хранения

Место доступа Группа пользователей Действие
Локальная сеть Финуниверситета Все Прочитать Печать Загрузить
Интернет Читатели Прочитать Печать
-> Интернет Анонимные пользователи

Оглавление

  • 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 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
  • Chapter 3: 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
  • Chapter 4: 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
  • Chapter 5: 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
  • Chapter 6: 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
  • Chapter 7: 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
  • Chapter 8: 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
  • Chapter 9: 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
  • Chapter 10: 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
  • Index

Статистика использования

stat Количество обращений: 0
За последние 30 дней: 0
Подробная статистика