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)

Handling errors

Any software needs to handle errors, either triggered by the business rules that are defined or just to handle extraordinary circumstances that may appear. In RESTful APIs, we use status codes to tell our consumers when an error has occurred, but within our code, we need to handle those scenarios and ensure that they are handled gracefully. During this section, we will review some of the techniques that we could use to handle these situations.

Using controller advice

In our last example, we got an exception when our JSON was not formatted correctly. That exception was JsonParseException, and was not handled in any part of our code so Spring was automatically handling it for us and returning an error message...