Robby RussellWho would you love to hear me talk shop with on @maintainable
Be Kinder Than NecessaryScott Bellware (@sbellware) and/or Nathan Ladd (@ntl) from Eventide.
Nathan Ladd@dcrossney I appreciate this, Damian!
@ntl My pleasure! I've been learning a lot about event sourcing lately and loving it!
I think I've watched all of the conference videos you and Scott have done, plus read through the Eventide docs.
It's starting to click, I think, but I want to learn more. You might say this was a poke in your direction too. 🤓
@jardo @deadcode has done a great job of exploring ideas and approaches that are underappreciated in the Ruby world. Eventide is an idea that needs more attention, IMO.
@ntl Can I ask what's been happening with Eventide? There are indications in the docs that more examples would be forthcoming.
I want to look at ways to integrate Eventide with Hanami. I know that goes against the grain of fully autonomous services, but I think there's a rich area of application there, with a modular approach to architecture that's difficult to achieve with Rails.
Finally, how would one go about looking for work in roles that use Eventide? 🤔
@dcrossney yes, indeed! We have a sizeable set of incremental improvements we aim to introduce in the next generation, and we hope to carve off dedicated time to work on it soon. It also competes with client work for our time (same old story for every open source project that's reached stability :)
Interesting re. Hanami! We tend to use Rails for web applications (they exist aplenty in our architectural style!), but Hanami should be simple to integrate with.. I'd be curious to see the outcome..
@dcrossney at the moment, there are some open positions. Feel free to send me an email: [email protected]
I'd love to schedule a call!
@ntl That's amazing! Give me a bit to gather my thoughts and I'll reach out. Thank you.
@ntl In a few of the talks I saw by you and Scott he said that microservices (or autonomous services) are not a natural evolution of monoliths.
But in one of the talks I remember that he showed a car that could split into two motorcycles and he said: unless they were designed that way from the start.
That's kind of what brought me around to event sourcing. I'm interested in using modularity patterns within monoliths, and Hanami seems better suited for that than Rails.
@ntl I'm thinking that modularity patterns will allow you to experiment more with evolving boundaries between "services," and might have lower overhead as well.
I started looking at event sourcing because it stands out as the communication protocol between services with its power and resiliency while maintaining service autonomy.
The problem is that event sourcing is like a mind virus--once you dip your head in, it's hard to look at statically modeled systems the same way ever again. 🥴