Event Store is the stream database for Event Sourcing.
Event sourcing is persisting changes to state as an ordered sequence of events. Current state can be calculated from those events.
Event Store is a database to store your data as a series of immutable events over time, making it easy to build event-sourced applications.
Whilst performance depends on configuration and use patterns, we've benchmarked Event Store at around 15000 writes per second and 50000 reads per second!
Event Store can run as a cluster of nodes containing the same data, which remains available for writes provided at least half the nodes are alive and connected
Event Store is licensed under 3-clause BSD license, whether is runs on a single node or as a high availability cluster. Commercial offers are available in case official support is required.
Event Store is platform and language independent. It has a native HTTP interface and there are native drivers for .NET, Java and other languages.
Oops, I DDD it Again (and Again)
Featuring Ora Egozi-Barzilai
Using DDD for mapping a company’s core domain is quite known and one can find many case studies on that, but case studies for merging or re-dividing domains upon acquisition are harder to find.culture boundedcontexts sociotechnical strategic-ddd architecture conways-law merge-domains autonomous-teams
Awesome CI/CD Data Pipelines for Distributed Data-Sources
Featuring Chris Burrell
The foundational principle of microservices is to segregate functionality into abstracted units. What if you want to empower your business with self-service access to almost every data source?architecture greater-expectations dbt stitch apache-spark aws glue redshift looker elt etl data-architecture microservices testing robust build pipeline data
The Dark Side Of Events
Featuring Vladik Khononov
Events are your industry’s near and dear. All technological conferences are full of talks on event sourcing, event driven architectures, or event driven integrations. So hey, why not make another one? …But a bit different: Let’s talk about the dark side of this pattern. Events, as any tool, can...architecture microservices event-sourcing event-driven-architecture events
Event Driven Collaboration
Featuring Ian Cooper
When you move from a monolith to microservices you abandon integrating via a shared database, as each service must own its own data to allow them it to be autonomous. But now you have a new problem, our data is distributed.event-driven-collaboration architecture microservices
A Hitchhikers Guide to Improving Observability in a Hybrid Universe
Featuring Alex Close
The goal of designing and building Observable systems is to make sure that when they run in production, developers and operators can detect undesirable behaviour and have actionable information to pin down root cause. As teams move more applications to Cloud the importance of having a Strategy of...observability microservices architecture observable-systems
What Do You Mean I Can’t Google It? - Search for Microservices
Featuring Heather Whyte
Google is an amazing tool, and let’s be honest, it has helped to build most of the software you’ve ever worked on. But when you are able to look up “that basketball dog movie” or “111th element” without having to recall cheesy 90s movie titles or knowing how to spell Roentgenium - people’s...implementation-options architecture event-driven microservices search
Keynote: Microservices & Containers: Getting your Security Team on Board
Featuring Liz Rice
At first glance, moving to microservices and containers can look like a threat to security.architecture keynote microservices
18 Heuristics to Discover your Contexts Boundaries
Featuring Cyrille Martraire
Microservices need DDD absolutely. Bounded Contexts, a key DDD ingredient, are the tool of choice to define services boundaries that won’t end up in a complete disaster at runtime and at deploy time.architecture domainlanguage domains servicesboundaries ddd boundedcontexts