Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to handle dependencies? #102

Open
rata opened this issue Mar 15, 2016 · 2 comments
Open

How to handle dependencies? #102

rata opened this issue Mar 15, 2016 · 2 comments

Comments

@rata
Copy link

rata commented Mar 15, 2016

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?

@ethernetdan
Copy link
Member

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?

@rata
Copy link
Author

rata commented Mar 23, 2016

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants