[nathanmarz]

There can be a lot of integration pain when implementing event sourcing and materialized views by combining individual tools together. However, these are all integrated in Rama, so there's nothing you have to glue yourself as a developer. For example, using the Clojure API here's how you declare a depot (an event log):

(declare-depot setup *my-events (hash-by :user-id))

That's it, and you can make as many of those as you want. And here's how a topology (a streaming computation that materializes indexes based on depots) subscribes to that depot:

(source> my-events :> *data)

If you want to subscribe to more depots in the topology, then it's just another source> call.

That these are integrated and colocated also means the performance is excellent.

[archarios]

This is what has me excited about Rama. I was very into the idea of event sourcing until I realized how painful it would be to make all the tooling needed.

[westhanover]

I don't care about HN rules, this is an astroturfing account. Don't believe anything it posts about RAMA.

[sroussey]

Examples should be in: PHP, NodeJS/Typescript, Python.

Seeing Closure ironically makes me think of Twitter though.

[archarios]

well it's either going to be Java or Clojure with this framework so those examples would be kind of pointless.

[sroussey]

So most apps… are pointless to use with this tool? That’s definitely a reason to stick with Postgres.