Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Netlify for the frontend, Micro for the backend

blog.m3o.com

Post reply on HN
Print view View original

31–40 of 66 posts

Re: Netlify for the frontend, Micro for the backend

#31

Post by Matthias1 »

brabel wrote: post #5

I'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…

Dark (https://darklang.com) is a very cool platform for building serverless backend APIs.

The Dark language itself is not what you’re looking for, and I don’t know if I would trust it in production (it’s still in beta). But the platform makes it extremely quick to get a POC backend working.

Re: Netlify for the frontend, Micro for the backend

#34

Post by asim »

simoneau wrote: post #32

Make sure you're cool with micro's license: https://polyformproject.org/licenses/shield/1.0.0/ The noncompete clause is problematic.

Happy to talk more about the benefits of Polyform and why we chose that. If you've seen what's happening with open source and AWS you'll understand that this is one of the few ways to protect against cannibalisation of our ecosystem and ability to build a real business. AWS gives nothing back to the creators, and we believe cloud will have its music industry moment. Polyform is a fairly liberal and standardised set of licenses co-drafted by Heather Meeker is well known for her work on open source and enterprise licensing. We believe licensing evolution is required beyond Apache 2.0 and MIT in this new world of cloud and AWS. By choosing licensing standards over custom drafting we think it will make it simpler for companies to adopt and get approval of those in larger orgs. Again happy to speak more on the topic.

Re: Netlify for the frontend, Micro for the backend

#35

Post by asim »

BenGosub wrote: post #33

Microservices have to be written in Go Nitro framework, this is not framework/language agnostic?

Go Nitro is not a thing. "Go Micro" was a framework that launched this company into existence, it's now been consolidated into a single project called "Micro". The "Go Micro" project has been renamed to "Nitro" to reduce confusion around the two.

Your services must be written using the Micro framework, as you would use something defined by iOS and Android for those platforms.

Re: Netlify for the frontend, Micro for the backend

#36

Post by asim »

rishav_sharan wrote: post #26
asim wrote: post #8

Earlier quoted context omitted.

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.

Will it be possible for you folks to add a Realworld example for Micro? https://github.com/gothinkster/realworld 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.

Hi, thanks for asking. This is the first time I've seen the project realworld so please excuse my ignorance, I'm not in the JS community. We will have a look and try to get around to this. Right now you can look at https://github.com/micro/services for any of our backend examples.

Re: Netlify for the frontend, Micro for the backend

#37

Post by clarle »

asim wrote: post #34
simoneau wrote: post #32

Make sure you're cool with micro's license: https://polyformproject.org/licenses/shield/1.0.0/ The noncompete clause is problematic.

Happy to talk more about the benefits of Polyform and why we chose that. If you've seen what's happening with open source and AWS you'll understand that this is one of the few ways to protect against cannibalisation of our ecosystem and ability to build a real business. AWS gives nothing back to the creators, and we believe cloud will have its music industry moment. Polyform is a fairly liberal and standardised set o…

I like the idea conceptually behind the license, but without an explicit definition of what competition is, it feels tough to use.

For instance, Micro provides a persistent form of key-value storage. If my product focuses on a very specific audience (say medicine), but also exposes a way for doctors to store arbitrary key-value pairs, could that be argued in court to be competition?

The definition of competition in the Polyform Shield license is never explicitly stated, and in fact, it specifically calls out that "Applications can compete with services".

Whereas the MIT and Apache license are pretty explicitly clear in what the terms of use are, Polyform seems to be fairly vague there, which is potentially something you wouldn't want for a legal license.

Re: Netlify for the frontend, Micro for the backend

#38

Post by simoneau »

asim wrote: post #34
simoneau wrote: post #32

Make sure you're cool with micro's license: https://polyformproject.org/licenses/shield/1.0.0/ The noncompete clause is problematic.

Happy to talk more about the benefits of Polyform and why we chose that. If you've seen what's happening with open source and AWS you'll understand that this is one of the few ways to protect against cannibalisation of our ecosystem and ability to build a real business. AWS gives nothing back to the creators, and we believe cloud will have its music industry moment. Polyform is a fairly liberal and standardised set o…

These all sound like good motivations to me. But it seems for an organization to use this software, you need to convince yourselves that you understand who the licensor is and what their business is, and that your business doesn't compete as defined in the Compete section. This is a significant task if you just want to respect the request of the authors, and is bigger if you want to make sure you don't end up in court.

Re: Netlify for the frontend, Micro for the backend

#39

Post by gav »

asim wrote: post #34
simoneau wrote: post #32

Make sure you're cool with micro's license: https://polyformproject.org/licenses/shield/1.0.0/ The noncompete clause is problematic.

Happy to talk more about the benefits of Polyform and why we chose that. If you've seen what's happening with open source and AWS you'll understand that this is one of the few ways to protect against cannibalisation of our ecosystem and ability to build a real business. AWS gives nothing back to the creators, and we believe cloud will have its music industry moment. Polyform is a fairly liberal and standardised set o…

I understand where you're coming from, but the license itself is terribly general and broad:

> Any purpose is a permitted purpose, except for providing any product that competes with the software or any product the licensor or any of its affiliates provides using the software.

You're not just unable to compete with Polyform, you're unable to compete with Polyform's affiliates.

Post reply on HN