The value proposition was clear and well written, until I got to this part: "you want to do it without having to standup layers of infrastructure on AWS or be beholden to the legacy players like Heroku or other providers who don’t get that you want the same Netlify like experience on the backend." So exactly how is Heroku "legacy"? From past experiences pushing a simple backend service onto Heroku was pretty smooth a…
Netlify for the frontend, Micro for the backend
61–66 of 66 posts
Re: Netlify for the frontend, Micro for the backend
#62The value proposition was clear and well written, until I got to this part: "you want to do it without having to standup layers of infrastructure on AWS or be beholden to the legacy players like Heroku or other providers who don’t get that you want the same Netlify like experience on the backend." So exactly how is Heroku "legacy"? From past experiences pushing a simple backend service onto Heroku was pretty smooth a…
Re: Netlify for the frontend, Micro for the backend
#63Re: Netlify for the frontend, Micro for the backend
#64I've been looking for exactly that: a backend thing that's as easy to setup as Netlify is for the frontend. Micro seems to be a Go framework evolved to automatically deploy code to the "cloud", but it seems it'll remain limited to Go backends... I can write Go without problems, but I wanted something that supports other languages as well, specially Java... I think RedHat seems to offer that with OpenShift and Quarkus…
Besides the other answers, I found Cloudfare Workers[1] seem to nearly fit the bill (the only problem is that workers are written in JS - though you can also write them in Rust, C or C++, with the caveat that they compile to WASM, then are executed via the JS API).
Pricing start free! With $5/month you get access to KV (Key-Value Storage) and a generous amount of requests (10 million/month) which seems appropriate for my needs... and it's still in beta, but they also have consistent storage now with Durable Objects[2].
[1] https://developers.cloudflare.com/workers/tutorials
[2] https://developers.cloudflare.com/workers/learning/using-dur...
Re: Netlify for the frontend, Micro for the backend
#65What 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?
This is a great point and one reason I am left scratching my head when considering building applications on the JAM stack. 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). [1] https://www.webase.com
Re: Netlify for the frontend, Micro for the backend
#66Earlier quoted context omitted.
This is a great point and one reason I am left scratching my head when considering building applications on the JAM stack. 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). [1] https://www.webase.com
what's the pitch vs an airtable wich i already use ?