You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The entire application should be as stateless as possible, meaning we have a one-way writeable database of users, markets, bets and calculate all relevant states of the application from as few possible columns within those models.
We should separate the data logic from the business logic as much as possible with a Domain Driven Design (DDD), meaning we have a repository/ directory which is designed to be the central location to keep functions that extract data from the databases. This should ideally help slow the growth of the codebase over time and keep data extraction more testable, which should make our startless architecture more reliable.
The text was updated successfully, but these errors were encountered:
pwdel
changed the title
Create Data Repository Layer for More Precise Testing
Create Data Repository Layer for More Precise Testing + Documentation
Sep 9, 2024
pwdel
linked a pull request
Sep 9, 2024
that will
close
this issue
Re, data conventions in readme:
The text was updated successfully, but these errors were encountered: