Hello Niels,

Thank you for your feedback.

You’re looking for an unopinionated solution. To be honest right away: like all the others, my solution is opinionated, too.

Under the hood, infrastructure-components use an express.js backend and the serverless-framework. Further, it uses styled-components, GraphQL, and other libraries, too.

Regarding comparison to Gatsby and Next.js. Both are good hosting options for different purposes (Gatsby: JAM-stack, Next.js: SSR). Infrastructure-components support both architectures. My library is rather about abstracting the infrastructure configuration away from the developer. So, if you like the simplicity of the boilerplate, then it achieves its purpose.

Actually, the solution works with Node.js. But Node.js needs to run somewhere (hosting). The only supported provider (right now) is AWS. I plan to add support for Azure and Google Cloud someday. But it will always require an actual infrastructure to run on.

I hope, you’re not disappointed with this answer. But creating an isomorphic-state (shared between client and server) requires to be opinionated to some extent.