3 ms·

I've seen several times where the overhead of the network request is dramatically higher than the work being preformed. The worst example was a validation micr

I've seen several times where the overhead of the network request is dramatically higher than the work being preformed. The worst example was a validation microservice that did things like "is True" or "is greater than 5" one element at a time on a large object. So you'd have an object with 50 elements and it would make 50 requests to the service. This was in the context of a batch processing job that handled millions of items, so billions of requests end up being created. I tried to explain that each network request probably does a few thousand things like "if request_type == 'get'" during it's lifecycle on both sides of the transaction, but nobody got it and I quit soon after.

brianwawok 4y ago
A lot of devs just don’t care. They want to do a cool thing for their resume. This usually means there is no tech leadership that “gets it”.
- runevault 4y ago
  Resume driven development is one of the most depressing things I keep running into in my career. Wanting to learn and grow is great, but forcing customers to suffer the repercussions of your learning because technology/design pattern x is in vogue is closing in on malpractice.
  - brianwawok 4y ago
    Until there is consequences, why not? Next time you interview with someone, ask why they converet a system to Microservices at their last job? If they don't have an actual reason, bin them.