docs: adapt state management pattern according to moving flux to on hold
This commit is contained in:
committed by
Stefan Rotsch
parent
e773f6e512
commit
85742a72c3
16
radar/2023-09-01/state-management-pattern.md
Normal file
16
radar/2023-09-01/state-management-pattern.md
Normal file
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: "State Management Pattern"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
tags: [architecture, coding]
|
||||
---
|
||||
|
||||
State Management is a design pattern with the goal of properly sharing state data across components and separating domain representation from state management.
|
||||
This pattern is applied by many popular web frameworks such as [Vuex](/languages-and-frameworks/vuex.html) or [Redux](/languages-and-frameworks/redux.html).
|
||||
|
||||
Especially in [reactive](/methods-and-patterns/reactive-programming.html) systems, this pattern helps to solve the task of maintaining decoupled, stateless components with immutable data.
|
||||
The ways of implementing state management differs and depends on the specific requirements of the application at hand.
|
||||
|
||||
For distributed backend systems one might want to utilize [Akka's](/languages-and-frameworks/akka.html) cluster sharding module to elastically manage domain object states.
|
||||
|
||||
We use the various state management patterns across most [Vue](/languages-and-frameworks/vue.html) and [React](/languages-and-frameworks/react.html) projects that warrant them.
|
||||
Reference in New Issue
Block a user