from Hacker News

Context: a Java web app project composed of independent services: the JakartaEE app itself, and Java SE apps around it which perform long running operations.

I manage inter-service communication with simple http requests.

Slow (especially when moving around files, which is rare but does happen) but:

- simple - tech is stable - easy to adapt if services end up moving to different servers - slowness is acceptable because dwarfed by the duration of the long running ops performed by the app.

I wonder if this approach is a common one, and why not?