Book Image

Kotlin for Enterprise Applications using Java EE

By : Raghavendra Rao K
Book Image

Kotlin for Enterprise Applications using Java EE

By: Raghavendra Rao K

Overview of this book

Kotlin was developed with a view to solving programmers’ difficulties and operational challenges. This book guides you in making Kotlin and Java EE work in unison to build enterprise-grade applications. Together, they can be used to create services of any size with just a few lines of code and let you focus on the business logic. Kotlin for Enterprise Applications using Java EE begins with a brief tour of Kotlin and helps you understand what makes it a popular and reasonable choice of programming language for application development, followed by its incorporation in the Java EE platform. We will then learn how to build applications using the Java Persistence API (JPA) and Enterprise JavaBeans (EJB), as well as develop RESTful web services and MicroServices. As we work our way through the chapters, we’ll use various performance improvement and monitoring tools for your application and see how they optimize real-world applications. At each step along the way, we will see how easy it is to develop enterprise applications in Kotlin. By the end of this book, we will have learned design patterns and how to implement them using Kotlin.
Table of Contents (13 chapters)

Breaking the monolith into microservices

Traditionally, enterprise applications were built as single, large, monolith applications. They were also sometimes built on database-driven systems that stored all logic, from UI to business, and data. Typically, a monolith application looks something like the following:

The problem with the monolith service architecture is that any failure in the system will halt the entire system and a small problem can bring down the entire application. When any code change or new implementation has to be applied, this would result in rebuilding and redeploying the whole system.

Since there is a code change, the system has to go through the entire verification process. Any library upgrade is a nightmare. When the system becomes bulky, it is very difficult to maintain.

Any code refactoring to improve the code quality or performance will take a lot...