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

Chapter 5. Creating an Effective Data Model

The software industry is rapidly changing. Rules, dimensions, and laws are changing daily. To gain more knowledge about the industry, you need to reiterate fast, build, get feedback, improve, and so on. Moving at this pace in a monolithic environment will make things more complicated. Microservices makes this path smooth. Going by the microservice architecture and breaking big problems into smaller ones can lead us to distributed components. Working in a distribution or scalability area always challenges the traditional ways of doing things. The ripple effect of distributed architecture can be seen on the database also. The traditional data model can't be applied to distributed architecture. Another challenge is dependencies. When problems become smaller and distributed, it is challenging to maintain the dependencies among different components. These dependencies can be in terms of the data model, coding library, and so on. So, what is the best...