4 options
Architecting cloud native applications : design high-performing and cost-effective applications for the cloud / Kamal Arora [and three others].
- Format:
- Book
- Author/Creator:
- Arora, Kamal, author.
- Language:
- English
- Subjects (All):
- Cloud computing.
- Physical Description:
- 1 online resource (654 pages)
- Edition:
- 1st ed.
- Place of Publication:
- Birmingham ; Mumbai : Packt Publishing, 2019.
- Summary:
- This Learning Path focuses on showing you how to leverage the benefits of the cloud and create applications that are high in performance and availability. It teaches you everything you need to know for designing industry-grade cloud applications and efficiently migrating your business to the cloud.
- Contents:
- Intro
- Title Page
- Copyright and Credits
- Architecting Cloud Native Applications
- About Packt
- Why subscribe?
- Packt.com
- Contributors
- About the authors
- 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
- 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
- Foundation Patterns
- Cloud-Native Databases Per Component
- Context, problem, and forces
- Solution
- Resulting context
- Example - cloud-native database trigger
- Event Streaming
- Example - stream, producer, and consumer
- Event Sourcing
- Event-First Variant
- Database-First Variant
- Example - database-first event sourcing
- Data Lake.
- Context, problem, and forces
- Example - Data Lake consumer component
- Stream Circuit Breaker
- Example - stream processor flow control
- Trilateral API
- Example - asynchronous API documentation
- Example - component anatomy
- Boundary Patterns
- API Gateway
- Example - CRUD service
- Command Query Responsibility Segregation (CQRS)
- Example - inverse oplock
- Example - event sourced join
- Offline-first database
- Example - offline-first counter
- Backend For Frontend
- Example - Author BFF
- Example - Worker BFF
- Example - Customer BFF
- Example - Manager BFF
- External Service Gateway
- Outbound communication
- Inbound communication
- Example - user authentication integration
- Control Patterns
- Event collaboration
- Resulting Context
- Example - order collaboration
- Event orchestration
- Example - order orchestration
- Saga
- Example - order collaboration with compensation
- Example - order orchestration with compensation
- 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
- 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
- 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
- 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
- Cloud Native Application Design
- From monolithic to microservices and everything in between
- System design patterns
- Monolithic
- Client server
- Services
- Service-oriented architectures (SOAs)
- Microservices
- Why services matter
- Containers and serverless
- Containers and orchestration
- Registries
- Orchestration
- Container usage patterns
- Microservices with containers
- Hybrid and migration of application deployment
- Container anti patterns
- Serverless
- Scaling.
- Serverless usage patterns
- Web and backend application processing
- Data and batch processing
- System automation
- Serverless anti patterns and concerns
- Development frameworks and approaches
- How to Choose Technology Stacks
- Cloud technology ecosystems
- Public cloud providers
- Independent software vendor (ISV) and technology partners
- Customer managed products
- Software as a Service
- Consulting partners
- Niche SI partners
- Regional SI partners
- Global SI partners
- Procurement in the cloud
- Cloud marketplaces
- Marketplace and service catalogs
- Cloud marketplace anti-patterns
- Licensing considerations
- Cloud vendor pricing models
- Example - AWS Lambda pricing
- Open source
- Cloud services
- Cloud services - vendor versus self-managed
- Self-managed approach
- Managed cloud services
- Vender lock-in
- Operating systems
- Windows versus Linux
- Do operating systems really matter any longer?
- Optimizing Cost
- Before the cloud
- Cloud cost view
- Cloud economics
- CapEx versus OpEx
- Cost monitoring
- Tagging best practices
- Cost optimization
- Compute optimization
- Storage optimization
- Serverless implications
- Cloud native toolkit
- Cloudability
- AWS Trusted Advisor
- Azure Cost Management
- Scalable and Available
- Introduction to the hyper-scale cloud infrastructure
- Always-on architectures
- Always-on - key architectural elements
- Network redundancy
- Redundant core services
- Infrastructure as Code
- Immutable deployments
- Self-healing infrastructures
- Core tenets
- Service-oriented architectures and microservices
- Cloud-native toolkit
- Simian Army
- Docker
- Kubernetes
- Terraform
- OpenFaaS (Function as a Service)
- Envoy
- Linkerd
- Zipkin
- Ansible
- Apache Mesos
- Saltstack
- Vagrant.
- OpenStack projects
- Amazon Web Services
- AWS' cloud native services (CNMM Axis-1)
- Introduction
- AWS platform - differentiators
- KRADL services
- AWS native security services
- Machine Learning/Artificial Intelligence
- Object storage (S3, Glacier, ecosystem)
- Application centric design (CNMM Axis-2)
- Serverless microservice
- API trigger
- Function
- Service
- Serverless microservice - sample walkthrough
- AWS Lambda function creation and configuration
- Configuring the Amazon API Gateway
- Setting up a Weather Service Account
- Testing the service
- Deploying the API
- Serverless microservice automation using AWS SAM
- SAM YAML template
- API definition Swagger file
- AWS Lambda code
- AWS SAM usage
- Automation in AWS (CNMM Axis-3)
- Infrastructure as code
- CI/CD for applications on Amazon EC2, Amazon Elastic Beanstalk
- CI/CD for serverless applications
- CI/CD for Amazon ECS (Docker containers)
- CI/CD for security services - DevSecOps
- Patterns for moving off monolithic application architectures to AWS native architectures
- Microsoft Azure
- Azure's Cloud Native Services (CNMM Axis-1)
- Microsoft Azure platform - differentiators
- Azure IoT
- Azure Cosmos DB
- Azure machine learning studio
- Visual Studio Team Services
- Office 365
- Application Centric Design (CNMM Axis-2)
- Serverless microservice - walkthrough
- Browser-based testing
- Command-line-based testing
- Automation in Azure (CNMM Axis-3)
- CI/CD for Azure container service (Docker containers)
- Patterns for moving from monolithic application architectures to Azure native architectures
- Google Cloud Platform
- GCP's cloud-native services (CNMM Axis-1)
- Introduction.
- Google Cloud Platform - differentiators.
- Notes:
- Description based on print version record.
- Description based on publisher supplied metadata and other sources.
- ISBN:
- 9781838642396
- 1838642390
- OCLC:
- 1099329440
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.