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.
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
Adopting Domain Driven Design at Scale
Featuring Gayathri Thiyagarajan and Andrew Harmel-Law
For the past decade and a half, Domain Driven Design has been giving teams the tools to successfully tackle the complexity at the heart of software. But lots of people fail when they try to put its techniques and patterns into practice. Why? It can't just be because the book is so thick?architecture transformation adoption microservices ddd
Lightning Talk: Domain Model in Multi-Language Environment with Examples from Healthcare
Featuring Mufrid Krilic
The literature and resources on DDD, or software-related in general, are mostly in English. Even the domain-specific discussions are presented in English.architecture domainmodel ubiquitouslanguage ddd
Micro Frontends – A Strive for Fully Verticalized Systems
Featuring David Leitner
Microservices brought you significant benefits, which allow you to structure teams based on business capabilities, improve scalability and enable the flexibility of being polyglot. Unfortunately, these powerful architectures are often complemented by a feature-rich browser application which ends...best-practices architecture frontend-monoliths verticalized-systems
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