re: Scalable architecture without magic (and how to build it if you’re not Google) VIEW POST

FULL DISCUSSION
 

I'm curious, for Cheetah, you mention a stack using Go and MongoDB. Do you think these choices are important in terms of the horizontal scaling? Say we replace Go with Python (or Ruby, Perl, Php), and MongoDB with Postgresql (or maybe MySQL), would that significantly impact the situation? Also, would using cooperative concurrency be very important here, or would using threads to serve the (stateless) application code be okay? I really like how you included a sense of how many concurrent connections are possible with each scenario, but it made me wonder about what makes the difference. Is it the particular technologies more, or is it more the overall architectural choices (like not storing any state at the application level) and having multiple servers?

 

Of course it’s about architecture. You can use whatever tools you want. I just mention the most popular and suitable as it seems to me

code of conduct - report abuse