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

Define DaaS implementation strategy #376

Closed
arnaldopereira opened this issue Nov 30, 2017 · 2 comments
Closed

Define DaaS implementation strategy #376

arnaldopereira opened this issue Nov 30, 2017 · 2 comments
Assignees

Comments

@arnaldopereira
Copy link
Contributor

To implement #374, we have a few options:

  1. Teresa using helm to manage resources through teresa resource create|delete ...
    • Positive:
      • Leverage maturity and features that already exists in helm, as well as all the charts
      • Quicker implementation
    • Negative:
      • Requires helm/tiller for teresa resource ... to work and it must be a specific version
      • Can't customize everything in teresa resource as we wish
  2. Implement everything in Teresa
    • Positive:
      • Fully customizable
      • Avoid adding another dependency
    • Negative:
      • Longer implementation
      • Will have to rewrite it afterwards - as we'll most likely end up with less quality code than teresa have overall
      • Less features, less databases supported
@arnaldopereira arnaldopereira added this to the Database as a service mechanism milestone Nov 30, 2017
@arnaldopereira
Copy link
Contributor Author

Using helm

@arnaldopereira
Copy link
Contributor Author

Everything on Teresa

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

4 participants