Summary

Currently we deploy the app as a single unit. It's fine as it but it has grown to become cumbersome in deployments (specifically due to Railway constraints... if we just hosted on a VM it'd be fine I guess)

Basic Example

• Split byte (Discord bot) into its own service
• Split server (API) into its own service
• Database remains in its own service

Drawbacks and Impact

This will allow us to eventually do least-diff deploys whereby we only deploy service X if X is changed, and not if Y is changed, etc.

Unresolved questions

We will need to figure out the current web of calls in between the two services. Currently they can call around each other, import similar utils, etc.

This may be a good chance to use uv workspaces?