|
|
|
|
|
by unionpivo
2467 days ago
|
|
I think OP thinks about different scale. It's not scale about number of users or data, it's complexity scale. Last enterprise app i worked on had (provided) something like 10.000 different api calls (and yes mostly because of bad/wrong initial design decisions), and over 50k different possible queries that it could run against database. (my job was to "make database go faster") Just running unit tests took longer than 6hrs (of course most unit test went out and connected to the database, because why not \s). It all could be replaced with dozen or so 10k to 30k lines go projects each, that would be a lot easier to maintain and to scale out. |
|