Scaling Rails and Postgres to millions of users at Microsoft
stepchange.work
Scaling Rails and Postgres to millions of users at Microsoft
1–10 of 96 posts
Re: Scaling Rails and Postgres to millions of users at Microsoft
#2I ran into some scaling challenges with Postgres a few years ago and had to dive into the docs.
While I was mostly living out of the "High Availability, Load Balancing, and Replication" chapter, I couldn't help but poke around and found the docs to be excellent in general. Highly recommend checking them out.
Re: Scaling Rails and Postgres to millions of users at Microsoft
#3I ran into some scaling challenges with Postgres a few years ago and had to dive into the docs. While I was mostly living out of the "High Availability, Load Balancing, and Replication" chapter, I couldn't help but poke around and found the docs to be excellent in general. Highly recommend checking them out. https://www.postgresql.org/docs/16/index.html
Like many of the BSDs
Re: Scaling Rails and Postgres to millions of users at Microsoft
#4I ran into some scaling challenges with Postgres a few years ago and had to dive into the docs. While I was mostly living out of the "High Availability, Load Balancing, and Replication" chapter, I couldn't help but poke around and found the docs to be excellent in general. Highly recommend checking them out. https://www.postgresql.org/docs/16/index.html
Like many of the BSDs
Did Postgres used to be a BSD? Are they known for good documentation?
Re: Scaling Rails and Postgres to millions of users at Microsoft
#5Re: Scaling Rails and Postgres to millions of users at Microsoft
#6I ran into some scaling challenges with Postgres a few years ago and had to dive into the docs. While I was mostly living out of the "High Availability, Load Balancing, and Replication" chapter, I couldn't help but poke around and found the docs to be excellent in general. Highly recommend checking them out. https://www.postgresql.org/docs/16/index.html
They are excellent! Another great example is the Django project, which I always point to for how to write and structure great technical documentation. Working with Django/Postgres is such a nice combo and the standards of documentation and community are a huge part of that.
Re: Scaling Rails and Postgres to millions of users at Microsoft
#7Postgres can be scaled vertically like Stackoverflow did. With cache on edge for popular reads if you absolutely must (but you most likely dont).
No need to microservice or sync read replicas even (unless you are making a game). No load balancers. Just up the RAM and CPU up to TB levels for heavy real world apps (99% of you wont ever run into this issue)
Seriously its so create scalable backend services with postgrest, rpc, triggers, v8, even queues now all in Postgres. You dont even need cloud. Even a mildly RAM'd VPS will do for most apps.
got rid of redis, kubernetes, rabbitmq, bunch of SaaS tools. I just do everything on Postgres and scale vertically.
One server. No serverless. No microservice or load handlers. It's sooo easy.
Re: Scaling Rails and Postgres to millions of users at Microsoft
#8I don't understand why you wouldn't just use Elixir/Phoenix if you need to scale?
Re: Scaling Rails and Postgres to millions of users at Microsoft
#9I ran into some scaling challenges with Postgres a few years ago and had to dive into the docs. While I was mostly living out of the "High Availability, Load Balancing, and Replication" chapter, I couldn't help but poke around and found the docs to be excellent in general. Highly recommend checking them out. https://www.postgresql.org/docs/16/index.html
They are excellent! Another great example is the Django project, which I always point to for how to write and structure great technical documentation. Working with Django/Postgres is such a nice combo and the standards of documentation and community are a huge part of that.
Interestingly I have had almost the exact opposite experience being very frustrated with the Django docs.
To be fair, it could be because I'm frustrated with Django's design decisions having come from Rails.
When learning Django a few years ago, I still carry a deep loathing against polymorphism (generic relations[0]), and model validations (full clean[1]),
You know what - it's design decisions...
[0] https://docs.djangoproject.com/en/5.1/ref/contrib/contenttyp...
[1] https://docs.djangoproject.com/en/5.1/ref/models/instances/#...
Re: Scaling Rails and Postgres to millions of users at Microsoft
#10Postgres can be scaled vertically like Stackoverflow did. With cache on edge for popular reads if you absolutely must (but you most likely dont). No need to microservice or sync read replicas even (unless you are making a game). No load balancers. Just up the RAM and CPU up to TB levels for heavy real world apps (99% of you wont ever run into this issue) Seriously its so create scalable backend services with postgres…
> One server
What happens if this server dies?