| Brain dump: Looks very cool. From what I can tell... pros: * No tooling to set up, don't have to think about project structure or computation (VMs or cloud functions) * Don't have to think about databases, connection strings, etc * Fast deployments * Perfect for rapid prototyping or hackathons cons: * Vendor lock-in at the language and infrastructure level * Not open source * Have to learn a new language Compared to serverless (for a CRUD application), I wouldn't have to write configuration to set up the API endpoints / dynamodb tables. Also, deployments would be super fast which closes the developer feedback loop. I shouldn't have to worry about emulating my stack locally or deploying my stack every time I want to test my code. The cons make this very hard for me to buy though. My ideal framework would be open source in a popular language (JS / Go), runs on cloud (AWS / Azure / GCP), fast deployments (no cloudformation), low configuration / convention based (like nextjs), and integrates with popular NoSQL data stores (mongo, redis, etc). Basically it would be completely conventional with an opinioned data access and the ability to override features to add more complicated functionality like optimizing data access after the initial prototyping. |