-
This is a design exploration of composability / orchestration patterns.
Resources as context
1. "`COMPOSABLE EVENT SOURCING WITH MONADS`"
http://www.lambdadays.org/static/upload/media/151972446…
-
This is both a question/request. One of the requirements of event sourcing application is projection/subscription to create read models.
Could edgedb provide mechanism to subscribe from a specific …
-
Ideally when new market events are received to the instance as well as when events are sent externally they should be persisted. For this it will be good to have an Event Store to persist the data. Th…
-
-
Event Sourcing is really only about persistence. You persist a sequence of events/facts which you use to derive the state of your model instead of mutating and persisting the state itself. That’s real…
-
Benefits of event sourcing:
* Implicitly audited
* Data "versioning"
* Data evolution follows code evolution
-
TODOS
---
- [ ] Update prisma.schema
- [ ] Seed some events, according to existing seed data
- [ ] Query events on single Artwork Page
- [ ] Query events on single User Page
- [ ] Create the e…
-
https://milestone.topics.it/categories/view-model-composition
- [x] What is Services ViewModel Composition, again?
https://milestone.topics.it/view-model-composition/2019/02/06/what-is-services-vi…
-
Implement one! Event sourcing & CQRS application
-
- Make use of built-in event store + repository.
- Consolidate interface.
- Add warning about `id` field that should be use (maybe even require implementing an abstract method after all).