Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Embracing Microservices Design
  • Toc
  • feedback
Embracing Microservices Design

Embracing Microservices Design

By : Mehboob Ahmed Khan, Siddiqui, Timothy Oleson
4.6 (14)
close
Embracing Microservices Design

Embracing Microservices Design

4.6 (14)
By: Mehboob Ahmed Khan, Siddiqui, Timothy Oleson

Overview of this book

Microservices have been widely adopted for designing distributed enterprise apps that are flexible, robust, and fine-grained into services that are independent of each other. There has been a paradigm shift where organizations are now either building new apps on microservices or transforming existing monolithic apps into microservices-based architecture. This book explores the importance of anti-patterns and the need to address flaws in them with alternative practices and patterns. You'll identify common mistakes caused by a lack of understanding when implementing microservices and cover topics such as organizational readiness to adopt microservices, domain-driven design, and resiliency and scalability of microservices. The book further demonstrates the anti-patterns involved in re-platforming brownfield apps and designing distributed data architecture. You’ll also focus on how to avoid communication and deployment pitfalls and understand cross-cutting concerns such as logging, monitoring, and security. Finally, you’ll explore testing pitfalls and establish a framework to address isolation, autonomy, and standardization. By the end of this book, you'll have understood critical mistakes to avoid while building microservices and the right practices to adopt early in the product life cycle to ensure the success of a microservices initiative.
Table of Contents (16 chapters)
close
close
Preface
Preface
Who this book is for
What this book covers
Download the color images
Conventions used
Get in touch
Share Your Thoughts
1
Section 1: Overview of Microservices, Design, and Architecture Pitfalls
Section 1: Overview of Microservices, Design, and Architecture Pitfalls
Free Chapter
2
Chapter 1: Setting Up Your Mindset for a Microservices Endeavor
chevron up
Chapter 1: Setting Up Your Mindset for a Microservices Endeavor
Philosophy of microservices
Microservice design principles
Building teams to deliver business value faster
Benefits of microservices
Challenges of microservices
Microservice architecture components
Reviewing leadership responsibilities
Defining core priorities for a business
Using the twelve-factor app methodology
Additional factors for modern cloud-native apps
Summary
Questions
Further reading
3
Chapter 2: Failing to Understand the Role of DDD
Chapter 2: Failing to Understand the Role of DDD
What are microservices and how do they align with DDD?
Benefits and challenges of microservices as compared to DDD
Lack of team alignment
Lack of governance
The whole is greater than the sum of its parts
Microservices are based on science
Complex or not complex – that is the question
DDD
A lack of awareness of stakeholder needs
Bounded contexts
Summary
Questions
Further reading
4
Chapter 3: Microservices Architecture Pitfalls
Chapter 3: Microservices Architecture Pitfalls
Layered architecture and its challenges
Over-architecting microservices
Overusing frameworks and technologies
Not abstracting common microservice tasks
Lack of knowledge about the microservice platform
Neutralizing the benefits of microservices by adopting a frontend monolithic architecture
Summary
Questions
Further reading
5
Chapter 4: Keeping the Replatforming Brownfield Applications Trivial
Chapter 4: Keeping the Replatforming Brownfield Applications Trivial
Not knowing the fundamentals when replatforming brownfield applications
Overlooking availability, reliability, and scalability when designing a microservices architecture
Sharing dependencies using older techniques
Summary
Questions
Further reading
6
Section 2: Overview of Data Design Pitfalls, Communication, and Cross-Cutting Concerns
Section 2: Overview of Data Design Pitfalls, Communication, and Cross-Cutting Concerns
7
Chapter 5: Data Design Pitfalls
Chapter 5: Data Design Pitfalls
The pitfalls of keeping a single shared database
Normalizing read models
Understanding the CQRS principle
The pitfalls of not knowing how to handle transactions
Not choosing the right consistency and concurrency
Knowing how to perform reporting
Summary
Questions
8
Chapter 6: Communication Pitfalls and Prevention
Chapter 6: Communication Pitfalls and Prevention
The fundamentals of microservices communication
Different architectures and their communication styles
Direct client-to-microservice communication
The overly complicated API gateway
Request timeout
Long chains of synchronous calls – the retry storm
The dark side of event-driven microservices
Avoiding service versioning
Service meshes
Dapr versus service meshes
Summary
Questions
Further reading
9
Chapter 7: Cross-Cutting Concerns
Chapter 7: Cross-Cutting Concerns
Microservices chassis patterns
Cross-cutting pitfalls
Summary
Questions
10
Section 3: Testing Pitfalls and Evaluating Microservices Architecture
Section 3: Testing Pitfalls and Evaluating Microservices Architecture
11
Chapter 8: Deployment Pitfalls
Chapter 8: Deployment Pitfalls
Failing to establish a deployment strategy
Using outdated tools and technologies
Failing to obtain cooperation from all teams
Not considering Infrastructure as Code (IaC) for environment setup
Not knowing the core principles of DevOps
Deployment stamps pattern
Deployment rings
Geode pattern
Summary
Questions
12
Chapter 9: Skipping Testing
Chapter 9: Skipping Testing
The shift-left testing strategy
Unit testing
End-to-end testing
Integration testing
Load testing
Summary
Questions
Further reading
13
Chapter 10: Evaluating Microservices Architecture
Chapter 10: Evaluating Microservices Architecture
Identifying the core priorities of a business
Managing architectural decisions
Team structure
Choosing the right methodology
Decomposition strategy
Evaluating the DevOps capability
Understanding which part of the business is going to change more rapidly
Infrastructure readiness
Release cycles
Communication protocol across services
Exposing services to clients
Distributed transaction handling
Service development
Capabilities of the hosting platform
Deployment strategy
Monitoring services
Assigning a correlation token to each service request
Defining a microservices chassis framework
Shift-left approach for testing and security
Summary
14
Assessments
Assessments
Chapter 1: Setting Up Your Mindset for Microservices Endeavor
Chapter 2: Failing to Understand the Role of DDD
Chapter 3: Microservices Architecture Pitfalls
Chapter 4: Keeping the Re-Platforming of Brownfield Applications Trivial
Chapter 5: Data Design Pitfalls
Chapter 6: Communication Pitfalls and Prevention
Chapter 7: Cross-Cutting Concerns
Chapter 8: Deployment Pitfalls
Chapter 9: Skipping Testing
Why subscribe?
15
Other Books You May Enjoy
Other Books You May Enjoy
Packt is searching for authors like you
Share Your Thoughts

