What about the database? All these Jamstack articles always seem to skip past a db in their examples and I have never seen an "app" without an associated database.
Or is the KV store supposed to act like an app database?
Or is the KV store supposed to act like an app database?
KV is the simplest thing you can provide, but in general it is hard to build applications on top of it, especially with changing requirements. KV means basically that all your query and way to interact with the storage must be well-known in advance. While with SQL, all your data is there and it is fast to add an index.
The problem with the solution above are the wrapper for libraries, nobody want to write a django or rails app, and integrate with an HTTP service for the database.
But maybe people are willing to do so for micro...
We are working on a solution to this with WeBase [1] and I'd love to see us do an integration with Netlify here where you build with WeBase and host on Netlify (and get automatic API integration with your data models).
(disclaimer, i worked there)
it will help someone like me, sitting on the fence about this whole idea, a better starting point for using Mirco for my use cases.