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

Micro 3.0 is a platform for cloud native development

micro.mu

Post reply on HN
Print view View original

21–30 of 63 posts

Re: Micro 3.0 is a platform for cloud native development

#21

Post by davedx »

asim wrote: post #3

Hey all, author here! Please provide comments and feedback. Happy to answer questions and discuss this old thing called "microservices" and poke fun at the complexity of cloud and AWS.

I would love something like this for nodejs, my language of choice for microservices.

I will definitely watch how your platform evolves. Good luck!

Re: Micro 3.0 is a platform for cloud native development

#22

Post by quells »

asim wrote: post #5
drondin wrote: post #4

Is there any way to self-host this? If there is a guide that would be awesome!

Yes. Micro is open source and has been so since inception. Here is a quick start to install https://micro.mu/getting-started#install

Is there any documentation on how to run multiple instances of Micro which can communicate and share config/secrets? What is the horizontal scaling story?

Re: Micro 3.0 is a platform for cloud native development

#23

Post by kp995 »

friendly_chap wrote: post #2

Hi people, I'm one of the people working on this. Thanks for your support! If you want to try the thing in minutes may I advise you to start here: https://m3o.com/start . Pretty much just a couple of commands to get started :)). Cheers

Hi, Great work just one tip, adding syntax highlighting to the start page will help. I noticed you have that similar on landing page tho

Re: Micro 3.0 is a platform for cloud native development

#24

Post by gen220 »

eatthoselemons wrote: post #19
asim wrote: post #11

Earlier quoted context omitted.

Micro is developer first focused. Meaning the starting point is writing code not deployment. We bake in a Go framework to write backend services. Then micro builds in everything you need. Abstracting away k8s. Everything you need is an importable package. Everything also works out of the box on your local machine using "micro server". No k8s necessary. The majority of the focus for us now is m3o.com. A hosted platfor…

Does that mean that you could run m3o on k8? (sounds like m3o is a microservice framework?)

From my perspective (I've taken cursory dives into micro in the past), micro is analogous to the libraries developed by every company's infra team to decorate teams' APIs (opentracing, metrics, logging, etc), making them consistently useful with minimal impact on developer velocity.

If this analogy is accurate, it means can deploy these however you want. They're kind of like force multipliers on the effectiveness of distributed computing tools (RPCs, logging, etc).

I welcome refinements/corrections of this analogy!

Re: Micro 3.0 is a platform for cloud native development

#25

Post by vr46 »

I've been using the previous version for a while, and it's been way too complicated and confusing, so I'm happy to see that version 3 is addressing some of those issues. It's very ambitious and promises great things with the client generation, but it's not that straightforward to set up and use. The cloud might be complex, but a lack of really great docunentation makes Micro just as complex. Good luck to them, though.

Re: Micro 3.0 is a platform for cloud native development

#26

Post by choeger »

emptysongglass wrote: post #20
tscherno wrote: post #13

ownCloud is currently doing a full rewrite called "ocis" which uses the go-micro stack. It allows us to focus on the business-logic of file-syncing while taking care of all the micro-service plumbing. Disclaimer: I work for ownCloud.

Why did you guys continue to exist once Nextcloud broke out and took the market? I feel like the insistence of ownCloud and OpenOffice to defy the more open standards their forks (together with nearly all developers) moved toward is... aggravating? Stop trying to tell the river where to turn. It's already done.

Whoa, I really hope no one ever comes telling you such an offensive thing. If owncloud has customers and/or investors they can develop whatever they want and I will applaude them for sharing the code.

Re: Micro 3.0 is a platform for cloud native development

#28

Post by asim »

vr46 wrote: post #25

I've been using the previous version for a while, and it's been way too complicated and confusing, so I'm happy to see that version 3 is addressing some of those issues. It's very ambitious and promises great things with the client generation, but it's not that straightforward to set up and use. The cloud might be complex, but a lack of really great docunentation makes Micro just as complex. Good luck to them, though…

Thanks for the feedback. You're right, Micro was trying to do too much, based on prior experiences at other companies that provided the all encompassing platform experience. Once I realised that I started to scale back. With Micro 3.0 we also knew docs was one lagging thing from before and the fragmented projects were causing huge issues. So now we have betters docs https://micro.mu/ and we have a single project https://github.com/micro/micro. The product M3O (https://m3o.com) has its own set of docs, sort of like how Git and GitHub would have different docs.

Hopefully we're headed in the right direction.

Re: Micro 3.0 is a platform for cloud native development

#30

Post by asim »

rfonseca wrote: post #14
asim wrote: post #3

Hey all, author here! Please provide comments and feedback. Happy to answer questions and discuss this old thing called "microservices" and poke fun at the complexity of cloud and AWS.

There is a lot of interest on microservices from the research community; there are many open-source frameworks that enable you to write/deploy/operate microservice applications with different levels of abstraction. One thing that is missing in the open is (significant) example applications / benchmarks, across which we can compare the different frameworks in terms of ease of use, convenience, performance, etc. Can yo…

I think most people are effectively doing some form of CRUD on the backend that's then consumed by web apps or mobile. In our case we've built out a number of example applications in https://github.com/micro/services.
Post reply on HN