One issue with a lot of the micro services currently in this repo is that they have a lot of external dependencies because the data lives elsewhere e.g if we want weather data it comes from somewhere else, if we want to send an sms we need to use an api, if we want to do any host of things we rely on external apis. While micro services can provide a standard interface to all these things, we should also think about how much can be managed internally or how much we can rely on bootstrapping self-hosted infrastructure. In an ideal world, you can boot the dependency and run the service in one step. In some cases we've defined container images that can provide things like headless chrome but might need to think more broadly about this.
One issue with a lot of the micro services currently in this repo is that they have a lot of external dependencies because the data lives elsewhere e.g if we want weather data it comes from somewhere else, if we want to send an sms we need to use an api, if we want to do any host of things we rely on external apis. While micro services can provide a standard interface to all these things, we should also think about how much can be managed internally or how much we can rely on bootstrapping self-hosted infrastructure. In an ideal world, you can boot the dependency and run the service in one step. In some cases we've defined container images that can provide things like headless chrome but might need to think more broadly about this.