舉報 
會員
Building Microservices with .NET Core
最新章節(jié)：
Summary
Thisbookisfor.NETCoredeveloperswhowanttolearnandunderstandmicroservicesarchitectureandimplementitintheir.NETCoreapplications.It’sidealfordeveloperswhoarecompletelynewtomicroservicesorhavejustatheoreticalunderstandingofthisarchitecturalapproachandwanttogainapracticalperspectiveinordertobettermanageapplicationcomplexity.
最新章節(jié)
- Summary
- The user auth microservice
- The order microservice
- The shopping cart microservice
- The book catalog microservice
- Synchronous versus asynchronous
品牌：中圖公司
上架時間：2021-07-02 18:43:46
出版社：Packt Publishing
本書數字版權由中圖公司提供，并由其授權上海閱文信息技術有限公司制作發(fā)行
- Summary 更新時間：2021-07-02 22:08:53
- The user auth microservice
- The order microservice
- The shopping cart microservice
- The book catalog microservice
- Synchronous versus asynchronous
- User authentication
- The order microservice
- The shopping cart microservice
- The book-searching microservice
- The book-listing microservice
- Scoping our services
- Greenfield application
- Reactive microservices
- Service design
- Infrastructure scaling
- Scalability
- Monitoring strategies
- Information visualization
- Component lifespan
- Scale
- Monitoring challenges
- Monitoring
- Security
- Testing microservices
- Deployment
- Integration techniques
- Monolith transitioning
- Messaging in microservices
- Microservice-styled architecture
- Service-oriented architecture
- Scaling
- Challenges in standardizing the .NET stack
- The monolithic architecture
- Architectures before microservices
- Creating a Complete Microservice Solution
- Summary
- Client - coding it down
- Creating the project
- Reactive microservices - coding it down
- The microservice ecosystem
- Managing data
- Communication resilience
- Scalability
- Message-level security
- Security
- Event communication
- Making it reactive
- Being message-driven
- Autonomous
- Resilience
- Responsiveness
- What are reactive microservices?
- Reactive Microservices
- Summary
- Service discovery
- Circuit breakers
- Redundancy and fault tolerance
- Caching mechanism
- Data persistence model design
- Scaling service design
- Container scaling using Docker swarm
- Auto Scaling
- Scaling virtual machines using scale sets
- Scaling the infrastructure
- Characteristics of a scalable microservice
- Y-axis scaling
- Z-axis scaling
- X-axis scaling
- Scale Cube model of scalability
- Microservices scalability
- Horizontal scaling (scaling out)
- Vertical scaling (scaling up)
- Scaling infrastructure
- Scalability overview
- Scaling
- Summary
- Reporting
- Alerting
- Splunk
- Kibana
- Logstash
- Elasticsearch
- A brief overview of the ELK stack
- Other microservice monitoring solutions
- Introduction of Application Insights
- Azure storage schema for diagnostic data
- Specifying a storage account
- Using Azure portal
- Storing diagnostic data using Azure storage
- Microsoft Azure Diagnostics
- Monitoring in Azure Cloud
- Semantic logging
- Use of a correlation ID in logging
- Centralized logging
- Logging strategies
- Logging challenges
- Logging
- Monitoring strategies
- Monitoring challenges
- Troubleshooting system failures
- End user monitoring
- Auditing sensitive data and critical business transactions
- SLA monitoring
- Security monitoring
- Performance monitoring
- Availability monitoring
- Health monitoring
- The need for monitoring
- Telemetry
- Instrumentation
- Instrumentation and telemetry
- Monitoring
- Summary
- Other security best practices
- Container security
- Azure API management as an API gateway
- Step 5 - Run both the applications
- Step 4 - Generate client certificates on IIS Express
- Step 3 - Configuring Visual Studio solution projects
- Step 2 - Generation of AppKey for TodoListWebApp
- Step 1 - Registration of TodoListService and TodoListWebApp with Azure AD tenant
- Microservice Auth example with OpenID Connect OAuth 2.0 and Azure AD
- Azure Active Directory
- What is OpenID Connect?
- What is OAuth 2.0?
- JSON Web Tokens
- Why traditional .NET auth mechanism won't work?
- Security in microservices
- Security in monolithic applications
- Security
- Summary
- Adding Docker Support
- Creating an ASP.NET web application
- Setting up Docker on your machine
- Microservice deployment example using Docker
- Microservice deployment with Docker overview
- Docker quick introduction
- It works on your machine? Let's ship your machine!
- Containers are new binaries
- Transformation of the operation team's mindset
- Suitability of containers over virtual machines
- What are containers?
- Containers
- Need for a new deployment paradigm
- Isolation requirements for microservice deployment
- Prerequisites for successful microservice deployments
- Understanding the deployment terminology
- Monolithic application deployment challenges
- Deployment
- Summary
- Integration tests
- Unit tests
- Getting ready with the test project
- Tests in action
- Stubs and mocks
- Sociable versus isolated unit tests
- End-to-end (UI/functional) testing
- Performance testing
- How Pact-net-core helps us achieve our goal
- How to implement a consumer-driven test
- Consumer-driven contracts
- Contract testing
- Integration testing
- Component (service) testing
- Unit testing
- Types of microservice tests
- Testing pyramid
- Testing strategies (testing approach)
- Handling challenges
- How to test microservices
- Testing Strategies
- Summary
- Receiving messages from the queue
- Sending messages to the queue
- Prerequisites
- Implementation of an Azure Service Bus queue
- Azure Service Bus queues
- Competing Consumers
- Compensating Transaction
- Eventual consistency
- Event sourcing
- The event-driven pattern
- The API gateway
- Integration patterns
- Styles of collaborations
- Communication between services
- Integration Techniques
- Summary
- Revisiting the product controller
- Introducing ViewModel
- Revisiting repositories and the controller
- Database migration
- EF Core migrations
- EF Core DbContext
- Adding EF core support
- The ProductService API
- Adding a product controller
- Registering the repositories
- Adding a repository
- Adding the model
- Creating our project
- Code migration
- Migrations
- Transitioning to our product service
- Prerequisites
- Revisiting the case study--Flix One
- API gateway versus API management
- Benefits of the API gateway for microservices
- Communication between microservices
- Transaction
- Master data
- Database
- Team structure
- Technology
- Module interdependency
- The concept of Seam
- Importance for microservices
- Domain model design
- DDD and its importance for microservices
- What makes a good service?
- Size of microservices
- Building Microservices
- Summary
- Integrating monolithic
- Data management
- Security
- Easy scalability
- Cost benefits
- Alignment with business goals
- Interdependency removal
- Technology independence
- Important microservices advantages
- Identifying decomposition candidates within monolithic
- Deployment
- Versioning
- Testing
- Automation
- DevOps culture
- Database sharding and partitioning
- Database refactoring
- Introducing dependency injections
- Making much better monolithic applications
- Handling deployment problems
- Solutions for current challenges
- Functional overview of the application
- Prerequisites for microservices
- Big database
- Modularity
- Organizational alignment
- Deployment challenges
- Horizontal scaling or scale out
- Vertical scaling or scale up
- Scaling
- Fault tolerance
- Challenges in standardizing a .NET stack
- Understanding problems with the monolithic architecture style
- Prerequisites of the microservice architecture
- SOA versus microservices
- Advantages of microservices
- How does the microservice architecture work?
- Why should we use microservices?
- Message formats
- Asynchronous messaging
- Synchronous messaging
- Messaging in microservices
- Understanding the microservice architecture
- What is service?
- Service-oriented architecture
- Monolithic architecture
- Discussing microservices
- Origin of microservices
- What Are Microservices?
- Questions
- Piracy
- Errata
- 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
- www.PacktPub.com
- About the Reviewers
- About the Authors
- Foreword
- Credits
- Title Page
- coverpage
- coverpage
- Title Page
- Credits
- Foreword
- About the Authors
- About the Reviewers
- www.PacktPub.com
- 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
- Errata
- Piracy
- Questions
- What Are Microservices?
- Origin of microservices
- Discussing microservices
- Monolithic architecture
- Service-oriented architecture
- What is service?
- Understanding the microservice architecture
- Messaging in microservices
- Synchronous messaging
- Asynchronous messaging
- Message formats
- Why should we use microservices?
- How does the microservice architecture work?
- Advantages of microservices
- SOA versus microservices
- Prerequisites of the microservice architecture
- Understanding problems with the monolithic architecture style
- Challenges in standardizing a .NET stack
- Fault tolerance
- Scaling
- Vertical scaling or scale up
- Horizontal scaling or scale out
- Deployment challenges
- Organizational alignment
- Modularity
- Big database
- Prerequisites for microservices
- Functional overview of the application
- Solutions for current challenges
- Handling deployment problems
- Making much better monolithic applications
- Introducing dependency injections
- Database refactoring
- Database sharding and partitioning
- DevOps culture
- Automation
- Testing
- Versioning
- Deployment
- Identifying decomposition candidates within monolithic
- Important microservices advantages
- Technology independence
- Interdependency removal
- Alignment with business goals
- Cost benefits
- Easy scalability
- Security
- Data management
- Integrating monolithic
- Summary
- Building Microservices
- Size of microservices
- What makes a good service?
- DDD and its importance for microservices
- Domain model design
- Importance for microservices
- The concept of Seam
- Module interdependency
- Technology
- Team structure
- Database
- Master data
- Transaction
- Communication between microservices
- Benefits of the API gateway for microservices
- API gateway versus API management
- Revisiting the case study--Flix One
- Prerequisites
- Transitioning to our product service
- Migrations
- Code migration
- Creating our project
- Adding the model
- Adding a repository
- Registering the repositories
- Adding a product controller
- The ProductService API
- Adding EF core support
- EF Core DbContext
- EF Core migrations
- Database migration
- Revisiting repositories and the controller
- Introducing ViewModel
- Revisiting the product controller
- Summary
- Integration Techniques
- Communication between services
- Styles of collaborations
- Integration patterns
- The API gateway
- The event-driven pattern
- Event sourcing
- Eventual consistency
- Compensating Transaction
- Competing Consumers
- Azure Service Bus queues
- Implementation of an Azure Service Bus queue
- Prerequisites
- Sending messages to the queue
- Receiving messages from the queue
- Summary
- Testing Strategies
- How to test microservices
- Handling challenges
- Testing strategies (testing approach)
- Testing pyramid
- Types of microservice tests
- Unit testing
- Component (service) testing
- Integration testing
- Contract testing
- Consumer-driven contracts
- How to implement a consumer-driven test
- How Pact-net-core helps us achieve our goal
- Performance testing
- End-to-end (UI/functional) testing
- Sociable versus isolated unit tests
- Stubs and mocks
- Tests in action
- Getting ready with the test project
- Unit tests
- Integration tests
- Summary
- Deployment
- Monolithic application deployment challenges
- Understanding the deployment terminology
- Prerequisites for successful microservice deployments
- Isolation requirements for microservice deployment
- Need for a new deployment paradigm
- Containers
- What are containers?
- Suitability of containers over virtual machines
- Transformation of the operation team's mindset
- Containers are new binaries
- It works on your machine? Let's ship your machine!
- Docker quick introduction
- Microservice deployment with Docker overview
- Microservice deployment example using Docker
- Setting up Docker on your machine
- Creating an ASP.NET web application
- Adding Docker Support
- Summary
- Security
- Security in monolithic applications
- Security in microservices
- Why traditional .NET auth mechanism won't work?
- JSON Web Tokens
- What is OAuth 2.0?
- What is OpenID Connect?
- Azure Active Directory
- Microservice Auth example with OpenID Connect OAuth 2.0 and Azure AD
- Step 1 - Registration of TodoListService and TodoListWebApp with Azure AD tenant
- Step 2 - Generation of AppKey for TodoListWebApp
- Step 3 - Configuring Visual Studio solution projects
- Step 4 - Generate client certificates on IIS Express
- Step 5 - Run both the applications
- Azure API management as an API gateway
- Container security
- Other security best practices
- Summary
- Monitoring
- Instrumentation and telemetry
- Instrumentation
- Telemetry
- The need for monitoring
- Health monitoring
- Availability monitoring
- Performance monitoring
- Security monitoring
- SLA monitoring
- Auditing sensitive data and critical business transactions
- End user monitoring
- Troubleshooting system failures
- Monitoring challenges
- Monitoring strategies
- Logging
- Logging challenges
- Logging strategies
- Centralized logging
- Use of a correlation ID in logging
- Semantic logging
- Monitoring in Azure Cloud
- Microsoft Azure Diagnostics
- Storing diagnostic data using Azure storage
- Using Azure portal
- Specifying a storage account
- Azure storage schema for diagnostic data
- Introduction of Application Insights
- Other microservice monitoring solutions
- A brief overview of the ELK stack
- Elasticsearch
- Logstash
- Kibana
- Splunk
- Alerting
- Reporting
- Summary
- Scaling
- Scalability overview
- Scaling infrastructure
- Vertical scaling (scaling up)
- Horizontal scaling (scaling out)
- Microservices scalability
- Scale Cube model of scalability
- X-axis scaling
- Z-axis scaling
- Y-axis scaling
- Characteristics of a scalable microservice
- Scaling the infrastructure
- Scaling virtual machines using scale sets
- Auto Scaling
- Container scaling using Docker swarm
- Scaling service design
- Data persistence model design
- Caching mechanism
- Redundancy and fault tolerance
- Circuit breakers
- Service discovery
- Summary
- Reactive Microservices
- What are reactive microservices?
- Responsiveness
- Resilience
- Autonomous
- Being message-driven
- Making it reactive
- Event communication
- Security
- Message-level security
- Scalability
- Communication resilience
- Managing data
- The microservice ecosystem
- Reactive microservices - coding it down
- Creating the project
- Client - coding it down
- Summary
- Creating a Complete Microservice Solution
- Architectures before microservices
- The monolithic architecture
- Challenges in standardizing the .NET stack
- Scaling
- Service-oriented architecture
- Microservice-styled architecture
- Messaging in microservices
- Monolith transitioning
- Integration techniques
- Deployment
- Testing microservices
- Security
- Monitoring
- Monitoring challenges
- Scale
- Component lifespan
- Information visualization
- Monitoring strategies
- Scalability
- Infrastructure scaling
- Service design
- Reactive microservices
- Greenfield application
- Scoping our services
- The book-listing microservice
- The book-searching microservice
- The shopping cart microservice
- The order microservice
- User authentication
- Synchronous versus asynchronous
- The book catalog microservice
- The shopping cart microservice
- The order microservice
- The user auth microservice
- Summary 更新時間：2021-07-02 22:08:53
