Earlier quoted context omitted.
Is it possible to create a tutorial showing features end-to-end (using CLI / Code generation)? I have seen a couple of high quality tutorial series on web - but they are advocating usage of 1.18 version.
Sure, what kind of tutorials are you interested in? Written form or video? We're thinking about doing a video walkthrough series potentially in live form.
Go Micro v2.4.0 – Go microservices development framework
21–26 of 26 posts
Re: Go Micro v2.4.0 – Go microservices development framework
#22I was just posting this on another forum. But I want to learn more about scalability and availability and microservices. I am quite familiar with fullstack and various databases but I need a hands on experience. Does micro have some sort of tutorials that build microservices from scratch?
https://itnext.io/micro-in-action-getting-started-a79916ae3c...
Note: it is based on v1.18 for now. I'll update it to v2.x soon
Re: Go Micro v2.4.0 – Go microservices development framework
#23We are looking into Dapr now. How do you compare to it? https://github.com/dapr/dapr
Re: Go Micro v2.4.0 – Go microservices development framework
#24Earlier quoted context omitted.
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.
The first two features listed on the README are "service discovery" and "load balancing", which is probably where the question is coming from.
Micro seems like a framework + platform for running micro services (ideally on bare metal). (Not saying there's anything wrong with that though)
Re: Go Micro v2.4.0 – Go microservices development framework
#25Earlier 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.
I could see using micro on bare metal (with all features) but trying to get the grasp of mixing with k8s (with all of micro's features). I'm assuming no one is using micro's load balancing and service discovery over k8s? I guess the broader question is, is micro highly coupled to all of its features/functions or is picking and pulling parts of it workable?
Re: Go Micro v2.4.0 – Go microservices development framework
#26I was just posting this on another forum. But I want to learn more about scalability and availability and microservices. I am quite familiar with fullstack and various databases but I need a hands on experience. Does micro have some sort of tutorials that build microservices from scratch?
Check "Micro In Action" series: https://itnext.io/micro-in-action-getting-started-a79916ae3c... Note: it is based on v1.18 for now. I'll update it to v2.x soon