Chapter 1: Setting Up Your Mindset for a Microservices Endeavor

Microservices is an architectural style that structures an application into multiple services that encapsulate business capabilities. These microservices are usually much smaller, both in terms of scope and functionality, compared to traditional services. They have logical and physical separation, and they communicate with each other via messages over a network to form an application.

Adopting the microservice architecture is a journey that requires a mindset that can embrace changes in culture, processes, and practices. In essence, organizations need to go through several changes to increase agility and adaptability to achieve their goals and deliver business value.

In this chapter, we will help you understand the philosophy of microservices and the various aspects that help organizations with their digital transformation. We will also learn about microservice design principles and their components, along with their benefits and challenges. Finally, we will discuss the role of leadership and how to get started by adopting widely accepted practices in the industry.

The following topics will be covered in this chapter:

  • Philosophy of microservices
  • Microservice design principles
  • Building teams to deliver business value faster
  • Benefits of microservices
  • Challenges of microservices
  • Microservice architecture components
  • Reviewing leadership responsibilities
  • Defining core priorities for a business
  • Using the twelve-factor app methodology
  • Additional factors for modern cloud-native apps

This chapter aims to help you understand the key concepts of microservices and their potential for bringing change that can fuel business growth for organizations. In addition, we will discuss the role of leadership in shifting the mindset by building effective teams that embrace change to deliver business value faster. Finally, we will dive into the "Twelve-Factor App" methodology, which has helped many organizations in their successful adoption of microservices.

End of Section 1
Next Section
bookmark search playlist download
font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete