Skip to content
Armagan Amcalar edited this page Aug 10, 2015 · 1 revision

A Regime is a stateful institution that deals with all the aspects of a specific purpose in an application. They breed, keep state of, and operate on Stereotypes. For complex task that would span different responsibilities, a Regime should negotiate with other Regimes, preferably over Diplomats. Although they are responsible for keeping application state of a specific purpose, Regimes don’t necessarily involve in persisting that state. For persistence, Regimes should delegate to Undertakers.

It’s worth mentioning that in very complex applications the developer may choose to implement two layers of Regimes on top of each other.

UI Applications often need to keep a global state for application life cycle management. We recommend using a GlobalRegime for this purpose.

Menu

  1. Home
  2. Common Pages
  3. Glossary
  4. FAQ
  5. Concepts & inspiration
  6. Contributors
  7. Naming conventions
  8. Goals
  9. Roles
  10. Core 1. Culture 1. Representative 1. Stereotype 1. Regime
  11. Optional 1. Undertaker 1. Satellite 1. Diplomat
  12. Contextual 1. Union
  13. Example applications
  14. Google Closure
  15. React
  16. AngularJS
  17. VanillaJS
  18. ES6
Clone this wiki locally