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

31–40 of 63 posts

Re: Micro 3.0 is a platform for cloud native development

#31

Post by asim »

oersted wrote: post #17
oersted wrote: post #16

Earlier quoted context omitted.

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.

We have multi-language grpc clients code generated in https://github.com/micro/micro/tree/master/client/sdk but we need to publish to various package managers or at the very least wrap them in a more clean and simple experience first. It's hard to replicate our Go framework experience in clients so I think to start its around consumption. I think grpc-web based typescript client or OpenAPI generated clients might be the next thing but open to ideas.

Re: Micro 3.0 is a platform for cloud native development

#32

Post by friendly_chap »

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.

> Stop trying to tell the river where to turn. It's already done.

After almost a decade of HN I have to say that's one of the most un-HN comments I have ever read.

Re: Micro 3.0 is a platform for cloud native development

#33

Post by asim »

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

M3O does run on k8s. We personally do it for our hosted offering with some customisation, but also include a helm install in the docs for those that want to run on k8s easily. The goal is to target, local as processes, k8s as containers and then look beyond in future to wasm.

Re: Micro 3.0 is a platform for cloud native development

#34

Post by emptysongglass »

choeger wrote: post #26
emptysongglass wrote: post #20

Earlier quoted context omitted.

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.

It wouldn't be an issue for me if these legacy products either a. opted for more ethics where their fork showed them the way or b. if they actually produced innovation instead of desperately holding onto big company departments.

OpenOffice, for example, has basically done nothing but maintenance. It's not something to be proud of.

Re: Micro 3.0 is a platform for cloud native development

#35

Post by Dahoon »

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.

I see nothing wrong with OwnCloud doing business as they do. At least they aren't trying actively to kill off their competitors, like Netgate/Pfsense does and yet HNers seem to like them.

Re: Micro 3.0 is a platform for cloud native development

#36

Post by emptysongglass »

friendly_chap wrote: post #32
emptysongglass wrote: post #20

Earlier quoted context omitted.

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.

> Stop trying to tell the river where to turn. It's already done. After almost a decade of HN I have to say that's one of the most un-HN comments I have ever read.

I think you're confusing daring and innovation with legacy swaddling.

Re: Micro 3.0 is a platform for cloud native development

#37

Post by eatthoselemons »

asim wrote: post #33
eatthoselemons wrote: post #19

Earlier quoted context omitted.

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

M3O does run on k8s. We personally do it for our hosted offering with some customisation, but also include a helm install in the docs for those that want to run on k8s easily. The goal is to target, local as processes, k8s as containers and then look beyond in future to wasm.

ah okay that makes sense, m3o is basically a microservices framework then? Pull the pieces you need (basic authentication, service communication etc) and all you need to add is your business logic?

Re: Micro 3.0 is a platform for cloud native development

#38

Post by tscherno »

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.

Seems like you are mixing up your claims and your premises a bit. Let me try to untangle this. The fork happened, yes, but it did not take the market as you claimed. Also, not “nearly all developers” but barely a dozen of the forkers’ closest friends left ownCloud. I currently have around 50 colleagues in engineering and support alone. ownCloud is doing rather fine, thank you, both as an open-source project and as a company, both with community users and enterprise users.

There are multiple open-source file sync and share platforms. The reason is quite simple: There are multiple ways to implement a digitally sovereign file platform, and different needs call for different feature sets. ownCloud focuses on code quality, reliability and features that security conscious companies and institutions have come to expect. You do not have to like ownCloud, you do you. To your open standards point: I posted here because we use go-micro in our current rewrite, which is by the way under the Apache 2.0 licence. We cherish and embrace open standards and open source, so I don’t exactly get what you mean by “more open standards”. But to answer your first question: we did not die because we were and are in good health, still had and have work to do and, most importantly, have oodles of happy users and customers to serve.

Re: Micro 3.0 is a platform for cloud native development

#39

Post by capableweb »

emptysongglass wrote: post #34
choeger wrote: post #26

Earlier quoted context omitted.

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.

It wouldn't be an issue for me if these legacy products either a. opted for more ethics where their fork showed them the way or b. if they actually produced innovation instead of desperately holding onto big company departments. OpenOffice, for example, has basically done nothing but maintenance. It's not something to be proud of.

> nothing but maintenance. It's not something to be proud of

What? Absolutely! Maintenance is hard. Maintenance of old/big/complex systems is even harder. Maintaining something for so long with substantial user base is definitely something to be proud for. Everything doesn't need to constantly add features in order for people to be proud of their work. Just adding bug/security fixes once you feel something is feature-complete is also OK.

Not sure where this constant need for changes is coming from, but each to their own. But to look down on people who are doing maintenance is a real shitty thing to do.

I hope you don't work together with others in open source, as they'll also feel saddened by your comment that they should not be proud unless they work on new features.

Re: Micro 3.0 is a platform for cloud native development

#40

Post by nickserv »

capableweb wrote: post #39
emptysongglass wrote: post #34

Earlier quoted context omitted.

It wouldn't be an issue for me if these legacy products either a. opted for more ethics where their fork showed them the way or b. if they actually produced innovation instead of desperately holding onto big company departments. OpenOffice, for example, has basically done nothing but maintenance. It's not something to be proud of.

> nothing but maintenance. It's not something to be proud of What? Absolutely! Maintenance is hard. Maintenance of old/big/complex systems is even harder. Maintaining something for so long with substantial user base is definitely something to be proud for. Everything doesn't need to constantly add features in order for people to be proud of their work. Just adding bug/security fixes once you feel something is feature…

Having maintained some old open source codebases, I can say that just keeping up with bitrot is at least 1/3 the workload. New versions of the OS, the language, the libraries, etc is not a minor thing to keep track of and update.
Post reply on HN