最新章節(jié)
- Summary
- Microservices development governance reference architectures and libraries
- Configuration management
- Monitoring and feedback
- Deployment
- Antifragility testing
品牌：中圖公司
上架時(shí)間：2021-07-02 18:25:03
出版社：Packt Publishing
本書數(shù)字版權(quán)由中圖公司提供，并由其授權(quán)上海閱文信息技術(shù)有限公司制作發(fā)行
- Summary 更新時(shí)間：2021-07-02 19:46:00
- Microservices development governance reference architectures and libraries
- Configuration management
- Monitoring and feedback
- Deployment
- Antifragility testing
- Testing in production (TiP)
- Other non-functional tests
- A/B testing Canary testing and blue-green deployments
- Exploratory testing
- Security testing
- Real user flow simulation or Journey testing
- Performance testing
- Acceptance testing
- Functional testing
- Regression testing
- Sanity tests
- Testing
- Integration
- Development
- Automating development cycle
- Continuous monitoring and feedback
- Value driven planning
- DevOps as a life cycle process
- Building a microservices ecosystem
- Building the self-service cloud
- Establishing self-organizing teams
- Overcoming the legacy hotspot
- Using the concept of minimum viable product (MVP)
- Choosing the right development philosophy
- Change the mindset from project to product development
- Understanding business motivation and value
- Practice points for microservice development
- Microservice Development Life Cycle
- Summary
- Deploying BrownField PSS services
- Preparing BrownField PSS services
- Running Mesos and Marathon
- Installing Mesos Marathon and related components
- Implementing Mesos and Marathon for BrownField microservices
- Implementing Mesos and Marathon with DCOS
- Marathon
- Mesos architecture
- Mesos in details
- Container orchestration with Mesos and Marathon
- CoreOS Fleet
- HashiCorp Nomad
- Apache Mesos
- Kubernetes
- Docker Swarm
- Container orchestration solutions
- Relationship with virtualization
- Relationship with microservices
- What does container orchestration do?
- Why is container orchestration is important
- Container orchestration
- The missing pieces
- Understanding autoscaling
- Scaling microservices
- Scaling Dockerized Microservices with Mesos and Marathon
- Summary
- Future of containerization
- Running BrownField services on EC2
- Installing Docker on AWS EC2
- Microservices on Cloud
- Publish microservices to the Docker Hub
- Setting up the Docker Hub
- Using the Docker registry
- Running RabbitMQ on Docker
- Deploying microservices into Docker
- Dockerfile
- The Docker registry
- The Docker container
- The Docker image
- The Docker client
- The Docker daemon
- Key components of Docker
- Introduction to Docker
- Microservices and containers
- Benefits of containers
- Difference between VM and containers
- What are containers?
- Understanding gaps in the BrownField PSS microservices
- Containerizing Microservices with Docker
- Summary
- Data analysis using Data Lake
- Aggregate Hystrix streams with Turbine
- Spring Cloud Hystrix for fault-tolerant microservices
- Monitoring microservice dependency
- Monitoring tools
- Monitoring challenges
- Monitoring microservices
- Distributed tracing with Spring Cloud Sleuth
- Custom logging implementation
- Dashboards
- Log storage
- Log stream processors
- Log shippers
- Best of the breed integration
- Off-the-shelf solutions
- Cloud services
- Selection of logging solutions
- Centralized logging solution
- Understanding log management challenges
- Logging and Monitoring Microservices
- Summary
- Summarising the BrownField PSS architecture
- Protecting microservices with Spring Cloud Security
- Streams for reactive microservices
- Completing Zuul for all other services
- High availability when client is not a Eureka Client
- High availability of Zuul when the client is also a Eureka Client
- High availability of Zuul
- Setting up Zuul
- Zuul proxy as the API Gateway
- High availability for Eureka
- Setting up the Eureka Server
- Understanding Eureka
- Understanding dynamic service registration and discovery
- Eureka for registration and discovery
- Completing changes to use Config Server
- Config Server for configuration files
- Monitoring Config Server health
- Setting up high availability for the Config Server
- Spring Cloud Bus for propagating configuration changes
- Handling configuration changes
- Accessing the Config Server from clients
- Understanding the Config Server URL
- Setting up the Config Server
- Building microservices with Config Server
- Spring Cloud Config
- Setting up the environment for the BrownField PSS
- Spring Cloud releases
- What is Spring Cloud?
- Scale Microservices with Spring Cloud Components
- Summary
- Potential next steps
- Running and testing the project
- Implementation projects
- Target implementation
- Handling exceptions
- Managing shared libraries
- Integration with other systems
- Orchestrating microservices
- Internal layering of microservices
- Migrate modules only if required
- Building ecosystem capabilities
- Test strategy
- Session handling and security
- User interfaces and web applications
- Managing reference data
- Data synchronization during migration
- Prioritizing microservices for migration
- Final dependency graph
- Challenge service boundaries
- Challenge requirements
- Events as opposed to synchronous updates
- Events as opposed to query
- Analyze dependencies
- Identification of microservices' boundaries
- Migration approach
- The business case
- Microservices to the rescue - a planned approach for migration
- Compromised on domain boundaries
- Stored procedures
- Native queries
- Single monolithic database
- Precedence on data sharing over modularity
- Retrospection
- Stopgap fix
- Pain points
- Death of the monolith
- Deployment view
- Implementation view
- Design view
- Architecture view
- Functional view
- Business process view
- Understanding the PSS application
- Microservices Evolution – A Case Study
- Summary
- Entry points for adoption
- Level 3 - Advanced
- Level 2 - Intermediate
- Level 1 - Basic
- Level 0 - Traditional
- Microservices maturity model
- Reference architecture and libraries
- Microservice documentation
- Container registry
- Automation tools
- DevOps
- Process and governance capabilities
- Reliable messaging
- Data lake
- Dependency management
- Ops monitoring
- Service configuration
- Security service
- Service discovery
- Central log management
- Software-defined load balancer
- Service gateway
- Supporting capabilities
- Container orchestration
- Container runtime
- Cloud
- Infrastructure capabilities
- Service endpoint
- Service implementation
- Storage capability
- Service listeners and libraries
- Core capabilities
- Microservices capability model
- Microservices Capability Model
- Summary
- Microservices and bulk operations
- Handling shared reference data
- Design for cross origin
- Service versioning considerations
- Use of ESB and iPaaS with microservices
- Use of API gateways in microservices
- User interfaces in microservices
- Handling shared libraries
- API documentations
- Optimized Communication Protocols
- HTTP and REST endpoints
- Message oriented services
- Protocol selection
- Contract design
- Service endpoint design consideration
- Distributed transaction scenarios
- Altering use cases to simplify transactional requirements
- Deciding transaction boundaries
- Can microservices be headless?
- Can microservices share a data store?
- Role of BPM and workflows
- Rules engine - shared or embedded?
- How many microservices per VM - one or multiple?
- How many endpoints - one or many?
- Orchestration of microservices
- How to decide which style to choose?
- Asynchronous style communication
- Synchronous style communication
- Designing communication styles
- Think of the microservice as a product
- Coupling and cohesion
- Replicability or changeability
- Single responsibility
- Agile teams and co-development
- Selective scaling
- Polyglot architecture
- Most appropriate function or sub-domain
- Size of the deployable unit
- Autonomous functions
- Deciding microservice boundaries
- Microservice design guidelines
- Applying Microservices Concepts
- Summary
- Putting it all together - Developing a customer registration microservice example
- Documenting microservices
- Building custom metrics
- Adding a custom health module
- Monitoring using ssh
- Monitoring using JConsole
- Spring Boot actuators for microservices instrumentation
- Enabling cross origin for microservices interactions
- Securing microservice with OAuth2
- Securing a microservice with basic security
- Implementing security
- Reactive microservices using Spring Boot and RabbitMQ
- Processor
- Subscription
- Subscriber
- Publisher
- Understanding Reactive Streams
- Reactive microservices using Spring WebFlux
- Reactive Spring Boot microservices
- HATEOAS-enabled Spring Boot microservice
- Testing Spring Boot microservice
- Developing our first Spring Boot microservice
- Developing a Spring Boot microservice
- Getting started with Spring Boot
- Spring Boot for building RESTful microservices
- Setting up a development environment
- Building Microservices with Spring Boot
- Summary
- Microservice frameworks
- Monolithic migration as the common use case
- Microservices early adopters - Is there a common theme?
- Microservice use cases
- A reactive microservice-based order management system
- Reactive microservices
- Cloud and Containers as the self-service infrastructure for microservices
- DevOps as the practice and process for microservices
- DevOps Cloud and Containers
- Lambda architecture
- Serverless computing
- Package admin processes
- Externalizing logs
- Development production parity
- Disposability with minimal overhead
- Concurrency for scale out
- Expose services through port bindings
- Stateless shared nothing processes
- Isolation between build release and run
- Backing services are addressable
- Externalizing configurations
- Bundle dependencies
- Single code base
- Twelve-Factor Apps
- Monolithic migration using SOA
- Service-oriented application
- Legacy modernization
- Service-oriented integration
- Service-Oriented Architecture (SOA)
- Related Architecture Styles and Use Cases
- Summary
- Enables DevOps
- Supporting event-driven architecture
- Supporting building self-organizing systems
- Allowing co-existence of different versions
- Helps managing technology debt
- Enables to build organic systems
- Allows substitution
- Elastically and selectively scalable
- Enables experimentation and innovation
- Supports polyglot architecture
- Microservices benefits
- An example of a travel agent portal
- An example of a holiday portal
- Microservices examples
- Antifragility fail fast and self healing
- Microservices are distributed and dynamic
- Microservices with a supporting ecosystem
- Automation in microservices environment
- Microservices with polyglot architecture
- Microservices are lightweight
- Characteristics of service in a microservice
- Services are first class citizens
- Characteristics of microservices
- Microservices are autonomous
- Single responsibility per service
- Principles of microservices
- Microservices - The honeycomb analogy
- What are Microservices?
- Imperative architecture evolution
- Technology as a catalyst for microservices evolution
- Business demand as a catalyst for microservices evolution
- Evolution of microservices
- Demystifying Microservices
- Questions
- Piracy
- Errata
- Downloading the color images of this book
- Downloading the example code
- Customer support
- Reader feedback
- Conventions
- Who this book is for
- What you need for this book
- What this book covers
- Preface
- Customer Feedback
- Why subscribe?
- www.PacktPub.com
- About the Reviewer
- Acknowledgments
- About the Author
- Credits
- Title Page
- coverpage
- coverpage
- Title Page
- Credits
- About the Author
- Acknowledgments
- About the Reviewer
- www.PacktPub.com
- Why subscribe?
- Customer Feedback
- Preface
- What this book covers
- What you need for this book
- Who this book is for
- Conventions
- Reader feedback
- Customer support
- Downloading the example code
- Downloading the color images of this book
- Errata
- Piracy
- Questions
- Demystifying Microservices
- Evolution of microservices
- Business demand as a catalyst for microservices evolution
- Technology as a catalyst for microservices evolution
- Imperative architecture evolution
- What are Microservices?
- Microservices - The honeycomb analogy
- Principles of microservices
- Single responsibility per service
- Microservices are autonomous
- Characteristics of microservices
- Services are first class citizens
- Characteristics of service in a microservice
- Microservices are lightweight
- Microservices with polyglot architecture
- Automation in microservices environment
- Microservices with a supporting ecosystem
- Microservices are distributed and dynamic
- Antifragility fail fast and self healing
- Microservices examples
- An example of a holiday portal
- An example of a travel agent portal
- Microservices benefits
- Supports polyglot architecture
- Enables experimentation and innovation
- Elastically and selectively scalable
- Allows substitution
- Enables to build organic systems
- Helps managing technology debt
- Allowing co-existence of different versions
- Supporting building self-organizing systems
- Supporting event-driven architecture
- Enables DevOps
- Summary
- Related Architecture Styles and Use Cases
- Service-Oriented Architecture (SOA)
- Service-oriented integration
- Legacy modernization
- Service-oriented application
- Monolithic migration using SOA
- Twelve-Factor Apps
- Single code base
- Bundle dependencies
- Externalizing configurations
- Backing services are addressable
- Isolation between build release and run
- Stateless shared nothing processes
- Expose services through port bindings
- Concurrency for scale out
- Disposability with minimal overhead
- Development production parity
- Externalizing logs
- Package admin processes
- Serverless computing
- Lambda architecture
- DevOps Cloud and Containers
- DevOps as the practice and process for microservices
- Cloud and Containers as the self-service infrastructure for microservices
- Reactive microservices
- A reactive microservice-based order management system
- Microservice use cases
- Microservices early adopters - Is there a common theme?
- Monolithic migration as the common use case
- Microservice frameworks
- Summary
- Building Microservices with Spring Boot
- Setting up a development environment
- Spring Boot for building RESTful microservices
- Getting started with Spring Boot
- Developing a Spring Boot microservice
- Developing our first Spring Boot microservice
- Testing Spring Boot microservice
- HATEOAS-enabled Spring Boot microservice
- Reactive Spring Boot microservices
- Reactive microservices using Spring WebFlux
- Understanding Reactive Streams
- Publisher
- Subscriber
- Subscription
- Processor
- Reactive microservices using Spring Boot and RabbitMQ
- Implementing security
- Securing a microservice with basic security
- Securing microservice with OAuth2
- Enabling cross origin for microservices interactions
- Spring Boot actuators for microservices instrumentation
- Monitoring using JConsole
- Monitoring using ssh
- Adding a custom health module
- Building custom metrics
- Documenting microservices
- Putting it all together - Developing a customer registration microservice example
- Summary
- Applying Microservices Concepts
- Microservice design guidelines
- Deciding microservice boundaries
- Autonomous functions
- Size of the deployable unit
- Most appropriate function or sub-domain
- Polyglot architecture
- Selective scaling
- Agile teams and co-development
- Single responsibility
- Replicability or changeability
- Coupling and cohesion
- Think of the microservice as a product
- Designing communication styles
- Synchronous style communication
- Asynchronous style communication
- How to decide which style to choose?
- Orchestration of microservices
- How many endpoints - one or many?
- How many microservices per VM - one or multiple?
- Rules engine - shared or embedded?
- Role of BPM and workflows
- Can microservices share a data store?
- Can microservices be headless?
- Deciding transaction boundaries
- Altering use cases to simplify transactional requirements
- Distributed transaction scenarios
- Service endpoint design consideration
- Contract design
- Protocol selection
- Message oriented services
- HTTP and REST endpoints
- Optimized Communication Protocols
- API documentations
- Handling shared libraries
- User interfaces in microservices
- Use of API gateways in microservices
- Use of ESB and iPaaS with microservices
- Service versioning considerations
- Design for cross origin
- Handling shared reference data
- Microservices and bulk operations
- Summary
- Microservices Capability Model
- Microservices capability model
- Core capabilities
- Service listeners and libraries
- Storage capability
- Service implementation
- Service endpoint
- Infrastructure capabilities
- Cloud
- Container runtime
- Container orchestration
- Supporting capabilities
- Service gateway
- Software-defined load balancer
- Central log management
- Service discovery
- Security service
- Service configuration
- Ops monitoring
- Dependency management
- Data lake
- Reliable messaging
- Process and governance capabilities
- DevOps
- Automation tools
- Container registry
- Microservice documentation
- Reference architecture and libraries
- Microservices maturity model
- Level 0 - Traditional
- Level 1 - Basic
- Level 2 - Intermediate
- Level 3 - Advanced
- Entry points for adoption
- Summary
- Microservices Evolution – A Case Study
- Understanding the PSS application
- Business process view
- Functional view
- Architecture view
- Design view
- Implementation view
- Deployment view
- Death of the monolith
- Pain points
- Stopgap fix
- Retrospection
- Precedence on data sharing over modularity
- Single monolithic database
- Native queries
- Stored procedures
- Compromised on domain boundaries
- Microservices to the rescue - a planned approach for migration
- The business case
- Migration approach
- Identification of microservices' boundaries
- Analyze dependencies
- Events as opposed to query
- Events as opposed to synchronous updates
- Challenge requirements
- Challenge service boundaries
- Final dependency graph
- Prioritizing microservices for migration
- Data synchronization during migration
- Managing reference data
- User interfaces and web applications
- Session handling and security
- Test strategy
- Building ecosystem capabilities
- Migrate modules only if required
- Internal layering of microservices
- Orchestrating microservices
- Integration with other systems
- Managing shared libraries
- Handling exceptions
- Target implementation
- Implementation projects
- Running and testing the project
- Potential next steps
- Summary
- Scale Microservices with Spring Cloud Components
- What is Spring Cloud?
- Spring Cloud releases
- Setting up the environment for the BrownField PSS
- Spring Cloud Config
- Building microservices with Config Server
- Setting up the Config Server
- Understanding the Config Server URL
- Accessing the Config Server from clients
- Handling configuration changes
- Spring Cloud Bus for propagating configuration changes
- Setting up high availability for the Config Server
- Monitoring Config Server health
- Config Server for configuration files
- Completing changes to use Config Server
- Eureka for registration and discovery
- Understanding dynamic service registration and discovery
- Understanding Eureka
- Setting up the Eureka Server
- High availability for Eureka
- Zuul proxy as the API Gateway
- Setting up Zuul
- High availability of Zuul
- High availability of Zuul when the client is also a Eureka Client
- High availability when client is not a Eureka Client
- Completing Zuul for all other services
- Streams for reactive microservices
- Protecting microservices with Spring Cloud Security
- Summarising the BrownField PSS architecture
- Summary
- Logging and Monitoring Microservices
- Understanding log management challenges
- Centralized logging solution
- Selection of logging solutions
- Cloud services
- Off-the-shelf solutions
- Best of the breed integration
- Log shippers
- Log stream processors
- Log storage
- Dashboards
- Custom logging implementation
- Distributed tracing with Spring Cloud Sleuth
- Monitoring microservices
- Monitoring challenges
- Monitoring tools
- Monitoring microservice dependency
- Spring Cloud Hystrix for fault-tolerant microservices
- Aggregate Hystrix streams with Turbine
- Data analysis using Data Lake
- Summary
- Containerizing Microservices with Docker
- Understanding gaps in the BrownField PSS microservices
- What are containers?
- Difference between VM and containers
- Benefits of containers
- Microservices and containers
- Introduction to Docker
- Key components of Docker
- The Docker daemon
- The Docker client
- The Docker image
- The Docker container
- The Docker registry
- Dockerfile
- Deploying microservices into Docker
- Running RabbitMQ on Docker
- Using the Docker registry
- Setting up the Docker Hub
- Publish microservices to the Docker Hub
- Microservices on Cloud
- Installing Docker on AWS EC2
- Running BrownField services on EC2
- Future of containerization
- Summary
- Scaling Dockerized Microservices with Mesos and Marathon
- Scaling microservices
- Understanding autoscaling
- The missing pieces
- Container orchestration
- Why is container orchestration is important
- What does container orchestration do?
- Relationship with microservices
- Relationship with virtualization
- Container orchestration solutions
- Docker Swarm
- Kubernetes
- Apache Mesos
- HashiCorp Nomad
- CoreOS Fleet
- Container orchestration with Mesos and Marathon
- Mesos in details
- Mesos architecture
- Marathon
- Implementing Mesos and Marathon with DCOS
- Implementing Mesos and Marathon for BrownField microservices
- Installing Mesos Marathon and related components
- Running Mesos and Marathon
- Preparing BrownField PSS services
- Deploying BrownField PSS services
- Summary
- Microservice Development Life Cycle
- Practice points for microservice development
- Understanding business motivation and value
- Change the mindset from project to product development
- Choosing the right development philosophy
- Using the concept of minimum viable product (MVP)
- Overcoming the legacy hotspot
- Establishing self-organizing teams
- Building the self-service cloud
- Building a microservices ecosystem
- DevOps as a life cycle process
- Value driven planning
- Continuous monitoring and feedback
- Automating development cycle
- Development
- Integration
- Testing
- Sanity tests
- Regression testing
- Functional testing
- Acceptance testing
- Performance testing
- Real user flow simulation or Journey testing
- Security testing
- Exploratory testing
- A/B testing Canary testing and blue-green deployments
- Other non-functional tests
- Testing in production (TiP)
- Antifragility testing
- Deployment
- Monitoring and feedback
- Configuration management
- Microservices development governance reference architectures and libraries
- Summary 更新時(shí)間：2021-07-02 19:46:00
