News for hackers. Stuff that matters.

A comment on “Lambda and serverless is one of the worst forms of proprietary lock-in” (2017). Parent comment

Re:“Lambda and serverless is one of the worst forms of propr... by Twirrim on Monday February 04, 2019 @10:45PM (#19082884)
> And, if you remember in the early days, Twitter's scalability was absolutely atrocious - the "Fail Whale" was an emblem of Twitter's engineering headaches.

That's because Twitter was:

1) A monolith

2) Written in Ruby

They started splitting components up in to specialised made-for-purpose components using Scala atop the JVM, and scaling ceased being a big issue. The problems they ran into couldn't be solved by horizontal scaling. There wasn't any service that AWS offers even today that would have helped with those engineering challenges.

[ Parent | on HN ]
Re:“Lambda and serverless is one of the worst forms of propr... by tomnipotent on Tuesday February 05, 2019 @12:24AM (#19083178)
It had more to do with the consistency model of relational databases, though Ruby definitely didn't help.
[ Parent | on HN ]
Re:“Lambda and serverless is one of the worst forms of propr... by drchickensalad on Tuesday February 05, 2019 @08:24AM (#19085026)
You honestly think that the main performance problem with a 2yo app is that it's a monolith?
[ Parent | on HN ]
Re:“Lambda and serverless is one of the worst forms of propr... by Twirrim on Thursday February 07, 2019 @05:23PM (#19109210)
Yes, based on their own detailed analysis and extensive technical blogs on the subject. Ruby was doing a lot of processing of the tweets contents etc. etc, and at the time Ruby was even worse for performance than it is today. (Ruby may be many things, but until the more recent JIT work, fast was not one of them).
[ Parent | on HN ]