4 ms·
Scaling is painful and requires a good deal of upfront work. I can't guarantee that anyone will use stuff that I make, so I'd rather improve performance when I
by litewulf 18y ago
Scaling is painful and requires a good deal of upfront work. I can't guarantee that anyone will use stuff that I make, so I'd rather improve performance when I actually need to.
Its addictive also to spend all your time thinking about scalability and sharding and clustering options instead of making something people use.
In summary: yes, but be pragmatic about these things. If you are the only user, scaling might not be worth it. If you know that people will be using a feature all the time, think about caching from the get-go. Obviously figuring out which of the cases you are in can sometimes be tricky. ;)
- alecco 18y agoIts addictive also to spend all your time thinking about scalability and sharding and clustering options instead of making something people use. I never proposed that. But leaving doors open for possible alternatives and quick fixes doesn't take much time, maybe 5 minutes of thinking. Sane programming methodologies help, like modularization and partitioning your code in different processes. Scalability and rapid development are not always mutually exclusive.