You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A micro service can have other dependencies, like a MySQL, other micro service (that at the same time has other dependencies), etc.
Maybe it will be interesting to handle dependencies in redspread?
If it is, probably the best way is to support or integrate nicely with helm: https://helm.sh (that I think it's being moved to the kubernetes organization).
What do you think?
The text was updated successfully, but these errors were encountered:
The concept that we are thinking about for when versioning has been implemented is the ability to link between spread repositories. This would allow your project to link directly to a version of the official MySQL configuration.
This way your application is versioned to a stable configuration of MySQL that you know will always work but you also have an easy path to upgrade if you want to change MySQL versions.
I'll be able to write down more in a few days but interested in what you think?
link in which way? Like a git submodule? And how do you start the service in kubernetes?
I mean, the dependency can be another micro service and you'd like to use the kubernetes service discovery to connect to it, etc. I'm not sure how that is addressed. (although not a big problem for me, I can handle dependencies manually for now, the list is really small)
Hi,
A micro service can have other dependencies, like a MySQL, other micro service (that at the same time has other dependencies), etc.
Maybe it will be interesting to handle dependencies in redspread?
If it is, probably the best way is to support or integrate nicely with helm: https://helm.sh (that I think it's being moved to the kubernetes organization).
What do you think?
The text was updated successfully, but these errors were encountered: