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.

Sign up for GitHub

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

Jump to bottom

Either consolide worker and notification or extract it as seperate apps #13

Open

allgreed opened this issue Jul 3, 2019 · 1 comment

Assignees

Milestone

Reliable operations

Collaborator

allgreed commented Jul 3, 2019 •

edited

Loading

We're either going monolith + fronted or different services - there's no middle ground

Pro monolith:

we're a small team
it's almost always simpler

Pro services:

those components already live as separate processes
they have different life-cycles
they can fail independently

allgreed added this to the Operation simplicity milestone

allgreed assigned yasiupl and allgreed

Owner

yasiupl commented Jul 23, 2019

Originally the lifecycle of notifications.js was supposed to be different, but after a lot of tinkering it just started to look like worker.js.

Perhaps the social media bindings should be kept in a separate file then exported to and invoked from worker?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment