Book Image

Hands-On Microservices with Kotlin

By : Juan Antonio Medina Iglesias
Book Image

Hands-On Microservices with Kotlin

By: Juan Antonio Medina Iglesias

Overview of this book

With Google's inclusion of first-class support for Kotlin in their Android ecosystem, Kotlin's future as a mainstream language is assured. Microservices help design scalable, easy-to-maintain web applications; Kotlin allows us to take advantage of modern idioms to simplify our development and create high-quality services. With 100% interoperability with the JVM, Kotlin makes working with existing Java code easier. Well-known Java systems such as Spring, Jackson, and Reactor have included Kotlin modules to exploit its language features. This book guides the reader in designing and implementing services, and producing production-ready, testable, lean code that's shorter and simpler than a traditional Java implementation. Reap the benefits of using the reactive paradigm and take advantage of non-blocking techniques to take your services to the next level in terms of industry standards. You will consume NoSQL databases reactively to allow you to create high-throughput microservices. Create cloud-native microservices that can run on a wide range of cloud providers, and monitor them. You will create Docker containers for your microservices and scale them. Finally, you will deploy your microservices in OpenShift Online.
Table of Contents (14 chapters)

Publishing to OpenShift

When we have the code for our microservice ready, and our tests are completed, we are ready to start doing our deployment into production. In this section, we will learn how easily we can deploy our microservice in OpenShift Online and how we can manage it. Then, we will update our microservice code and trigger new deployments to complete the life cycle of deployments of our application.

Creating an application

In order to deploy our microservice, first we need to create an application in OpenShift Online, so we will log in to the OpenShift Online console. Remember that we got an URL in an email at the beginning of this chapter (in our example, it was https://console.starter-ca-central-1.openshift.com...