Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Kotlin Design Patterns and Best Practices

You're reading from   Kotlin Design Patterns and Best Practices Elevate your Kotlin skills with classical and modern design patterns, coroutines, and microservices

Arrow left icon
Product type Paperback
Published in Apr 2024
Publisher Packt
ISBN-13 9781805127765
Length 474 pages
Edition 3rd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Alexey Soshin Alexey Soshin
Author Profile Icon Alexey Soshin
Alexey Soshin
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Section 1: Classical Patterns FREE CHAPTER
2. Getting Started with Kotlin 3. Working with Creational Patterns 4. Understanding Structural Patterns 5. Getting Familiar with Behavioral Patterns 6. Section 2: Reactive and Concurrent Patterns
7. Introducing Functional Programming 8. Threads and Coroutines 9. Controlling the Data Flow 10. Designing for Concurrency 11. Section 3: Practical Application of Design Patterns
12. Idioms and Anti-Patterns 13. Practical Functional Programming with Arrow 14. Concurrent Microservices with Ktor 15. Reactive Microservices with Vert.x 16. Assessments
17. Other Book You May Enjoy
18. Index

Routing requests

Notice that no matter which URL we specify, we always get the same result. Of course, that’s not what we want to achieve. Let’s start by adding the most basic endpoint, which will only tell us that the service is up and running:

fun main() {
    val vertx = Vertx.vertx()
    vertx.createHttpServer().requestHandler{ ctx ->
        ctx.response().end("OK")
    }.listen(8081)
    println("open http://localhost:8081")
}

This code is designed to produce the same response for any type of request, whether it’s a GET or POST, and irrespective of the URL. Typically, this isn’t the desired behavior. In REST architecture, it’s common practice to define distinct paths for various actions. To facilitate this, we’ll employ the Router. The Router enables the definition of specific handlers for different HTTP methods and URLs.

Now, let’s add a /status endpoint that will return an HTTP status code...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image