Book Image

Full Stack Development with JHipster,

By : Deepu K Sasidharan, Sendil Kumar Nellaiyapen
Book Image

Full Stack Development with JHipster,

By: Deepu K Sasidharan, Sendil Kumar Nellaiyapen

Overview of this book

JHipster is a development platform to generate, develop, and deploy Spring Boot and Angular/React applications and Spring microservices. It provides you with a variety of tools that will help you quickly build modern web applications. This book will be your guide to building full stack applications with Spring and Angular using the JHipster tool set. You will begin by understanding what JHipster is and the various tools and technologies associated with it. You will learn the essentials of a full stack developer before getting hands-on and building a monolithic web application with JHipster. From here you will learn the JHipster Domain Language with entity modeling and entity creation using JDL and JDL studio. Moving on, you will be introduced to client side technologies such as Angular and Bootstrap and will delve into technologies such as Spring Security, Spring MVC, and Spring Data. You will learn to build and package apps for production with various deployment options such as Heroku and more. During the course of the book, you will be introduced to microservice server-side technologies and how to break your monolithic application with a database of your choice. Next, the book takes you through cloud deployment with microservices on Docker and Kubernetes. Going forward, you will learn to build your client side with React and master JHipster best practices. By the end of the book, you will be able to leverage the power of the best tools available to build modern web applications.
Table of Contents (23 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Foreword
Contributors
Preface
Index

Microservice applications versus monoliths


The benefits of microservice architectures can be better understood by comparing them with monolithic architectures.

Note

The benefits of microservices over monoliths are phenomenal when they are designed and deployed correctly.

It is not as simple as splitting a monolithic application based on structure, component, or functionality and then deploying them as individual services. This will not work out. Converting a monolithic application or even a monolithic design into microservices needs a clear vision of the product. It includes knowledge of what part of the project will change and what part will be consistent. We must have low-level details, such as which entities we should group together and those that can be separated. 

This clearly illustrates the need for an ever-evolving model. It is much easier to split the technologies used in the application, but not the interdependent models or the business logic of the application. So it is essential...