4 ms·
While I hate the cargo culting of microservices, there is one use case they handle very well - reusable services with obnoxious dependencies that don't really n
by CuriouslyC 2y ago
While I hate the cargo culting of microservices, there is one use case they handle very well - reusable services with obnoxious dependencies that don't really need to be integrated in with the rest of your codebase. I would much rather take a docker image of a whisper or text-to-speech service and add it to my compose file and call it via HTTP than try to wrestle a CUDA build and get whisper/TTS bindings working for every language where I might need them.
- mind-blight 2y agoA similar case for me has been processing large files. It's really nice to be able to scale up the memory of the file processing server when there are large files being processed, they scale it back down for normal usage
- _heimdall 2y agoMicroservices can also be a great fit for certain team/org structures. Its not ideal to pick the tech based on the team structure, but that's life. I've also found it micro services helpful for heavy data processing projects. A micro service architecture driven by events as data is processed and moved through different steps can be a surprisingly simple setup to reason about and debug.