Newman - Building Microservices

This book is primarily organized in a topic-based format. As such, you may want to jump into the specific topics that interest you the most. While I have done my best to reference terms and ideas in the earlier chapters, Id like to think that even people who consider themselves fairly experienced will find something of interest in all chapters here. I would certainly suggest that you take a look at , which touches on the breadth of the topic as well as providing some framing for how I go about things in case if you want to dive deeper into some of the later topics.

For people new to the subject, Ive structured the chapters in a way that I hope will make sense to read from beginning to end.

Here is an overview of what we cover:

Well begin with an introduction to microservices, including the key benefits as well as some of the downsides.

This chapter discusses the difficulties we face in terms of making trade-offs as architects, and covers specifically just how many things we need to think about with microservices.

Here well start to define the boundary of microservices, using techniques from domain-driven design to help focus our thinking.

This is where we start getting a bit deeper into specific technology implications, as we discuss what sorts of service collaboration techniques will help us most. Well also delve into the topic of user interfaces and integrating with legacy and commercial off-the-shelf (COTS) products.

Many people get interested in microservices as an antidote to large, hard-to-change monolithic systems, and this is exactly what well cover in detail in this chapter.

Although this book is primarily theoretical, few topics in the book have been as impacted by recent changes in technology as deployment, which well explore here.

This chapter goes deep into the topic of testing, an area of particular concern when handling the deployment of multiple discrete services. Of particular note will be the role that consumer-driven contracts can play in helping us ensure the quality of our software.

Testing our software before production doesnt help if problems occur once we go live, and this chapter explores how we can monitor our fine-grained systems and deal with some of the emergent complexity of distributed systems.

Here well examine the security aspects of microservices and consider how to handle user-to-service and service-to-service authentication and authorization. Security is a very important topic in computing, one that is all too readily ignored. Although I am in no way a security expert, I hope that this chapter will at least help you consider some of the aspects you need to be aware of when building systems, and microservice systems in particular.