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

Data model in monolithic architecture


In monolithic applications, all modules are bundled in one big fat application, such as WAR/JAR/EAR. If one module has to use another module's functionality, then it will make a simple call to that module. This is how module dependencies are created. Modules share data among themselves. This is the way dependencies are created among various microservices. They might be using the same one-instance database. This eventually creates tight coupling between modules by sharing the common data model. That's why a database model can be seen as one large database behind an application. In a traditional data model, the journey starts from an ER diagram and ends with a relational model. The relational model basically includes tables and relations between tables. Attributes are defined as fields or columns of these tables. One row of a table in the relational database is called the tuple. Every tuple must have a unique key that define its data uniquely. These keys...