Description
Lightweight implementation, succinct data models, fast command processing, in-memory and on-disk indexing, causality-preserving hybrid logical clocks, locking primitives and OSGi support out of the box.
Instead of mutating data in a database, it stores all changes (events) and causes (commands). This facilitates rapid application development and evolution by mitigating the inability to predict how future needs will drive data shape requirements as all causal information is persisted. It also provides a foundation for deep analytics, data recovery, audit trails and other associated benefits.
Eventsourcing for Java alternatives and similar libraries
Based on the "Database" category
-
orientdb
OrientDB is the first Multi-Model DBMS with Document & Graph engine. OrientDB can run distributed (Multi-Master), supports SQL, ACID Transactions, Full-Text indexing, Reactive Queries and has a small memory footprint. OrientDB is licensed with Apache 2 license and the development is driven by OrientDB LTD and a worldwide Open Source community. -
MapDB
Embedded database engine that provides concurrent collections backed on disk or in off-heap memory. -
Crate
Distributed data store that implements data synchronization, sharding, scaling, and replication. In addition, it provides a SQL-based syntax to execute queries across a cluster. -
requery
A modern, lightweight but powerful object mapping and SQL generator. Easily map to or create databases, perform queries and updates from any platform that uses Java. -
sql2o
Thin JDBC wrapper that simplyfies database access and provides simple mapping of ResultSets to POJOs. -
JetBrains Xodus
JetBrains Xodus is a Java transactional schema-less embedded database used by JetBrains YouTrack and JetBrains Hub. -
MariaDB4j
Launcher for MariaDB which requires no installation or external dependencies. -
Liquibase
Database-independent library for tracking, managing and applying database schema changes.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of Eventsourcing for Java or a related project?
README
Eventsourcing for Java
Enabling plurality and evolution of domain models
Instead of mutating data in a database, Eventsourcing stores all changes (events) and what caused them (commands). To make this data useful, Eventsourcing builds indices over it.
This helps developing applications faster because there is no need to worry about designing the right domain models upfront (or as close to right as possible). By keeping all the commands and events, we can enrich or change our domain models over time with very little friction. Furthermore, this approach removes a need to have a one and only domain model for every entity. We experience the world and reality in different ways, depending on circumstances and points of view, and our programs should be able to reflect that.
To learn more about what kind of problems ES4J addresses, please read Why Use Eventsourcing Database
Key benefits
- Domain model flexibility
- Late domain model binding
- Persistence of causal information
- Serializable conflict resolution
- Audit trail logging
- Mapping application functionality
Key features
- Strongly typed schemas
- Event migrations
- Domain protocols
- Batteries included (shared event languages)
- Basic support for Kotlin
- Causality-preserving Hybrid Logical Clocks
- In-memory and server (PostgreSQL) storage
- Locking synchronization primitive
- JMX-based introspection and management
Presentation
You can find our current slide deck at https://eventsourcing.com/presentation
Downloading and installing
To start using ES4J, please follow the installation instructions.
Documentation
Documentation can be found at es4j.eventsourcing.com
We strive to specify the building blocks behind Eventsourcing and its ecosystem as succinct specifications, you can find the current list of them at rfc.eventsourcing.com
Roadmap
As this project is striving to be a decentralized, contributors-driven project governed by the C4 process, there is no central roadmap per se. However, there's a centralized list of reported issues. These do not imply an actual roadmap, just what has been reported, ranging from bugs to longer-term design issues.
Contributing
Contributions of all kinds (code, documentation, testing, artwork, etc.) are highly encouraged. Please open a GitHub issue if you want to suggest an idea or ask a question.
We use Unprotocols C4 process. In a nutshell, this means:
- We merge pull requests rapidly (try!)
- We are open to diverse ideas
- We prefer code now over consensus later
For more details, please refer to [CONTRIBUTING](CONTRIBUTING.md)
Related projects
- es4j-graphql A Relay.js/GraphQL adaptor for ES4J-based applications.