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

Configuring tools for CI and CD with our microservices


Build, test, and deployment are integral parts of any web project. CI and CD tools are used in the automation of these three steps. To figure out any good tool for CI and CD for your project, make sure that the project supports the preceding three automations.

The upcoming diagram explains the generic work flow. There could be customization in this process, but this is mainly how it works. Let's try to understand its steps:

  1. The developer develops and pushes the code.
  2. They raise the merge request so that the other member can review the code.
  1. The other members review the code of the developer and either pass it or give the developer some review comments. This cycle can happen 2-3 times depending on the length and quality of code.
  2. The reviewer merges the code to branch, and it triggers the build of the software package.
  3. It is automatically deployed to environment, let's say Dev-environment.
  4. All kinds of test cases should be run automatically in...