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

Gateway application generation


We will start by converting the monolithic application that we have generated into a microservice gateway application. 

Even though microservices are made up of different services inside, for end users it should be a single, unified product. There are a lot of services that are designed to work in a lot of different ways, but there should be a single entry point for users. Thus, we need a gateway application, since they form the frontend of your application. 

Segregate the internal contracts and services from external users. We may have application-level internal services that we shouldn't expose to external users, so these can be masked away. This also adds another level of security to the application.

Easier to mock services for testing help validate the services independently in integration testing.

Converting a monolithic application to a microservice gateway

We already have our monolithic application generated, as well as our entities. As a part of monolithic...