Go Micro v2.4.0 – Go microservices development framework

Post by chuhnk » Tue, Mar 31, 2020, 4:30 PM UTC

andy9775 wrote: post #9

Would I use micro on top of k8s? Doesn't seem to make sense to mix the two as far as I can tell.

Post by gigatexal » Tue, Mar 31, 2020, 5:14 PM UTC

chuhnk wrote: post #7

mpfundstein wrote: post #6

Earlier quoted context omitted.

I think thats not really micro.service anymore. It creates a lock in we dont want. Why not build a monolith then?

Micro focuses on providing distributed systems programming as a single framework, so it takes all the patterns you'd normally leverage and puts them in one place for you to easily build services. We do this with a pluggable model so you can pick and choose underlying infrastructure dependencies or a zero dep model if you choose. Its very powerful and our hope is the next generation of services are built using it.

Post by haggy » Tue, Mar 31, 2020, 5:35 PM UTC

chuhnk wrote: post #11

andy9775 wrote: post #9

Would I use micro on top of k8s? Doesn't seem to make sense to mix the two as far as I can tell.

Actually Micro is the exact thing you would use ontop of kubernetes. Micro was built to tame the world of cloud-native complexity and focus on developer needs. You can think of Micro as an abstraction layer over distribute systems infrastructure, hiding the complexity from the developer and providing a pluggable system which allows it to operate in any environment. This means locally a dev can run with zero deps but…

Post by chuhnk » Tue, Mar 31, 2020, 6:32 PM UTC

haggy wrote: post #15

chuhnk wrote: post #11

Earlier quoted context omitted.

Actually Micro is the exact thing you would use ontop of kubernetes. Micro was built to tame the world of cloud-native complexity and focus on developer needs. You can think of Micro as an abstraction layer over distribute systems infrastructure, hiding the complexity from the developer and providing a pluggable system which allows it to operate in any environment. This means locally a dev can run with zero deps but…

Using this framework on top of kubernetes (which is itself another framework used to managed microservices) sounds like an operational nightmare. Kubernetes is already filled with operational pitfalls so adding more layers on top only increases complexity. I think Go-Micro looks cool but I wouldn't suggest layering this much more than you already are. Complexity is death for distributed systems so minimizing complexi…

Post by PhilippGille » Tue, Mar 31, 2020, 8:50 PM UTC

chuhnk wrote: post #17

haggy wrote: post #15

Earlier quoted context omitted.

Using this framework on top of kubernetes (which is itself another framework used to managed microservices) sounds like an operational nightmare. Kubernetes is already filled with operational pitfalls so adding more layers on top only increases complexity. I think Go-Micro looks cool but I wouldn't suggest layering this much more than you already are. Complexity is death for distributed systems so minimizing complexi…

I'm sorry you've misunderstood what this is. This is a Go Framework for microservices development. It's what you use to write services. It's like Rails or Spring. Kubernetes is for running applications not writing them. Kubernetes no opinions about how you write software. We encapsulate the underlying infrastructure and provide a framework for the developer to literally write business logic.