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
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

State

You can think of the State design pattern as a more opinionated version of the Strategy pattern we discussed earlier in this chapter. However, there’s a crucial difference: while the Strategy pattern is typically changed from the outside by the client, the state can change internally based solely on the input it receives.

Consider this dialogue a client has with the Strategy pattern:

Client: “Here’s a new thing to do, start doing it from now on.”

Strategy: “OK, no problem.”

Client: “What I like about you is that you never argue with me.”

Now, compare it with this dialogue:

Client: “Here’s some new input I got for you.”

State: “Oh, I don’t know. Maybe I’ll start doing something differently. Maybe not.”

The client should also be prepared for the state to possibly reject some of its inputs:

Client: “Here’s something for you to...

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