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

11–20 of 63 posts

Re: Micro 3.0 is a platform for cloud native development

#11

Post by asim »

eatthoselemons wrote: post #10
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.

How is this different from K8's? It just looks like k8 with a little extra boilerplate for microservices (built in key-value store etc)

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 platform. Otherwise I think k8s is the wrong abstraction for devs. We need access to underlying primitives but also need a workflow thats driven around writing services not operating them.

Re: Micro 3.0 is a platform for cloud native development

#12

Post by friendly_chap »

eatthoselemons wrote: post #10
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.

How is this different from K8's? It just looks like k8 with a little extra boilerplate for microservices (built in key-value store etc)

K8s is closer to an infra tool while Micro is a full flegded development model - it's a bit like Rails/frameworks going to the cloud.

Re: Micro 3.0 is a platform for cloud native development

#14

Post by rfonseca »

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 you give a description or samples of what people are doing in m3o.com?

Re: Micro 3.0 is a platform for cloud native development

#15

Post by cooperadymas »

It's not entirely clear from a light perusing of the sites or docs. Is Micro a Go framework or does it support building services in any language?

A lot of the concepts and features seem really useful to what I'm looking to build, but the project will not be built in Go.

Re: Micro 3.0 is a platform for cloud native development

#16

Post by oersted »

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.

Is it correct that Micro is only compatible with the Go stack? We would be very interested to apply this to our Node/Typescript/Python family of microservices, we've been having many difficulties with K8S and this looks like a level of abstraction that would be perfect for us right now.

Re: Micro 3.0 is a platform for cloud native development

#17

Post by oersted »

oersted wrote: post #16
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.

Is it correct that Micro is only compatible with the Go stack? We would be very interested to apply this to our Node/Typescript/Python family of microservices, we've been having many difficulties with K8S and this looks like a level of abstraction that would be perfect for us right now.

I see now that "go, java, typescript, ruby, python clients" is done in the roadmap, but can't find any documentation about it.

Re: Micro 3.0 is a platform for cloud native development

#18

Post by friendly_chap »

cooperadymas wrote: post #15

It's not entirely clear from a light perusing of the sites or docs. Is Micro a Go framework or does it support building services in any language? A lot of the concepts and features seem really useful to what I'm looking to build, but the project will not be built in Go.

At the moment Micro is focusing on Go backends consumed by clients in different languages. I would wait until there is more explicit support for different nackend languages, unless you feel adventurous.

Re: Micro 3.0 is a platform for cloud native development

#19

Post by eatthoselemons »

asim wrote: post #11
eatthoselemons wrote: post #10

Earlier quoted context omitted.

How is this different from K8's? It just looks like k8 with a little extra boilerplate for microservices (built in key-value store etc)

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?)

Re: Micro 3.0 is a platform for cloud native development

#20

Post by emptysongglass »

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.

Post reply on HN