> Rama can build end-to-end backends at any scale on its own in a tiny fraction of the code. At its core is a new programming language implementing a new programming paradigm..
Grand claims, but where are the super powerful demo apps? The getting started docs are a trickle of info..
The "demo gallery" has a few cherry picked examples, but I don't see how this fulfills the claim of a "new paradigm". I wanted to be blown.. but this ain't it.
Check out twitter-scale-mastodon, which is an implementation of Mastodon's backend from scratch that scales to Twitter scale. It's more than 40% less code than Mastodon's backend and 100x less code than Twitter wrote to build the equivalent.
> These numbers are a bit better than Twitter’s numbers. Because of how unbalanced the social graph is, getting performance this good and this reliable is not easy. For example, when someone with 20M followers posts a status, that creates a huge burst of load which could delay other statuses from fanning out. How we handled this is described more below.
Huh. I haven't written myself a twitter, but I've always assumed that this problem is solved by a mix of fan-on-write and fan-on-read. Most people are fan-on-write, but those with a follower count > $THRESHOLD are fan-on-read.
The fan-on-read set is small enough to be easily cacheable, so the extra reads required to service a follower's feed are more than compensated for by the fact that the content is in RAM in a cache.
Sounds like RedPanda went exclusively with fan-on-write. I'd be surprised if Twitter does the same - but it sounds like OP has more knowledge about this than me, so I'm happy to be educated!
Edit: @nathanmarz that's cool you have enough interest to keep things moving with it being private. I'm only interested in open solutions for this domain, though. IMO, accepting lock-in is a lot to ask.
Best wishes ~ MD
Well there is whole bank transfer implementation there and thoroughly commented too. Some entrepreneur can take this and run with it to create next generation banking platform.
Tbf, the purpose of the blog is to talk about the power of Clojure/Lisp for defining the new paradigm, rather than the paradigm itself. Though the author then goes on to talk about "fragments" as the basis for the new paradigm.
The first sentence has a link to the project page which has most of the info you need.
The Clojure community is extremely cult like. I worked with a dev who tried to push Datomic, and despite the huge flaws with his system, and the fact that it was closed source, he would continuously tout how much better it was than a relational database. I don’t believe the hype.
You just generalized an entire community based on one person. I can add a counter anecdote to your N=1. I'm a Clojure dev. I've used and enjoyed Datomic. Postgres is still my goto database.
Is anyone using Rama at scale? This isn't a complaint about it being closed-source, people have to make their money somehow. But I've seen a lot about Rama's scale when the only things to check the claim are a private beta and a single-process dev build.
I'm super curious to hear from people who have tried it for larger projects!
> At its core is a new programming language implementing a new programming paradigm, at the same level as the “object-oriented”, “imperative”, “logic”, and “functional” paradigms... Rama generalizes the concept of a function into something called a “fragment”... a fragment can output many times (called “emitting”), can output to multiple “output streams”, and can do more work between or after emitting.
This sounds really similar to programming with observables (e.g. RxJS), is a "fragment" an even more general concept?
I used observables when I did frontend development, I found it a useful paradigm (once I got my head around the idea).
A fragment itself is a generic programming construct that serves the same purpose as a function (just more general). When used in Rama topologies, they serve a similar role as observables in terms of reacting to new data as it flows through and sending any amount of information downstream to any number of output streams.
I remember when the first time i read about Rama,
with the blog post about having duplicated Twitter scale
at 100x code or some such.
Which all in all, if you have built a platform/runtime/language
and you pick one particular example to highlight it, being able
to achieve XXXX% less than is trivial.
I was curious about all the bluster then,
Seeing this post I am somewhat disappointed that there does not
appear to have been a lot of visible progression.
But I guess it is still running semi stealth in private beta.
Indeed, we're in private beta and aren't publicizing much about what we're doing. We'll eventually be releasing many case studies on how our private beta users are using Rama.
I think we've spent a lot of time looking at backend and frontend web app development as separate. In my work, TRPC (https://trpc.io/) solved this. I hope others in different frameworks find a similar solution soon.
From just thinking about the architecture of Rama I feel it would scale very well.
Data parallelism and partitioning and sharding is a very effective scaling technique.
Nathan, I would appreciate writings about the mental model of mapping software to your mental model of implementing behaviours in the streaming data approach because it is a different paradigm.
I can't read the DSL yet and know what is going on!
The best documentation on the mental model of using Rama is the last page of the tutorial, linked below. However, I would recommend going through the whole tutorial rather than starting there.
Grand claims, but where are the super powerful demo apps? The getting started docs are a trickle of info..
https://redplanetlabs.com/docs/~/operating-rama.html#_access...
The "demo gallery" has a few cherry picked examples, but I don't see how this fulfills the claim of a "new paradigm". I wanted to be blown.. but this ain't it.
https://github.com/redplanetlabs/rama-demo-gallery
Oof.
https://github.com/redplanetlabs/twitter-scale-mastodon
https://blog.redplanetlabs.com/2023/08/15/how-we-reduced-the...
Huh. I haven't written myself a twitter, but I've always assumed that this problem is solved by a mix of fan-on-write and fan-on-read. Most people are fan-on-write, but those with a follower count > $THRESHOLD are fan-on-read.
The fan-on-read set is small enough to be easily cacheable, so the extra reads required to service a follower's feed are more than compensated for by the fact that the content is in RAM in a cache.
Sounds like RedPanda went exclusively with fan-on-write. I'd be surprised if Twitter does the same - but it sounds like OP has more knowledge about this than me, so I'm happy to be educated!
> Until Rama is publicly available, the only way to get access to the full Rama release is by applying to our private beta.
I thought it was coming out last August? What happened?
(As per your link, https://blog.redplanetlabs.com/2023/08/15/how-we-reduced-the...)
Edit: @nathanmarz that's cool you have enough interest to keep things moving with it being private. I'm only interested in open solutions for this domain, though. IMO, accepting lock-in is a lot to ask. Best wishes ~ MD
https://github.com/redplanetlabs/twitter-scale-mastodon/blob...
It certainly looks like it does a lot with their DSL, but as a newcomer it's really hard to parse.
https://redplanetlabs.com/docs/~/tutorial1.html
https://github.com/redplanetlabs/rama-demo-gallery
The first sentence has a link to the project page which has most of the info you need.
https://github.com/redplanetlabs/rama-demo-gallery
https://github.com/redplanetlabs/twitter-scale-mastodon
https://blog.redplanetlabs.com/2023/10/11/introducing-ramas-...
https://redplanetlabs.com/docs/~/tutorial1.html
I'm super curious to hear from people who have tried it for larger projects!
Omg. Didn't anyone learn anything from the Datomic story?
> https://github.com/redplanetlabs/specter/tree/master/src
> MutableCell.Java. 8 years ago
Behold the power!Deleted Comment
Or did you mean something else? In which case please elaborate.
This sounds really similar to programming with observables (e.g. RxJS), is a "fragment" an even more general concept?
I used observables when I did frontend development, I found it a useful paradigm (once I got my head around the idea).
Which all in all, if you have built a platform/runtime/language and you pick one particular example to highlight it, being able to achieve XXXX% less than is trivial.
I was curious about all the bluster then, Seeing this post I am somewhat disappointed that there does not appear to have been a lot of visible progression.
But I guess it is still running semi stealth in private beta.
I will be interesting to see what becomes of it.
https://redplanetlabs.com/docs/~/clj-dataflow-lang.html
Data parallelism and partitioning and sharding is a very effective scaling technique.
Nathan, I would appreciate writings about the mental model of mapping software to your mental model of implementing behaviours in the streaming data approach because it is a different paradigm.
I can't read the DSL yet and know what is going on!
https://redplanetlabs.com/docs/~/tutorial6.html