Skip to main content

Overview

This chapter is the third category, following "Optimization" and "Testing."
geajs does not enforce React-style unidirectional data flow or state management libraries. And since Store is simply a class, where it is placed, how it is connected, and its granularity are left entirely up to the developer. That is precisely why accidents are likely to occur, and guidelines are necessary.

Questions Addressed in This Category​

  • At what level of granularity should a Store be created, and where should it be placed?
  • How should multiple Stores be coordinated?
  • What should you keep in mind when creating a custom mechanism for handling Stores by reference?
info

Store design decisions in this chapter are discussed independently of the compiler's optimization tiers covered in Component Tiers. We recommend reading that page first, since some of the terminology (e.g., "1 File, 1 Store") is reused here.