Skip to content
Sunny Calculator Add-On

ADR-012 - Data Management

Statusaccepted
Date2025-04-14
Decision MakersDardan Bujupaj (AX), Marc Gähwiler (AX), Markus Brenner (Griesser)

Context

The Sunny Calculator will work with different data surrounding each the quotes to be calculated. Most data will be read from existing APIs and also written there. Some data needs to be stored in the context of the currently processed offer.

We need to define data management regarding this data.

Decision

All data that can be associated with quote or position data will be stored in the CMS. The CMS will provide additional fields for storing data as needed.

Consequences

  • CMS will provide additional fields for storing data as needed
  • No backup strategy for Sunny Calculator Add-On needed right now
  • Further data for future requirements will be analyzed and other storing mechanisms will be implemented as needed

Alternatives

  • Separate Database A separate database for Sunny Calculator Add-On. Data can be stored there and synchronized with the CMS. Pros: less dependency from CMS, better latency for requests. Cons: immense operational and implementation complexity.

  • In-Memory Store (e.g., Redis Cache) Fast and simple for ephemeral data. Pros: low latency for transient data. Cons: not suitable for durable storage, adds operational complexity. Not needed right now, but can be considered as caching data data becomes relevant.