Weronika Łabaj
Weronika Łabaj
It's not clear how events are stored (e.g. in a single table? table per event type?). It'd be useful to have such information, for example here https://railseventstore.org/docs/repository/ or in the...
It'd be useful to have a brief glossary/concepts overview in the getting started section, e.g. containing definitions of what event vs command is, what stream is, what is projection, etc....
Currently, in the documentation there's no information about how streams are implemented under the hoods, nor are there any design guidelines. That kind of information would be useful to understand...
https://railseventstore.org/docs/projection/ It's not clear whether projections are in-memory, calculated ad-hoc/at project startup or are somehow persisted. However, having such information would be helpful to understand when to use them.
It currently is hard to decommission an endpoint. We have the manual Unsubscribe API but that requires users to (a) don't have a handler for that type or (b) to...
In versions 12.2 and above the max name length is 128 bytes ([source](https://stackoverflow.com/questions/756558/what-is-the-maximum-length-of-a-table-name-in-oracle)), but we always assume the max length is 30 bytes (as in Oracle 12.1 and below).
Add a sample covering solution with business data stored in Marten and SQL persistence using Postgres. Has to wait until marten [can support re-using an existing connection and transaction](https://github.com/JasperFx/marten/issues/905).
- ensure indexes are used, etc. - similar to what was done for Oracle by @DavidBoike @MarcinHoppe