Apache Ignite
Event Store
| Apache Ignite | Event Store | |
|---|---|---|
| 3 | 5 | |
| 4,686 | 5,091 | |
| 0.4% | 0.8% | |
| 9.5 | 9.5 | |
| 7 days ago | 1 day ago | |
| Java | C# | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Apache Ignite
-
Ask HN: P2P Databases?
Ignite works as you describe:
https://ignite.apache.org/
I wouldn't really recommend this approach, I would think more in terms of subscriptions and topics and less of a 'database'.
-
Which library/project do you wish was ported to golang?
Apache Ignite https://ignite.apache.org/
-
.NET and Apache Ignite: Testing Cache and SQL API features — Part I
Last days, I started using Apache Ignite as a cache strategy for some applications. Apache Ignite is an open-source In-Memory Data Grid, distributed database, caching, and high-performance computing platform.
Event Store
-
Event Store State of the Art
I've been doing some research and found this: https://github.com/EventStore/EventStore
-
if you had to restart at 0 knowledge what would you do?
C#: In Europe, Java is still strong but many trading firms use C# because of the strong Microsoft culture in Europe, as well as because of strongly supported C# libraries like say EventStore, which tends to be used for the matchmaking engines for stock exchanges (especially that exchange matchmaking problem is basically SMR). And skimming over the code, it has Paxos implemented too, making it good for dealing with partial failures (failover), essential for any HFT/trading firm. C#'s also the biggest ecosystem that many of the breakthrough java tech mentioned earlier was first ported to.
- Call for Help - Open Source Datom/EAV/Fact database in Rust.
-
Event sourcing two years later (almost)
Support for eventstore.com eventstore. esdb
-
3 reasons to adopt Event Sourcing
Where's the catch, then? Well, there's a couple of catches, in fact. First of all, in a distributed setting, appending data to a log isn't that easy. First, you need to make your log distributed. Again, Kafka/Cassandra/EventStore make this possible, however, whenever you start dealing with distributed data, you‘re introducing new operational and implementation complexity.
What are some alternatives?
LiteDB - LiteDB - A .NET NoSQL Document Store in a single data file
Marten - .NET Transactional Document DB and Event Store on PostgreSQL
MongoDB - The MongoDB Database
Alluxio (formerly Tachyon) - Alluxio, data orchestration for analytics and machine learning in the cloud
Streamstone - Event store for Azure Table Storage
SqlKata Query Builder - SQL query builder, written in c#, helps you build complex queries easily, supports SqlServer, MySql, PostgreSql, Oracle, Sqlite and Firebird
Firebase.Net - C# wrapper over Firebase database REST API
Insight.Database - Fast, lightweight .NET micro-ORM
Apache Cassandra - Mirror of Apache Cassandra
Realm Xamarin - Realm is a mobile database: a replacement for SQLite & ORMs
RavenDB - ACID Document Database