Skip to content
This repository has been archived by the owner on Oct 1, 2024. It is now read-only.

Decide on a scalable quilt_rails architecture #1100

Closed
GoodForOneFare opened this issue Oct 7, 2019 · 3 comments
Closed

Decide on a scalable quilt_rails architecture #1100

GoodForOneFare opened this issue Oct 7, 2019 · 3 comments

Comments

@GoodForOneFare
Copy link
Member

Overview

quilt_rails should have a recommended architecture that scales far beyond its current limitations.

For now, this discussion will happen in internal channels. Ping me in Slack if you'd like more context.

Motivation

Deadlocks in Puma (see #1059 for more information).

@GoodForOneFare
Copy link
Member Author

We've decided to solve deadlocks via deployment configuration. Production platform will get back to us with a recommended approach. Until then, this is blocked.

@GoodForOneFare
Copy link
Member Author

This is a rough version of the architecture that we'll work towards with prod eng:

Private Rails for Node - draw io 2020-01-07 15-48-49

There'll be some improvements along the way, of course.

@marutypes
Copy link
Contributor

Closing this, as the architecture is decided. Tracking in a private issue since it's Shopify specific.

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

No branches or pull requests

2 participants