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.
Workshop: Show me the Kubernetes
Featuring Lewis Denham-Parry and Salman Iqbal
You’ve heard about it, read the book and listened to the talk, but have you actually used Kubernetes? In this workshop, you will be getting hands-on with Kubernetes to learn the fundamentals of what you use.architecture kubernetes microservices
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
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
Lightning Talk: Don't Rebuild your Monolith!
Featuring Peter Anning
Peter will tell you a real life story from the trenches of Microservice implementation. This journey will take you from the decomposition of a Monolith to its eventual reconstruction.architecture lesson-learned monolith microservice
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
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
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
Leveraging Metamodels and DCI to Build Modular Monoliths
Featuring Dan Haywood
In your typical "big-ball-of-mud" monolith, both (horizontal) layers and (vertical) subdomains become intertwined. Architectural constraints are needed to prevent this from happening. Microservices is one way to enforce those constraints, but if what you're really struggling with is...modular-monoliths metamodels microservices architecture ddd