If you take some pub sub like Kafka, Nats or RabbitMQ and bolt some code into it, it really is trivial. You scale by using Kubernetes for services and by sharding and replicating the DBs. It's really easy these days.
Maybe it was more complicated in 20 years ago.
However there's orders of magnitude more effort that goes into:
* Usability
* Performance
* Stability
* Security
* Localisation/internationalisation and accounting for cultural differences
* Monetisation - ads, payment platform integration, fighting fraud
* Fighting abuse, both automated and not
* ... and thousands of little things that will come up when building something big.
Think of this another way... Twitter would not employ literally thousands of employees if there was nothing for them to do. It is not a charity. I don't buy that building anything that can handle hundred of millions of users is simple.
I’ll put it another way. Which job would you rather have? Build a scalable Twitter clone? Or operate the business and make money?
How do you make sure it’s not an epic cesspool? It’s not an engineering problem.
Even Twitter wasn’t able to figure that part out
That twitter is already profitable either means a) the current team are on the same giga-genius level as Elon or b) people are talking absolute nonsense.
Twitter might be better able to survive the pinch - or would have before being lumped with a massive pile of debt. They have 2 costs; servers and staff and one revenue stream; advertising. Simple model and easy to balance the two sides of the equation.
Before the Musk buyout they paid $51mil to service the small amount of debt they had, post the takeover they will be paying ~$1bil to service the debts he has added to their balance sheet.
It's an excellent platform for dissiminating information to interested parties, and it doesn't have to be ads. We have a company's account and we'd paying if they's allow us.
Plus they are bloated as hell, which is also contributing to their business apathy.
Making a viable business out of it is hard.