Hacker News new | past | comments | ask | show | jobs | submit login
[flagged] M3O – An open source AWS alternative (github.com/m3o)
19 points by asim 4 days ago | hide | past | favorite | 16 comments





The title is misleading. This project isn't open source, rather "source available". I get that the underlying packages from github.com/micro/* are FOSS, but m3o isn't: https://github.com/m3o/m3o/blob/8a533e3ab/LICENSE

Also, the title could be prefixed with a Show HN.


How is this license merely "source available" ? After reading it it sounds extremely permissive. For example:

> The licensor grants you a copyright license for the software to do everything you might do with the software that would otherwise infringe the licensor's copyright in it for any permitted purpose.

> Your license to distribute covers distributing the software with changes and new works

> The licensor grants you an additional copyright license to make changes and new works based on the software for any permitted purpose.

> The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software.

> Any purpose is a permitted purpose


m3o developers have since adopted Apache License v2 which is FOSS, but the previous Polyform-based license wasn't.

From "What is polyform", https://archive.is/1YxES

> PolyForm is not...

> Open source or free software. There are plenty of existing open source licenses. PolyForm is not a substitute for them, but an alternative for those who want to license source code under limited rights.

See also:

"Open source confronts its midlife crisis", https://news.ycombinator.com/item?id=18687498

"What comes after open source", https://news.ycombinator.com/item?id=19554272


If you look at the situation with Elastic and AWS, licensing has become something of a difficult situation. The entirety of the system is built on open source services and infrastructure. The pieces we've built around dev UX and self hosting we're still trying to figure out what to do with. Likely most of it will be moved to open source licenses. But it does not stop anyone from hosting it right now as long as they're not attempting to sell it as a service.

I can honestly see why you would do this, but I’m not sure the over all ecosystem would benefit from this.

Consider the user’s perspective. If they’ve decided to be locked into your stack and your company dies (/becomes prohibitively expensive/etc), they can still host the stuff themselves on premise - a welcome step out, but also quite expensive. There are reasons they wanted cloud hosting in the first place, after all. They can not get another cloud service.

You may be able to somewhat work around this problem by doing a deal like the Qt Company has with KDE: If you can’t meet certain criteria, the code will be released under an open license.


The idea here is we can potentially partner with existing cloud providers who do not have the breadth of services AWS offers. People don't want to be locked in, they want to know they can still take the services with them but you're right they also don't want to manage it themselves anymore. I think this is where there's prime opportunity to work with the Hetzners, OVH's, Linode's of the world.

I honestly think the vendor lock-in argument is overdone. I don't really care that I cannot move from GCP to AWS. I picked my vendor and don't see myself moving. Some companies are looking at hybrid solutions, still using vendor tech and relying on that is not something that is outright avoided, rather often embraced due to decrease in operational overhead.

The VPS "cloud" is the more cost optimizing, DIY group, which I know less about the motivations and market for.


> Likely most of it will be moved to open source licenses.

As OP said, the title is misleading as it is not open source now.

Looks like an interesting project, why muddle the message by making an obviously false claim up front?


The reason why AWS is so complex is because there is like 200 different services. I am sure AWS would be infinitely less complex with only 39 (and most of those are small things like get the current weather, stocks, currency, crypto, etc not actual services in the same sense as AWS).

I appreciate the project, but advertising yourselves as a AWS alternative when you don't even have a EC2 competitor seems a little disingenuous.


PSA: That "M3O" is read as "Micro".

(I initially expected that it was "minio" deciding to rebrand to sound more like AWS)

Also, this is not like AWS at all -- this is not IaaS offering, but a single specific microservices framework [0] and a hosting which specializes on apps using that framework.

[0] https://micro.mu/introduction


No, that's incorrect. We provide a catalog of services as public APIs consumed via HTTP/JSON. So far we offer 35+ services which you can see here https://m3o.com/explore. Those services are open source and you can see the source code at https://github.com/micro/services. The entire suite of services are built using the Micro platform which is also open source. Think Android for Cloud.

Just a couple of days ago I was thinking on how a really decentralised AWS would look like. I think something on top of STORJ, GolemNetwork, IPFS and similar distributed technologies could work. One of the missing links is compatibility with current services. Storj already has S3 compatibility, but something that allows you to setup a "virtual machine" a la EC2 with specific allocated RAM/CPU/HDD would be an interesting use case.

I don't think I want "distributed," I think I just want "federated." I keep hoping something like Standstorm.io will come along, that makes it easy for someone like me to host different apps for my friends and family.

That's nice af but AWS is already widely used :/

"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."

https://news.ycombinator.com/newsguidelines.html


It's also very expensive and has considerable vendor lock-in. Open source alternatives are always welcome.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: