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.
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
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
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
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
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
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
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