Understand traditional GOF design patterns to apply generic solutions
Shift from OOP to FP; covering reactive and concurrent patterns in a step-by-step manner
Choose the best microservices architecture and MVC for your development environment
Book DescriptionDesign patterns enable you as a developer to speed up the development process by providing you with proven development paradigms. Reusing design patterns helps prevent complex issues that can cause major problems, improves your code base, promotes code reuse, and makes an architecture more robust.
The mission of this book is to ease the adoption of design patterns in Kotlin and provide good practices for programmers.
The book begins by showing you the practical aspects of smarter coding in Kotlin, explaining the basic Kotlin syntax and the impact of design patterns. From there, the book provides an in-depth explanation of the classical design patterns of creational, structural, and behavioral families, before heading into functional programming. It then takes you through reactive and concurrent patterns, teaching you about using streams, threads, and coroutines to write better code along the way
By the end of the book, you will be able to efficiently address common problems faced while developing applications and be comfortable working on scalable and maintainable projects of any size.
What you will learn
Get to grips with Kotlin principles, including its strengths and weaknesses
Understand classical design patterns in Kotlin
Explore functional programming using built-in features of Kotlin
Solve real-world problems using reactive and concurrent design patterns
Use threads and coroutines to simplify concurrent code flow
Understand antipatterns to write clean Kotlin code, avoiding common pitfalls
Learn about the design considerations necessary while choosing between architectures
Who this book is forThis book is for developers who would like to master design patterns with Kotlin to build efficient and scalable applications. Basic Java or Kotlin programming knowledge is assumed