I would love to have my eventual service accessible securely from within my NextJS, Remix, and SvelteKit apps. I think a smart way to enable this would be to have meta constructs that bind SST's constructs like this SvelteKit app construct with an eventual Service construct. This meta-construct might share configuration which allows the SST deployed app to securely communicate with the deployed eventual Service without needing to configure anything. The EventualClient could then automatically look for the configuration upon construction and automatically authenticate all services between the server side of the SvelteKit app and the Eventual Service.
This would also enable the community to manage authentication to Eventual Service defined functionality using the existing ecosystems of these frontend frameworks. Does this make sense?
I would love to have my eventual service accessible securely from within my NextJS, Remix, and SvelteKit apps. I think a smart way to enable this would be to have meta constructs that bind SST's constructs like this SvelteKit app construct with an eventual Service construct. This meta-construct might share configuration which allows the SST deployed app to securely communicate with the deployed eventual Service without needing to configure anything. The EventualClient could then automatically look for the configuration upon construction and automatically authenticate all services between the server side of the SvelteKit app and the Eventual Service.
This would also enable the community to manage authentication to Eventual Service defined functionality using the existing ecosystems of these frontend frameworks. Does this make sense?