> The reason is quite simple: they are using Ruby on Rails internally for many parts of the system.
The choice of a language or framework is only one factor on the success of failure of a system.
You can write a broker in brainfuck if you are so inclined. You can make it rock solid. Your pick may require more or less engineering resources, but that's all it does.
You mention ActiveRecord. That too is premature optimization. Crafting optimized SQL queries will not save a badly architected app. They might even be worse if whoever is optimizing them doesn't fully understand what they are doing.
> if you want to make sure that the databas doesn't lock the tables for a long time.
You didn't mention which database you are using. You didn't say anything about its schema. This is yet another generalization. Not all databases will "lock the tables", no matter how badly queries are written. And, if they do, optimize that.
Usually, only a handful of services are critical. Microservices are all the rage, optimize those to death.
The choice of a language or framework is only one factor on the success of failure of a system.
You can write a broker in brainfuck if you are so inclined. You can make it rock solid. Your pick may require more or less engineering resources, but that's all it does.
You mention ActiveRecord. That too is premature optimization. Crafting optimized SQL queries will not save a badly architected app. They might even be worse if whoever is optimizing them doesn't fully understand what they are doing.
> if you want to make sure that the databas doesn't lock the tables for a long time.
You didn't mention which database you are using. You didn't say anything about its schema. This is yet another generalization. Not all databases will "lock the tables", no matter how badly queries are written. And, if they do, optimize that.
Usually, only a handful of services are critical. Microservices are all the rage, optimize those to death.