Chapter 4. Conclusion: The Microservice API Security Frontier
The first three chapters of this book serve a practical purpose: to outline the microservice API security landscape and its requirements, to review the current solution options available in the industry, and most importantly to define a platform independent approach to securing web APIs in a microservice architecture. However, as a secondary purpose, we hope that the concepts and approaches introduced here can help to cover existing gaps and explore new areas of microservice architecture and API security.
Standardizing the Language of Microservices
This book proposes a conceptual vocabulary for API security in a microservice architecture, through “The Microservice API Landscape” and the definition of DHARMA’s foundational concepts in Figure 3-2. Given the growth in scope and popularity of the microservices approach, we hope this vocabulary can be used beyond the API security scope and help software architects develop consistent language when working with complex systems of microservices.
Applying DHARMA
Chapter 3 includes a detailed description of how DHARMA can be implemented using platform-independent access and trust mechanisms. Still, it is quite possible to implement DHARMA using platform-specific mechanisms such as those listed in Chapter 2. It is expected that the service registries such as Consul and etcd that are used for service discovery and dynamic configuration could play a role in the security landscape ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access