Eventide Blog

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

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

The v2 generation of Eventide is on the horizon. Here are the notable changes coming: »

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

One word best sums up error handling in services: Don’t. »

The Eventide toolkit supports two backend database implementations of its message store: Postgres and Event Store. »

Service architectures in Ruby, you say? Certainly services can only be built in languages like Java and Go, and require elaborate messaging transport and mass-scale storage solutions that only the biggest teams and companies can afford! »

The Eventide Project community is excited to announce the 1.0 release of Eventide: the best microservice, autonomous service, event/reactive, and event sourcing toolkit built in Ruby, and one of the best stacks available in any language! »