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)

Understanding the messaging domains

Let's start by looking at what we require from a messaging system and how it works at a high level. A messaging system is characterized by the following attributes:

  • The message itself
  • The interaction mode
  • The messaging system

The message represents the business data that is used either for further processing or for persistence.

The interaction mode can be either synchronous or asynchronous. In synchronous mode, the producer of the message and the receiver system are both in sync and have to be available simultaneously. They will be tightly coupled. In asynchronous mode, however, the interacting systems are loosely coupled, which means the applications are not tied to each other over a message interaction and they aren't aware of the existence of each other. All they need is the messaging format to be defined. The applications interact...