Netlify for the frontend, Micro for the backend
blog.m3o.com
Netlify for the frontend, Micro for the backend
1–10 of 66 posts
Re: Netlify for the frontend, Micro for the backend
#2When I read about such abstractions and "simplifications" (which usually end up with a 10 box diagram simplified to a 2-3 box diagram), I often hesitate to start building something new, always wondering "Am I doing this in the most " upvoted" way of implementing such a thing? Some of this tech feels like if you switch on, and stare at your monitor long enough, a "Hello World" API will be deployed on the cloud for you, voilà!
Re: Netlify for the frontend, Micro for the backend
#3When I read about such abstractions and "simplifications" (which usually end up with a 10 box diagram simplified to a 2-3 box diagram), I often hesitate to start building something new, always wondering "Am I doing this in the most " upvoted" way of implementing such a thing? Some of this tech feels like if you switch on, and stare at your monitor long enough, a "Hello World" API will be deployed on the cloud for you…
Maybe microservices might seem buzzwordy on the surface, and this might be an anecdote, but I have seen it working first hand at Hailo (Uber competitor back in 2013). Relatively inexperienced people not knowing anything about Go or deeper architectural issues deploying Go services in no time, without even asking for permission.
I don't think that would have been doable with a monolith. It enabled innovation I have never seen before. My 2c
Re: Netlify for the frontend, Micro for the backend
#4When I read about such abstractions and "simplifications" (which usually end up with a 10 box diagram simplified to a 2-3 box diagram), I often hesitate to start building something new, always wondering "Am I doing this in the most " upvoted" way of implementing such a thing? Some of this tech feels like if you switch on, and stare at your monitor long enough, a "Hello World" API will be deployed on the cloud for you…
Maybe microservices might seem buzzwordy on the surface, and this might be an anecdote, but I have seen it working first hand at Hailo (Uber competitor back in 2013). Relatively inexperienced people not knowing anything about Go or deeper architectural issues deploying Go services in no time, without even asking for permission. I don't think that would have been doable with a monolith. It enabled innovation I have ne…
Absolutely. I wasn't criticizing the architecture at all, just musing out loud. I had meetings this week at Big Co (read: cash cow) where external vendors were pushing microservices as manna from heaven for problems that are yet to be discovered. I am sure the technology described in the article is very clever and has strong merits.
Re: Netlify for the frontend, Micro for the backend
#5I'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[1], but their material is so ridden with marketing buzzwords I am not sure it's suitable for what I'm looking for (basically, a small server that can store a small amount of documents or key-value information on whatever database the platform supports without fuss).
Heroku seems to be the most close to this I could find, but it's pretty expensive from what I saw if you need a DB.
Does anyone have suggestions for alternatives?
[1] https://developers.redhat.com/blog/2020/05/28/quarkus-a-kube...
Re: Netlify for the frontend, Micro for the backend
#6I'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…
Heroku for sure. It’s all running on AWS so you can leverage AWS services without as much of a performance penalty for routing as say another provider.
I don’t understand how this Micro framework is valuable unless your entire team writes Go. Even then, this is not just ‘micro services’ it’s a monolith on a proprietary framework that happens to have network hops between function calls. It is the kitchen sink!
Re: Netlify for the frontend, Micro for the backend
#7What 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?
Re: Netlify for the frontend, Micro for the backend
#8What 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?
Founder of Micro here. Yes the key-value store is basically like a crud database. We're working on some modelling on top of that and something we'll present more like a document database. Watch this space.
Re: Netlify for the frontend, Micro for the backend
#9I'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…
Heroku for sure. It’s all running on AWS so you can leverage AWS services without as much of a performance penalty for routing as say another provider. I don’t understand how this Micro framework is valuable unless your entire team writes Go. Even then, this is not just ‘micro services’ it’s a monolith on a proprietary framework that happens to have network hops between function calls. It is the kitchen sink!
All your services are written independently as microservices. In fact Micro is itself a microservices architecture and each feature is an independent service backed by highly available managed infrastructure.
Yes we expect you to write everything in Go. I don't think that should be surprising since all of frontend is JavaScript, iOS is objective C and Android is Java. We think cloud is as complex Architecture as any of those and that requires a single language and framework for it.
Re: Netlify for the frontend, Micro for the backend
#10Hi HN! Asim here. Founder CEO of Micro. We've been working on M3O for some time now and excited to not only share it with the world but help understand our positioning amongst other technology such as Netlify and the frontend. Happy to answer any questions.