#I'm little confused about remix

1 messages · Page 1 of 1 (latest)

humble frigate
#

Hello everyone,

I'm starting to create a standalone Shopify app and encountered Remix while researching templates. I'm still not entirely convinced about how this framework can handle large, complex applications. I really want to try it, but I'd love to hear about your experiences with Remix in developing large web applications with many features.

Specifically, if you've developed a large application with Remix, do you write both the backend and frontend within one app, or do you have a separated backend? If you don't have a separated backend, how do you scale your application? For instance, if the backend workload is heavier than the frontend workload, but they are deployed together, how does this affect scaling? Is there a way to deploy them separately, and if so, is that considered best practice?

Thank you!

lapis cairn
#

If you need a separate backend just make a separate one, let remix only a thin layer of UI and SSR as backend of frontend

humble frigate
#

According to the approach you've mentioned, I think it is called bff, loader and action are only used to send API requests to separate backend, right?

But otherwise, how can we scale two components seperately?

sweet stream