Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Learning Concurrent Programming in Scala
  • Table Of Contents Toc
Learning Concurrent Programming in Scala

Learning Concurrent Programming in Scala

By : Aleksandar Prokopec
4.7 (10)
Buy this Book
close
close
Learning Concurrent Programming in Scala

Learning Concurrent Programming in Scala

4.7 (10)
By: Aleksandar Prokopec
Buy this Book

Overview of this book

This book is a must-have tutorial for software developers aiming to write concurrent programs in Scala, or broaden their existing knowledge of concurrency. This book is intended for Scala programmers that have no prior knowledge about concurrent programming, as well as those seeking to broaden their existing knowledge about concurrency. Basic knowledge of the Scala programming language will be helpful. Readers with a solid knowledge in another programming language, such as Java, should find this book easily accessible.
Table of Contents (11 chapters)
close
close
close
Preface
Icon
Preface
Icon
How this book is organized
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Introduction
Icon
1. Introduction
Icon
Concurrent programming
Icon
The advantages of Scala
Icon
Preliminaries
Icon
Summary
Icon
Exercises
2
2. Concurrency on the JVM and the Java Memory Model
Icon
2. Concurrency on the JVM and the Java Memory Model
Icon
Processes and Threads
Icon
Monitors and synchronization
Icon
Volatile variables
Icon
The Java Memory Model
Icon
Summary
Icon
Exercises
3
3. Traditional Building Blocks of Concurrency
Icon
3. Traditional Building Blocks of Concurrency
Icon
The Executor and ExecutionContext objects
Icon
Atomic primitives
Icon
Lazy values
Icon
Concurrent collections
Icon
Creating and handling processes
Icon
Summary
Icon
Exercises
4
4. Asynchronous Programming with Futures and Promises
Icon
4. Asynchronous Programming with Futures and Promises
Icon
Futures
Icon
Promises
Icon
Futures and blocking
Icon
The Scala Async library
Icon
Alternative Future frameworks
Icon
Summary
Icon
Exercises
5
5. Data-Parallel Collections
Icon
5. Data-Parallel Collections
Icon
Scala collections in a nutshell
Icon
Using parallel collections
Icon
Caveats of parallel collections
Icon
Using parallel and concurrent collections together
Icon
Implementing custom parallel collections
Icon
Alternative data-parallel frameworks
Icon
Summary
Icon
Exercises
6
6. Concurrent Programming with Reactive Extensions
Icon
6. Concurrent Programming with Reactive Extensions
Icon
Creating Observable objects
Icon
Composing Observable objects
Icon
Rx schedulers
Icon
Subjects and top-down reactive programming
Icon
Summary
Icon
Exercises
7
7. Software Transactional Memory
Icon
7. Software Transactional Memory
Icon
The trouble with atomic variables
Icon
Using Software Transactional Memory
Icon
Composing transactions
Icon
Retrying transactions
Icon
Transactional collections
Icon
Summary
Icon
Exercises
8
8. Actors
chevron up
Icon
8. Actors
Icon
Working with actors
Icon
Communication between actors
Icon
Actor supervision
Icon
Remote actors
Icon
Summary
Icon
Exercises
9
9. Concurrency in Practice
Icon
9. Concurrency in Practice
Icon
Choosing the right tools for the job
Icon
Putting it all together – a remote file browser
Icon
Debugging concurrent programs
Icon
Summary
Icon
Exercises
10
Index
Icon
Index

Actor supervision

When studying the actor life cycle, we said that top-level user actors are by default restarted when an exception occurs. We now take a closer inspection at how this works. In Akka, every actor acts as a supervisor for its children. When a child fails, it suspends the processing messages, and sends a message to its parent to decide what to do about the failure. The policy that decides what happens to the parent and the child after the child fails is called the supervision strategy. The parent might decide to do the following:

  • Restart the actor, indicated with the Restart message

  • Resume the actor without a restart, indicated with the Resume message

  • Permanently stop the actor, indicated with the Stop message

  • Fail itself with the same exception, indicated with the Escalate message

By default, the user guardian actor comes with a supervision strategy that restarts the failed children access. User actors stop their children by default. Both supervision strategies can be overridden...

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.
Learning Concurrent Programming in Scala
End of Section 8
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist 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
Order Page Read Now

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