Show HN: M3O – an open source public cloud platform
blog.m3o.com
blog.m3o.com
> AWS is a fairly complex beast which makes it hard for new developers to get started. In the past we needed VMs and file storage, but today with the Jamstack and other modern development models, the building blocks we’re looking for are changing.
Yes! Here's a decent read on how the Big3 cloud providers are being unbundled [0]: https://www.swyx.io/cloud-distros/ Heroku, the blog argues, was ahead of its time, but now PaaS start-ups like replit.com, railway.app, render.com, glitch.com, posthog.com, vercel.com, netlify.com are back on the menu, making a big splash as it were, even if most of them themselves rely on Big3 infrastructure underneath.
Curiously, m3o is taking the hard path that fly.io once did before settling on their current "global, auto-scaled ec2 with free vpc and load balancer" offering (which is uber awesome as a fargate / lambda replacement) and focusing on just one or two core use-cases (of late, seems like fly.io is particularly putting its weight behind the elixir ecosystem). supabase.com is another such project that's narrowed itself down to being a firebase alternative (as opposed to, say, an alternative to all of GCP) with their FOSS tech build-out being mostly around Postgres.
Risking the ire of Dan Abramov here [1], but I suggest m30 errs towards simplicity (and not just easy). Good luck!
[0] https://archive.md/bV9oM, "The Founder's Dilemma: To Compete or Unbundle" (a16z)
Its calling itself a public cloud, but you cant deploy your own apps to it. Instead it appears to be a collection of APIs, that you can consume with your app that you must host elsewhere (sure, thats easily resolved to some extent).
Im still not sure why you are comparing to fly, which is a completely different product.
I may be totally wrong, of course, but thats what I understood from the website.
contrasting it with what flyio once was: https://news.ycombinator.com/item?id=16758525 "fly edge apps" and https://news.ycombinator.com/item?id=13985940 "fly global load balancer and middleware"
> I may be totally wrong, of course, but thats what I understood from the website.
Their docs are better.
m3o framework: https://docs.m3o.com/concepts/framework
m3o platform: https://docs.m3o.com/concepts/platform
Forgive me if this sounds a bit negative... but, aren't you just reselling another cloud provider at this point?
Why would I use you and not go directly to EKS or GKE?
EDIT: Looks like you use digital ocean.. but please don't use commit messages like 'fix' https://github.com/m3o/platform/commit/5c006d3390cf680d58f11...
:o
I mean, I get it - I would avoid undescriptive commit messages myself, and I might mandate it for projects I own or am in some way responsible for.
But I would never complain about it in some stranger's project. Of all the things to complain about...
It's a bit odd to call it a "strangers" project.
I mean, you're right, it is, but it's open source, so we can comment on how that project is being managed.
Surely they're hoping for some kind of contribution and things like that make me shy away a bit. It also seems minorly unprofessional to show what amounts to laziness publicly. I would be chewed out if I did that internally and we have higher standards for what the public see than what our own devs see.
You may consider editing your edit.
On the one hand it seems overly pendantic and petty.
On the other it may harm perception of the products maturity and dampen desire of others to work with it. Additionally it is an anti-pattern which rejects the notion that commits are teaching tools (effectively nuking git-blame). Thus the feedback, while petty, is constructive.
So I think it stays.
Thank you for your feedback.
However, the comment seems misplaced, just like someone else noted in this thread.
Not sure how I’d actually host a web app/site on it, there doesn’t appear to be any documentation on pointing a DNS entry to an entry point or even static file hosting.
Also no notes on HA or reliability, but I guess you get what you pay for in these cases.