You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
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.
The text was updated successfully, but these errors were encountered: