Earlier quoted context omitted.
yea but does hn have any client side js?
Yeah, a very small amount so that clicking the upvote button does not need to reload the whole page
We reduced the cost of building Mastodon at Twitter-scale by 100x
321–330 of 376 posts
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#322Is Twitters 7k tweets per second the average? If so, what’s the peak rate, and have you tested your system under this load?
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#323Earlier quoted context omitted.
Any JVM language should work. We've built modules with Clojure. We're keeping it closed-source for now.
> We're keeping it closed-source for now. Rama sounds interesting to me for my 'next big project', but I'd not even consider building it on top of a closed core. I think this is a pretty common sentiment in these circles. I understand building an OSS business is not easy either. But perhaps there is some middle of the road that you can walk? - A contractual obligation to open source all (now current) code a couple of…
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#324Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#325Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#326I would argue that this is not "a Mastodon instance", since it is not running Mastodon - other than that, very very neat work! I'm excited for that "Source Code" link to be live :)
I think it's smart from a legal perspective, because the team members seem to partially be coming from companies acquired by Twitter. So I guess, if you say "it's a Mastodon-clone", you cannot be accused of taking proprietary ideas from Twitter (this is just a guess, they know better). But technically very interesting and refreshing to see. I really like their approach. It feels they are innovative.
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#327Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#328Earlier quoted context omitted.
We're comparing just to the original consumer product, which is about the same as Mastodon is today. That's why we said "original consumer product" and not "Twitter's current consumer product". Mastodon actually has more features than the original Twitter consumer product like hashtag follows, global timelines, and more sophisticated filtering/muting capabilities. Some people argue it's not so expensive to build a sc…
I work in gaming, so I cannot speak to your specific experiences. Entity Component Systems are extremely performant, really good science, and shipping in middlewares like Unity. However, in order to ship an ECS game, in my experience, you have to have already made your whole game first in a normal approach, in order to have everything be fully specified sufficiently that you can correctly create an ECS implementation…
What do you mean by normal approach? OO classes with inheritance?
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#329Noticeably missing are any details about concurrency control and replication or recovery protocols. A Twitter clone is one thing but any sort of application needing ACID Transactions is a whole other beast.
All data on Rama is replicated automatically with a configurable "replication factor". Data written to Rama is not made visible until it's successfully replicated. The documentation we're releasing next week includes a page going into detail in how this works.
Re: We reduced the cost of building Mastodon at Twitter-scale by 100x
#330Earlier quoted context omitted.
I consider "DSL" as something that's its own language with it's own lexer and parser, like SQL. The Rama API is just Java – classes, interfaces, methods, etc. Everything you do in Rama, from defining indexes, performing queries, or writing dataflow ETLs, is done in Java.
This is usually referred to as an "embedded DSL" - you have a DSL embedded in a normal programming language using its first class constructs.