Book Image

Practical Microservices

By : Umesh Ram Sharma
Book Image

Practical Microservices

By: Umesh Ram Sharma

Overview of this book

<p>A microservice architecture helps you build your application as a suite of different services. This approach has been widely adopted as it helps to easily scale up your application with reduced dependencies. This way if a part of your application is corrupted, it can be fixed easily thereby eliminating the possibility of completely shutting down your software. This book will teach you how to leverage Java to build scalable microservices. You will learn the fundamentals of this architecture and how to efficiently implement it practically.</p> <p>We start off with a brief introduction to the microservice architecture and how it fares with the other architectures. The book dives deep into essential microservice components and how to set up seamless communication between two microservice end points. You will create an effective data model and learn different ways to test and deploy a microservices. You will also learn the best way to migrate your software from a monolith to a microservice architecture.</p> <p>Finishing off with monitoring, scaling and troubleshooting, this book will set a solid foundation for you to start implementing microservices.</p>
Table of Contents (17 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Principles in monitoring a microservice system


Monitoring is one of the key considerations in microservice control systems. Unfortunately, migrating to a microservices architecture gives you flexibility, but it has its challenges as well, since it turns one single monolithic application to complex distributed micro systems. How many nodes or microservices you have is directly proportional to the chances of failure. It can be extremely difficult to have visibility about the communication and request flow between different microservices. In this architecture, monitoring becomes as important as development. Any application, whether it is a web application or mobile application, might have a single API call to system, but behind the scenes, that single API call might turn into tons of internal communication. If anything fails here, even one of them, DevOps and developer have to track it back. It becomes very important for developers and DevOps to have visibility of the internal system so that...