If you have two separate processes running in two separate containers... those are two separate services. You need to solve the same problems that would come with running them on two different EC2 instances: what's the method for communicating with the other container? What happens if the other container I'm calling is down? If the other container is down or slow to respond to my API calls, am I dealing with backpressure gracefully or will the system start to experiencing a cascade of failures?
Re:The Costs of Microservices
by jethro_tell on Monday October 30, 2023 @01:00PM
(#38072155)
I suppose if you do that, they will communicate over the network likely via api and have the ability to scale independently.
You just invented microservices, lol.
They don't need to be microservices in order to isolate dependencies, do they?
In Python, for instance, you don't even need containers. Just different virtual environments running on separate processes.