49bbe281dfb9c97f10a359ad22b69ebff429ecd8
V2 - Attempt 2
Roadmap
- Complete this design document?
- Complete defining this roadmap checklist
- Website displaying an audit of store events
- Start with just a list of events for a given store (use a static test store)
- ...
Looking to follow the CQRS pattern.
The database will follow the event sourcing database pattern. All events (or commands) will be stored in a respective event series, and all database reads will be from views that are projections, reductions, aggregations of those event series.
Application/directory structure
- /internal
- /site: website
- /webhooks: webhooks for platform events
- /domains: packages for each domain
- /store_events: storing and events
- /platforms: ecommerce platform domains
- /tiktok: interface with tiktok
- ... etc
- ... etc
Architectural and Software Diagrams
Event Sourcing Architecture
Event Structure
Store Event Database Tables
All Diagrams
All diagrams are stored in the diagrams directory
Languages
Go
54.5%
PLpgSQL
16.6%
Go Template
12.2%
JavaScript
9.4%
CSS
6.8%
Other
0.5%