Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Kotlin Design Patterns and Best Practices
  • Table Of Contents Toc
Kotlin Design Patterns and Best Practices

Kotlin Design Patterns and Best Practices - Second Edition

By : Alexey Soshin
4.5 (13)
close
close
Kotlin Design Patterns and Best Practices

Kotlin Design Patterns and Best Practices

4.5 (13)
By: Alexey Soshin

Overview of this book

This book shows you how easy it can be to implement traditional design patterns in the modern multi-paradigm Kotlin programming language, and takes you through the new patterns and paradigms that have emerged. This second edition is updated to cover the changes introduced from Kotlin 1.2 up to 1.5 and focuses more on the idiomatic usage of coroutines, which have become a stable language feature. You'll begin by learning about the practical aspects of smarter coding in Kotlin, as well as understanding basic Kotlin syntax and the impact of design patterns on your code. The book also provides an in-depth explanation of the classical design patterns, such as Creational, Structural, and Behavioral families, before moving on to functional programming. You'll go through reactive and concurrent patterns, and finally, get to grips with coroutines and structured concurrency to write performant, extensible, and maintainable code. By the end of this Kotlin book, you'll have explored the latest trends in architecture and design patterns for microservices. You’ll also understand the tradeoffs when choosing between different architectures and make informed decisions.
Table of Contents (17 chapters)
close
close
1
Section 1: Classical Patterns
6
Section 2: Reactive and Concurrent Patterns
11
Section 3: Practical Application of Design Patterns

Understanding Kotlin code structure

When you start programming in Kotlin, your first step is typically to create a new file, which usually has the .kt extension.

In contrast to Java, Kotlin doesn’t strictly enforce a one-to-one relationship between the filename and the class name. While you have the flexibility to include multiple public classes within a single Kotlin file, it’s generally considered best practice to group only logically related classes together in one file. Keep in mind that doing so should not make the file excessively long or difficult to read. Additionally, packing multiple public classes into a single file can make it harder to search for specific functionality, as the project overview may not display all available classes.

Naming conventions

As a convention, if your file consists of a single class, it is recommended to name your file the same as your class.

When your file contains multiple classes, the filename should describe the...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Kotlin Design Patterns and Best Practices
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon