4 ms·
And how often do you need that sort of decoupling at all? Beside that, I disagree in principle because, like the OP said, it's just hiding the maintenance burd
by ljm 6y ago
And how often do you need that sort of decoupling at all?
Beside that, I disagree in principle because, like the OP said, it's just hiding the maintenance burden elsewhere. It doesn't go away.
- zionic 6y agoThe problem is the server has a connection to the database that’s infinitely more reliable than the client -> server. I’ve dealt with garbage REST APIs with tons of sequential calls and in low reliability scenarios 1 call is a massive improvement over a scenario where 4-5 sequential calls need to be made and if/when one of them fails you need to start over. Now the client has to handle result caching and all the different error states because some server dev couldn't be bothered to batch a few calls and return all the required models.
- ForHackernews 6y agoAt my company, we benefit from loose coupling between components every time we'd like to release an update to one without a concomitant deploy to some other service.