Abstract
At some point, services need to work with state. The way for persisting the state marks out how scalable they are going to be. In this chapter, I will walk you through a brief introduction to what is the difference between stateful and stateless services and what are the challenges for scaling them. As it typically happens, when you don’t want to incorporate some functionality in your code, you use an external service that provides the functionality you need out of the box. You will learn how Dapr helps you persist the state of your services by leveraging external state stores. When you make it to the point to persist data of a distributed application, you must think over two important traits – concurrency and consistency. Once I cover how the State Management building block works, I will go through the state stores that are supported by Dapr. I will also touch on how the Actors building block that I am going to cover in Chapter 10: The Actor Model relies upon state management.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2021 The Author(s), under exclusive license to APress Media, LLC, part of Springer Nature
About this chapter
Cite this chapter
Gatev, R. (2021). State Management. In: Introducing Distributed Application Runtime (Dapr). Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-6998-5_8
Download citation
DOI: https://doi.org/10.1007/978-1-4842-6998-5_8
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-6997-8
Online ISBN: 978-1-4842-6998-5
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)