Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

How to structure future services? #51

Open
indrif opened this issue Jun 26, 2018 · 0 comments
Open

How to structure future services? #51

indrif opened this issue Jun 26, 2018 · 0 comments
Labels

Comments

@indrif
Copy link
Contributor

indrif commented Jun 26, 2018

I and @teozkr discussed this a bit today, would be nice to bring this up for a larger discussion on friday.

Should we continue developing micro/nanoservices or should we aim for "domain"-grouped larger services? What is the difficulty/benefit of the different strategies?

What will need scaling? E.g. downloading of images vs normalizing data structures?

How to scale? Or simply, do we think about scaling atm?
Do we aim to scale services by number of workers or by hardware? Perhaps different for different services? How about lambda or similar instead?

How can we manage a fast and clean development environment without current problems (compilation time, dependencies, overhead in docker images)?

How small should services be?
At the current level the number of services will explode in the future. This gives a large overhead in docker images, deployment handling, etc etc

Just writing down some of the thoughts we discussed. Feel free to add more to this issue before friday

@indrif indrif added the discuss label Jun 26, 2018
@indrif indrif changed the title How to structure future services How to structure future services? Jun 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant