You're reading from Embracing Microservices Design A practical guide to revealing anti-patterns and architectural pitfalls to avoid microservices fallacies

Product type Paperback

Published in Oct 2021

Publisher Packt

ISBN-13 9781801818384

Length 306 pages

Edition 1st Edition

Concepts

Design

Authors (3):

Ovais Mehboob Ahmed Khan

Timothy Oleson

Nabil Siddiqui

View More author details

Table of Contents (16) Chapters

Preface

1. Section 1: Overview of Microservices, Design, and Architecture Pitfalls

2. Chapter 1: Setting Up Your Mindset for a Microservices Endeavor FREE CHAPTER

3. Chapter 2: Failing to Understand the Role of DDD

4. Chapter 3: Microservices Architecture Pitfalls

5. Chapter 4: Keeping the Replatforming Brownfield Applications Trivial

6. Section 2: Overview of Data Design Pitfalls, Communication, and Cross-Cutting Concerns

7. Chapter 5: Data Design Pitfalls

8. Chapter 6: Communication Pitfalls and Prevention

9. Chapter 7: Cross-Cutting Concerns

10. Section 3: Testing Pitfalls and Evaluating Microservices Architecture

11. Chapter 8: Deployment Pitfalls

12. Chapter 9: Skipping Testing

13. Chapter 10: Evaluating Microservices Architecture

14. Assessments

15. Other Books You May Enjoy

Additional factors for modern cloud-native apps

In Beyond the Twelve-Factor App, Kevin Hoffman discussed three additional factors that are important for building cloud-native applications in the modern era. Let's take a look.

API first

In the API first approach, applications are designed with the intent to be consistent and reusable. The API description language helps in providing a contract that dictates the behavior of an API. For example, Swagger provides the tooling for developing APIs with the OpenAPI specification.

Telemetry

In a cloud-native environment, teams have less control over the execution environment. They are dependent on the capabilities provided by the cloud vendor. Installing debuggers and inspectors is not an option, which makes real-time application monitoring and telemetry a challenge. To address telemetry, you need to make sure that you are collecting system/health data, application performance data, and domain-specific data so that you have complete visibility of the system in near real time.

Security

Security is an important pillar of a well-architected cloud-native application. The cloud-native application is built to run in multiple data centers to serve customers across the globe. They need to ensure that the clients accessing these applications are authenticated and authorized. These applications should identify every requestor and grant access based on their roles. At times, these requests are encrypted using Transport Layer Security (TLS) to ensure data privacy while data is in transit. Teams also need to think about securing their data at rest with the capabilities available in different storage platforms. As an example, Azure Cosmos DB and an Azure SQL server allow us to encrypt data at rest.

The preceding 12 factors and the three additional factors we've looked at here have given us a thorough understanding of building cloud-native microservices with an API first mindset. In the cloud-native world, security and telemetry are no longer an afterthought. Approaching security with a zero-trust mindset is essential, while continuously collecting data to monitor system health gives you the ability to make the necessary adjustments to achieve higher availability for the systems.