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)

Path and request parameters

Now that we have an understanding of how we can return data in a controller, we should learn how we can ask for a particular resource so we can filter the information and return it as a response. In RESTful APIs, when an application invokes our services for a particular resource, it will query through the URL path, the desired information to be returned.

For example, if an application invokes our API with the URL /customer/1, it is indicating that the resource that has been queried is a particular customer 1 in this example.

But RESTful APIs also allow us to extend a request further providing additional information through parameters.

An application could invoke our API using the URL /customers, indicating the need to receive the customer list. But that URL could provide an additional parameter to specify a filter, for example, to search customers by...