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

Feathers Scaling Question #534

Closed
kethan opened this issue Mar 20, 2017 · 2 comments
Closed

Feathers Scaling Question #534

kethan opened this issue Mar 20, 2017 · 2 comments

Comments

@kethan
Copy link

kethan commented Mar 20, 2017

Hi All,
I am about to create PaaS like architecture similar to Parse or Firebase using feathers. But each services like UserService, AppService, DBService, FileService, etc will made as docker containers and will be scaled according to the traffic for each service. I will be using kubernates or Marathon to Orchestrate.

So how do i design this ? How will socket connection scale?
I have seen feathers-sync and few articles
but I don't know how to make proper use of it??
#121
#332
#157
#118
https://github.com/nanobox-quickstarts/nanobox-feathers

Can somebody give a example app structure so i can start with?

Thank You,
Kethan

@kc-dot-io
Copy link
Contributor

kc-dot-io commented Mar 21, 2017

HI @kethan your question is pretty broad and unfortunately some of this falls outside the feathers domain. Ideally you will want to use feathers-sync to synchronize events across your services. This would be similar to how you would do it with a "cluster" of processes. Aside from syncing events, the rest of feathers is stateless by default and so the normal rules would apply to scaling your infrastructure. We don't unfortunately have an "example" persay as infrastructure concerns are somewhat unique to your implementation but aside from syncing events, there isn't anything unique about feathers that should cause you much pain in this regard as long as you follow the best practices of the orchestration framework that you end up using.

@lock
Copy link

lock bot commented Feb 7, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants