[FlorianRappl]

Thanks for sharing! How is it different to DAPR (https://dapr.io) (besides using a side car to enable all kinds of frameworks instead of just go)? Are the goals similar or actually quite different?

How difficult is it to run it completely independent and on premise (i.e., define custom storage provider etc)? Any examples available? Thanks!

[asim]

I think Dapr has the same goals as Micro. Dapr is from the team who built Azure Service Fabric, which is basically a microservices platform, and with this they've decided to take an open source angle for kubernetes. We're going the other way. Open source is great, but it's not enough. Micro 3.0 is a hosted platform and focused on removing that operation burden but also providing value add higher level services.

I think like most things you either prefer dapr's primitives or ours. As was the same with go-micro vs grpc-go.

Micro can be self hosted. It's an open source project for which you can find the docs here https://micro.mu.