The release of Eventide v2 was a hurdle of breaking changes to the message store and its supporting libraries, and the extraction of Message DB. Now that we’re past the v2 hurdle, look out for exciting new features coming to the Eventide stack. »
Eventide Project Team
Product, Roadmap, Plan
The Eventide Project team is excited to announce Message DB: A fully-featured event store and message store implemented in PostgreSQL for pub/sub, event sourcing, and evented microservices applications. »
Eventide Project Team
Release, Product
We’re super excited to announce that Eventide v2 has been released! Eventide has been in production for five years now, and open-sourced for four years. The v2 release marks a major leap forward for the toolkit and opens the door for exiting new features coming in the v2 generation of the stack. »
Eventide Project Team
Release, Product
The Eventide Project has been recognized for Social Impact by the 2019 Fukuoka Ruby Awards. If there's one thing the Eventide community would want to be recognized for, it's indeed social impact. It's something that we are 100% committed to. To be recognized for it is more meaningful than we can say. »
Eventide Project Team
Ruby, Community
A good sign of a technology’s vitality is the appearance of clones and ports to other platforms. It’s compelling not only to the users of its native environment, but is also attracting users from other platforms. And when those users return to their home environments, they spread the word. The Eventide Project isn’t exactly taking the tech world by storm, but it is inspiring some porting activity. And we’ve made some structural changes to the toolkit to enable this work. »
Eventide Project Team
MessageStore, Ecosystem, NodeJS
The Eventide Project has released a breaking change update to the message store library and the message store Postgres library that all users should be aware of, but that few users will be affected by. »
Eventide Project Team
The v2 generation of Eventide is on the horizon. Here are the notable changes coming: »
Eventide Project Team
Allowing a service to terminate is the most common course of action to take when an unexpected error is encountered. The key word here is unexpected. »
Scott Bellware
Microservices, Error Handling, Event Sourcing, SOA, Programming
One word best sums up error handling in services: Don’t. »
Scott Bellware
Error Handling, Microservices, Software Architecture, Software Engineering, Programming
The Eventide toolkit supports two backend database implementations of its message store: Postgres and Event Store. »
Scott Bellware
SQL, Event Sourcing, Microservices, Postgres, EventStore
