2 ms·
I've seen quite a few people use the argument that their system wouldn't cope otherwise when they reach the size of Google. If you are one of those, then I hav
by ranting-moth 4y ago
I've seen quite a few people use the argument that their system wouldn't cope otherwise when they reach the size of Google.
If you are one of those, then I have news for you.
1. You are not going to reach the size of Google. Certainly not if you are engineering for it in your 2 person startup. But in case you do, see number 2.
2. Reaching Google scale means you'll have funding to hire good people to scale your software.
- foepys 4y agoIf you plan your architecture carefully and modularize a lot, there is very little that will prevent you from branching out modules of a monolith into microservices when the time comes. If you produce spaghetti code with tightly coupled components, well, then you are going to have a problem.
- ranting-moth 4y agoEspecially in small startups, you need to make a sensible balance. If you only have funding for 2 months, you need to hack together whatever you can get away with. This is not against modularisation. By all means designs your system well. But don't lose sight of the goal.
- foepys 4y agoIf you bet everything on crappy code you will have to rewrite anyways and then I don't see why this discussion matters.
- deleted 4y ago[deleted]
- shapefrog 4y agoReaching Google scale means you'll be sat on a beach wondering how to spend your multiple billions - scale is someone else's problem, might as well leave something in it for the next person.