首頁(yè) > 計(jì)算機(jī)網(wǎng)絡(luò) > 編程語(yǔ)言與程序設(shè)計(jì) > Building Microservices with .NET Core 2.0（Second Edition）
舉報(bào) 
會(huì)員
Building Microservices with .NET Core 2.0（Second Edition）
Gaurav Aroraa 著
更新時(shí)間：2021-07-02 20:13:48
開會(huì)員，本書免費(fèi)讀 >
最新章節(jié)：
Summary
Thisbookisfor.NETCoredeveloperswhowanttolearnandunderstandthemicroservicesarchitectureandimplementitintheir.NETCoreapplications.It’sidealfordeveloperswhoarecompletelynewtomicroservicesorjusthaveatheoreticalunderstandingofthisarchitecturalapproachandwanttogainapracticalperspectiveinordertobettermanageapplicationcomplexities.
最新章節(jié)
- Summary
- The user-authentication microservice
- The order microservice
- The shopping-cart microservice
- The book-catalog microservice
- Synchronous versus asynchronous
品牌：中圖公司
上架時(shí)間：2021-07-02 18:28:02
出版社：Packt Publishing
本書數(shù)字版權(quán)由中圖公司提供，并由其授權(quán)上海閱文信息技術(shù)有限公司制作發(fā)行
- Summary 更新時(shí)間：2021-07-02 20:13:48
- The user-authentication 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
- Communication between the application and the database
- Creating the project
- Coding reactive microservices
- The microservice ecosystem
- Managing data
- Communication resilience
- Scalability
- Message-level security
- Security
- Event communication
- Let's make code reactive
- Message-driven: a core of reactive microservices
- Autonomous
- Resilience
- Responsiveness
- Understanding reactive microservices
- Introduction to Reactive Microservices
- Summary
- Service discovery
- Half-Open state
- Open state
- Closed state
- Circuit breakers
- Redundancy and fault tolerance
- Azure Redis Cache
- CacheCow
- 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
- Scaling of y axis
- Scaling of z axis
- Scaling of x axis
- Scale Cube model of scalability
- Microservice scalability
- Horizontal scaling (scaling out)
- Vertical scaling (scaling up)
- Scaling infrastructure
- Scalability overview
- Scaling Microservices
- 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
- Using a correlation ID in logging
- Centralized logging
- Logging strategies
- Logging challenges
- Logging
- Endpoint monitoring
- Profiling
- Semantic monitoring and synthetic transactions
- Real user monitoring
- Application/system monitoring
- Monitoring strategies
- Testing of monitoring tools
- Data flow visualization
- DevOps mindset
- Scale
- 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 Microservices
- Summary
- Other security best practices
- Container security
- Rate limit and quota policy example
- Azure API management as an API gateway
- Running both the applications
- Generate client certificates on IIS Express
- Configuring Visual Studio solution projects
- Generation of AppKey for TodoListWebApp
- 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 won't a traditional .NET auth mechanism work?
- Security in microservices
- Security in monolithic applications
- Securing Microservices
- Summary
- Creating an ASP.NET Core web application
- Prerequisites
- Setting up Docker on your machine
- Microservice deployment example using Docker
- Microservice deployment with Docker overview
- Introducing Docker
- Does it work 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
- Deploying Microservices
- Summary
- Consumer-driven contract tests
- Integration tests
- Unit tests
- Getting ready for 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 Microservices
- Summary
- Receiving messages from the queue
- Adding configuration settings
- Sending messages to the queue
- Prerequisites
- Implementing an Azure Service Bus queue
- Azure queues
- Azure Service Bus
- Competing consumers
- Compensating transactions
- Eventual consistency
- Event sourcing
- The event-driven pattern
- The API gateway
- Integration patterns
- Styles of collaboration
- Communication between services
- Integration Techniques and Microservices
- Summary
- Adding Swagger support
- 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 Flix One case study
- 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
- Microsoft SQLServer
- Visual Studio 2017
- Entity Framework Core
- C# 7.0
- Introduction
- Implementing Microservices
- Summary
- Overview of Azure Service Fabric
- 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 the problems with the monolithic architectural 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 a service?
- Service-Oriented architecture
- Monolithic architecture
- Discussing microservices
- Origin of microservices
- An Introduction to 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
- About the Author
- Foreword
- Credits
- 版權(quán)信息
- 封面
- 封面
- 版權(quán)信息
- Credits
- Foreword
- About the Author
- 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
- An Introduction to Microservices
- Origin of microservices
- Discussing microservices
- Monolithic architecture
- Service-Oriented architecture
- What is a 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 the problems with the monolithic architectural 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
- Overview of Azure Service Fabric
- Summary
- Implementing Microservices
- Introduction
- C# 7.0
- Entity Framework Core
- Visual Studio 2017
- Microsoft SQLServer
- 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 Flix One case study
- 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
- Adding Swagger support
- Summary
- Integration Techniques and Microservices
- Communication between services
- Styles of collaboration
- Integration patterns
- The API gateway
- The event-driven pattern
- Event sourcing
- Eventual consistency
- Compensating transactions
- Competing consumers
- Azure Service Bus
- Azure queues
- Implementing an Azure Service Bus queue
- Prerequisites
- Sending messages to the queue
- Adding configuration settings
- Receiving messages from the queue
- Summary
- Testing Microservices
- 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 for the test project
- Unit tests
- Integration tests
- Consumer-driven contract tests
- Summary
- Deploying Microservices
- 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
- Does it work on your machine? Let's ship your machine!
- Introducing Docker
- Microservice deployment with Docker overview
- Microservice deployment example using Docker
- Setting up Docker on your machine
- Prerequisites
- Creating an ASP.NET Core web application
- Summary
- Securing Microservices
- Security in monolithic applications
- Security in microservices
- Why won't a traditional .NET auth mechanism 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
- Registration of TodoListService and TodoListWebApp with Azure AD tenant
- Generation of AppKey for TodoListWebApp
- Configuring Visual Studio solution projects
- Generate client certificates on IIS Express
- Running both the applications
- Azure API management as an API gateway
- Rate limit and quota policy example
- Container security
- Other security best practices
- Summary
- Monitoring Microservices
- 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
- Scale
- DevOps mindset
- Data flow visualization
- Testing of monitoring tools
- Monitoring strategies
- Application/system monitoring
- Real user monitoring
- Semantic monitoring and synthetic transactions
- Profiling
- Endpoint monitoring
- Logging
- Logging challenges
- Logging strategies
- Centralized logging
- Using 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 Microservices
- Scalability overview
- Scaling infrastructure
- Vertical scaling (scaling up)
- Horizontal scaling (scaling out)
- Microservice scalability
- Scale Cube model of scalability
- Scaling of x axis
- Scaling of z axis
- Scaling of y axis
- 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
- CacheCow
- Azure Redis Cache
- Redundancy and fault tolerance
- Circuit breakers
- Closed state
- Open state
- Half-Open state
- Service discovery
- Summary
- Introduction to Reactive Microservices
- Understanding reactive microservices
- Responsiveness
- Resilience
- Autonomous
- Message-driven: a core of reactive microservices
- Let's make code reactive
- Event communication
- Security
- Message-level security
- Scalability
- Communication resilience
- Managing data
- The microservice ecosystem
- Coding reactive microservices
- Creating the project
- Communication between the application and the database
- 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-authentication microservice
- Summary 更新時(shí)間：2021-07-02 20:13:48
