Re:Ask HN: How to learn how to scale software?
by moomoo11 on Thursday March 28, 2024 @04:06PM
(#39856685)
Scale means different things in different contexts.
Elixir by itself is a good choice if you’re IO bound. So, for most simple APIs (that are used by millions of people per min or something) or notification services or chron job type things.. I think it’s cool.
What about computationally heavy things?
What about data systems? Redundancy at scale? Cache? Etc.
Imo do a case study on discord itself.
Think about everything you see in the app. How do you think it works? Draw some arch diagrams. I think the best way to learn this stuff is experience and working on it yourself. That’s how I learned at $prevJob. We went from simple deployments to bare metal servers to by the time we IPOd using AWS to serve our users all across the world. Our data stores for some things evolved from pg or MySQL to dynamo. Our rdbms deployments evolved. We went from simple single node streams to complicated Kafka setups.
Elixir by itself is a good choice if you’re IO bound. So, for most simple APIs (that are used by millions of people per min or something) or notification services or chron job type things.. I think it’s cool.
What about computationally heavy things?
What about data systems? Redundancy at scale? Cache? Etc.
Imo do a case study on discord itself.
Think about everything you see in the app. How do you think it works? Draw some arch diagrams. I think the best way to learn this stuff is experience and working on it yourself. That’s how I learned at $prevJob. We went from simple deployments to bare metal servers to by the time we IPOd using AWS to serve our users all across the world. Our data stores for some things evolved from pg or MySQL to dynamo. Our rdbms deployments evolved. We went from simple single node streams to complicated Kafka setups.