Live data from Hacker News

Decoupling a core service from your monolith the right way

betterprogramming.pub

1–10 of 51 posts

Re: Decoupling a core service from your monolith the right way

#6
I don't understand why people choose to put an HTTP barrier in their code. It would have been much better if they had stopped at a Billing module. They get all the code factoring benefits they seek without the performance and operational overhead of an additional service.

Re: Decoupling a core service from your monolith the right way

#9
post #6

I don't understand why people choose to put an HTTP barrier in their code. It would have been much better if they had stopped at a Billing module. They get all the code factoring benefits they seek without the performance and operational overhead of an additional service.

Scaling and load balancing.

Re: Decoupling a core service from your monolith the right way

#10
post #6

I don't understand why people choose to put an HTTP barrier in their code. It would have been much better if they had stopped at a Billing module. They get all the code factoring benefits they seek without the performance and operational overhead of an additional service.

Scaling and load balancing.

From a business perspective, unlocking this precision for infrastructure is only worth the investment at the highest levels of scale.
Post reply on HN