3 ms·

While that's true that the network calls should be function calls, it means you can scale horizontally in a lot easier fashion. Sure you've got waste at the sm

While that's true that the network calls should be function calls, it means you can scale horizontally in a lot easier fashion. Sure you've got waste at the small scale, but if you're building for webscale then you have to realize these are the trade offs one must make.

willcipriano 4y ago
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.
Beltalowda 4y ago
A lot of people seem to underestimate how fast computers are; a lot of times you don't need to scale horizontally, even at "webscale". And even when you do, it's not like you need microservices for that; sometimes you just run a new instance of $app, or spin off one thing to a new service (while similar to "microservices", it's not really the same thing as the bulk remains monolithic).
- thibauts 4y ago
  Right. Then HTTP requests being share-nothing they horizontally scale in a single instance, too. Just spin more cores. This microservices craze has been mind-boggling. As for many other fashions, it’s excruciatingly difficult to make young or even average senior devs understand it’s bullshit at 90%. When Netflix does it and the self-appointed expert bloggers praise it, as a CTO or team lead you’re pretty much screwed.
vlunkr 4y ago
> you can scale horizontally in a lot easier fashion. I think you need to define "easier" here. It's easy to launch more instances of your rails app.

willcipriano 4y ago

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.

Beltalowda 4y ago

A lot of people seem to underestimate how fast computers are; a lot of times you don't need to scale horizontally, even at "webscale". And even when you do, it's not like you need microservices for that; sometimes you just run a new instance of $app, or spin off one thing to a new service (while similar to "microservices", it's not really the same thing as the bulk remains monolithic).

thibauts 4y ago
Right. Then HTTP requests being share-nothing they horizontally scale in a single instance, too. Just spin more cores. This microservices craze has been mind-boggling. As for many other fashions, it’s excruciatingly difficult to make young or even average senior devs understand it’s bullshit at 90%. When Netflix does it and the self-appointed expert bloggers praise it, as a CTO or team lead you’re pretty much screwed.

vlunkr 4y ago

> you can scale horizontally in a lot easier fashion. I think you need to define "easier" here. It's easy to launch more instances of your rails app.