goloroden

8 ms·

121.
by goloroden 1y ago
Just a little hint: Read the other comments as well…
122.
by goloroden 1y ago
Hi there, I’m one of the creators of EventSourcingDB, and the CTO of the native web (the company behind EventSourcingDB). Because of ongoing legal investigations I can’t comment any further, but I’d like to provide you with some links, so y
123.
Fun with TypeScript
2 points by goloroden 1y ago|0 comments
124.
by goloroden 1y ago
I think I’d call what Tesla did fraud. Or scam. Or both.
125.
An event store that natively supports Dynamic Consistency Boundaries (DCBs)(docs.eventsourcingdb.io)
1 points by goloroden 1y ago|0 comments
126.
EventSourcingDB – Git for your data, with time travel and AI-ready history(hub.docker.com)
2 points by goloroden 1y ago|0 comments
127.
Show HN: OpenCQRS – A new CQRS framework for JVM developers(github.com)
3 points by goloroden 1y ago|0 comments
128.
Show HN: Rethink How You Build AI-Driven Systems(eventsourcing.ai)
3 points by goloroden 1y ago|0 comments
129.
Show HN: Rethink How You Build Software(cqrs.com)
1 points by goloroden 1y ago|0 comments
130.
OpenCQRS – The lightweight CQRS and event sourcing framework for the JVM(github.com)
1 points by goloroden 1y ago|0 comments
131.
Show HN: Learn what CQRS, Event Sourcing and co. Are all about(cqrs.com)
2 points by goloroden 1y ago|1 comments
132.
Stop Guessing: Use Event Sourcing to Feed Your AI the Right Data(eventsourcing.ai)
1 points by goloroden 1y ago|0 comments
133.
Show HN: Event Sourcing and AI(eventsourcing.ai)
4 points by goloroden 1y ago|1 comments
134.
CQRS and Event Sourcing(cqrs.com)
3 points by goloroden 1y ago|0 comments
135.
OpenCQRS – an open-source CQRS framework for the JVM(github.com)
5 points by goloroden 1y ago|1 comments
136.
A database purpose-built for audit logs, time-travel and replayable workflows(hub.docker.com)
2 points by goloroden 1y ago|0 comments
137.
Show HN: A database specialized in Event Sourcing(thenativeweb.io)
1 points by goloroden 1y ago|0 comments
138.
by goloroden 1y ago
It’s not even 2 lines: 1. Type definition 2. Chain definition 3. Enqueue definition
139.
by goloroden 1y ago
I „solved” it by ignoring a part of the problem? Please don’t take this personal, but IMHO that’s not solving the problem. That’s coming up with a workaround.
140.
Cqrs.com(cqrs.com)
3 points by goloroden 1y ago|0 comments
141.
Tom Scott is not back yet, but he's looking for where to go next [video](youtube.com)
1 points by goloroden 1y ago|0 comments
142.
Show HN: Rethink How You Build Software(cqrs.com)
1 points by goloroden 1y ago|0 comments
143.
We built a dedicated event store – here's why Kafka and Postgres weren't enough(docs.eventsourcingdb.io)
1 points by goloroden 1y ago|1 comments
144.
by goloroden 1y ago
After years of building systems with CQRS and event sourcing, we kept running into the same roadblocks: Missing concurrency control, unreliable ordering, complex snapshotting, no native replays. So we built a database purpose-built for even
145.
We Built a Database Just for Event Sourcing (EventSourcingDB)(hub.docker.com)
1 points by goloroden 1y ago|0 comments
146.
We Created a New Database from Scratch(docs.eventsourcingdb.io)
2 points by goloroden 1y ago|0 comments
147.
EventQL: A Query Language for Events(docs.eventsourcingdb.io)
11 points by goloroden 1y ago|2 comments
148.
EventSourcingDB 1.0 Released(thenativeweb.io)
1 points by goloroden 1y ago|0 comments
149.
A New Database for Event Sourcing(docs.eventsourcingdb.io)
4 points by goloroden 1y ago|0 comments
150.
EventSourcingDB – new database for event sourcing(thenativeweb.io)
4 points by goloroden 1y ago|2 comments

More ›