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

Server Side Rendering #24

Open
alrdytaken opened this issue Jan 21, 2019 · 1 comment
Open

Server Side Rendering #24

alrdytaken opened this issue Jan 21, 2019 · 1 comment

Comments

@alrdytaken
Copy link

To me it’s the only missing piece at the moment.
Do you have any ideas how that could be solved, yet?

So we could take any templating engine that has a
JavaScript verison, too which we could just run in
the browser i like i.e. TwigJS. But then we’d have
a requirement on using nodejs on the backend.

@romainl
Copy link

romainl commented Jan 22, 2019

You need a composition solution on the back-end just like you need a composition solution on the front-end and using Node.js on the back-end allows you to share at least some code with the front-end.

The main problem, IMO, is when to do SSR in a distributed micro-frontends context. Calling n fragments via HTTP for SSR (even if they are on the same node) and then calling them again in the browser sounds incredibly wasteful to me.

The solution I'm envisioning for my next project is a half-in-the-bag solution where we build a skeleton, the most static parts of the app + metadata, on the back-end with a templating engine (marko looks very good).

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

No branches or pull requests

2 participants