Book Image

Scala Design Patterns

By : Ivan Nikolov
Book Image

Scala Design Patterns

By: Ivan Nikolov

Overview of this book

Scala has become increasingly popular in many different IT sectors. The language is exceptionally feature-rich which helps developers write less code and get faster results. Design patterns make developer’s lives easier by helping them write great software that is easy to maintain, runs efficiently and is valuable to the company or people concerned. You will learn about the various features of Scala and be able to apply well-known, industry-proven design patterns in your work. The book starts off by focusing on some of the most interesting features of Scala while using practical real-world examples. We will also cover the popular "Gang of Four" design patterns and show you how to incorporate functional patterns effectively. By the end of this book, you will have enough knowledge and understanding to quickly assess problems and come up with elegant solutions.
Table of Contents (20 chapters)
Scala Design Patterns
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
Index

Components in Scala


Components are parts of an application that are meant to be combined with other parts of the application. They should be reusable in order to achieve less code duplication. Components typically have interfaces, which describe the services they provide and a number of services or other components they depend on.

In large applications, we usually see multiple components that are integrated to work together. Describing the services that a component provides is usually straightforward, and it is done with the help of interfaces. Integrating other components, however, could sometimes require a developer to do extra work. This is usually done by passing the interface of the requirement as a parameter. However, imagine a large application in which we might have a lot of requirements; wiring things up could take time and effort. Moreover, every time a new requirement comes up, we would have to do quite a lot of refactoring. An alternative to parameters is multiple inheritance...