zlacker

Rails, and the way it used MySQL/Postgres, was designed for building CMSs. Very amenable to CDN caching to scale.

Twitter was a realtime messaging platform (fundamentally not edge-cacheable) that evolved from that CMS foundation. So the reason for the difficult evolution should be clear.

It's not really a coincidence that before Twitter I worked at CNET on Urbanbaby.com which was also a realtime, threaded, short message web chat implemented in Rails.

Anyway the point is: use my new project/company https://fauna.com/ to scale your operational data. :-)

>>evanwe+(OP)
I take it from a quick glance: you either own/work for Fauna and it’s a completely proprietary product? If so .. I’ll pass, I like building things atop stuff I can control. :)

>>Operyl+b1
Yes, it's not open source (for now). Managed cloud and on-premises edition. We will have a free download soon.

>>evanwe+H1
Might I suggest disclosing it when you post about it? Clicking through your profile revealed it, but it seems like it could read off better for you in the future. :)

EDIT: either it was edited above, or I’m blind. I think it was the earlier?

>>Operyl+Q1
Yeah I fixed it. Thanks.