4 ms·
> One of the primary complaints we get is that our current system is too slow Before rewriting the whole thing, are you SURE that you can't make that thing fas
by d--b 2y ago
> One of the primary complaints we get is that our current system is too slow
Before rewriting the whole thing, are you SURE that you can't make that thing faster?
Speeding things up is not too difficult usually. My experience is that there is always something that takes up 95% of the time. And if you find a way to make your app a lot faster without rewriting it, you'll be a hero.
Replacing the app sounds painful. And btw the architecture you propose sounds way too complicated, the 10k-line controllers are more manageable than your microservice proposal.
- dormento 2y ago> Before rewriting the whole thing, are you SURE that you can't make that thing faster? Hear hear! This is _very_ often true. You can profile your database from the command line, looking for query optimizations. Usually, adding some indexes and removing "useless" joins does the trick. Maybe you can convert schema to take advantage of specific optimizations? Maybe if you're storing blobs you can move those to the file system? You can check network usage in the client, maybe the app is loading things it does not need? Maybe the JS stalls waiting for a CDN request? Maybe images, if any, can be optimized and/or removed? You can look into the server process list, and check if its hitting the disk too much, if there are any permission issues, if there's enough RAM, whether the database is local or networked (databases can peg your CPU, which can be costly if its on the same machine -- i know its not recommended but I've seen a lot of weird stuff). > And btw the architecture you propose sounds way too complicated, the 10k-line controllers are more manageable than your microservice proposal. This is also often true, but a hard pill to swallow. Good luck!