dapr VS go-micro

Compare dapr vs go-micro and see what are their differences.

dapr

Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge. (by dapr)

go-micro

A framework for distributed systems development (by asim)
Our great sponsors
  • SonarQube - Static code analysis for 29 languages.
  • Scout APM - Less time debugging, more time building
  • OPS - Build and Run Open Source Unikernels
dapr go-micro
34 12
16,614 17,504
6.1% -
9.8 9.3
5 days ago 6 days ago
Go Go
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

dapr

Posts with mentions or reviews of dapr. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-01-11.
  • Azure Container Apps - CI/CD deployments (Video Demo)
    3 projects | dev.to | 11 Jan 2022
    Azure Container Apps is a container orchestration platform for deploying modern applications and microservices. With Azure Container Apps you can deploy your containerized apps without the need to take on the overhead of managing the infrastructure of the underlying systems. This service is still in preview, but provides you with the ability to use your preferred language or framework to build microservices with support for Distributed Application Runtime (Dapr). There's also scaling of your containers with Kubernetes Event-Driven Autoscaling (KEDA).
  • What is the new equivalent of microsoft message queue
    1 project | reddit.com/r/csharp | 3 Jan 2022
    If you are looking for a unified way to build this across different clouds, you could look into DAPR https://dapr.io/
  • Is developing microservices in .net is heavily dependent on Azure?
    2 projects | reddit.com/r/csharp | 31 Dec 2021
    Take a look at DAPR if you are looking for a conceptual Queues, Storage, Pub Sub etc without being tied to any particular infrastructure. https://dapr.io/
  • Azure Service Bus
    1 project | reddit.com/r/AZURE | 2 Dec 2021
    This sounds like something you can do with Dapr (https://dapr.io/) It's a microservice architecture that was developed by Microsoft i think and now open-source. It has build in support for communication between services. I don't know your architecture/landscape or the requirements, but maybe this could work for you. If not, yeah queues could work. Setup a listener on startup for the specific queue and you should be good. Keep scaling in mind, I think there was a limit to the number of listeners is possible on a queue (1 per partition or something)
  • FOSS News International #2: November 8-145, 2021
    6 projects | reddit.com/r/fossnews | 15 Nov 2021
    Dapr is a set of APIs that makes it easy for developers to write distributed applications. Dapr runs as a sidecar process next to an application, whether on Kubernetes or any other environment.
  • gRPC Development experience in modern .NET
    7 projects | reddit.com/r/dotnet | 12 Nov 2021
    Think i agree that the tooling is a little behind for .net and gRPC but it isn't bad. Are you also cutting the monolith into smaller pieces you might want to look at https://dapr.io/
  • Next.js 12
    27 projects | news.ycombinator.com | 26 Oct 2021
    I guess https://dapr.io/ could also be considered a contender in that space, though the developer experience is not as polished as next.js (yet?).
  • Show HN: Scaffoldly – Serverless APIs on AWS, in Minutes
    1 project | news.ycombinator.com | 21 Oct 2021
    Very cool project. It reminds me a bit of https://dapr.io (even though they're obviously quite different).

    One tiny note on the docs - I found it surprisingly hard to find the github repo for the project listed in the docs. I was expecting to find a GitHub link under contributing but only saw a slack channel. I eventually spotted a link in the Roadmap section.

  • Do you guys use frameworks with Go for backend development?
    7 projects | reddit.com/r/golang | 8 Oct 2021
    https://dapr.io/ might be a fit sometimes
  • From Monolith to Microservices and Beyond
    5 projects | dev.to | 5 Oct 2021
    Projects like Dapr aim to be the Holy Grail for application development. Their goal is to help developers build resilient services that run in the cloud. By codifying best practices for building microservices into independent and agnostic building blocks that can be used only if necessary, they allow services to be built using any language or framework and run anywhere.

go-micro

Posts with mentions or reviews of go-micro. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-01.
  • Go Micro – A framework for distributed systems development
    1 project | reddit.com/r/CKsTechNews | 31 Dec 2021
    1 project | news.ycombinator.com | 31 Dec 2021
  • Go Micro - A framework for distributed systems development
    1 project | reddit.com/r/microservices | 31 Dec 2021
    1 project | reddit.com/r/golang | 31 Dec 2021
  • Show HN: Go Micro – a Go framework for distributed systems development
    1 project | news.ycombinator.com | 1 Nov 2021
  • Go Micro - a framework for distributed systems development
    3 projects | reddit.com/r/golang | 1 Nov 2021
  • Show HN: A microservice framework, listed in CNCF Landscape, 1 year 10k+ stars
    5 projects | news.ycombinator.com | 20 Sep 2021
    Been striving in the way of micro services for a few years. My contribution is https://go-micro.dev (17k stars)
  • Why and how we built Distributed with Next.js and Micro
    8 projects | dev.to | 26 Mar 2021
    Distributed is a live social chat app built as a Jamstack demo using Next.js and Micro. We built it to demonstrate the value proposition of M3O - a cloud platform for API development. This post explains what went into building Distributed in just a few weeks and how M3O helped rapidly build our MVP. You can find the source code for distributed on Github. If you want to build and host your own version signup to M3O and start running the same services from our open source repository micro/services. Why we built Distributed Distributed was built as a jamstack demo to show how you could leverage M3O as an API backend for rapid MVP development. M3O itself is a cloud platform for API development, built on the popular open source project Micro. Micro enables you to quickly build APIs in Go on the backend and M3O provides simple free hosting of those services. We wanted to show the Jamstack audience how you could quickly leverage those APIs to build something on the frontend. Not only that, we really wanted to understand and experience the frontend developers perspective through dogfooding of our own APIs rather than just throwing stuff over the wall and hoping it works. Hopefully in that we we've done is demonstrate the value of our platform and how others can also make use of it with a real world app like Distributed to learn from. Let's talk more about Jamstack now. Jamstack Development Jamstack is a new architecture pattern for frontend which offloads dynamic aspects of the stack to javascript and third party APIs. Vercel, the makers of Next.js and related companies are pioneering the way forward for jamstack development. Credit jamstack.org JAMstack stands for Javascript, API and Markup. The static part of the application is deployed to a CDN with javascript dynamically loading various pieces of dynamic content from backend APIs and rendering it. Why we chose Next.js Next.js is a massively popular react based framework for Jamstack development. When we were looking at building out a demo on top of M3O we had the choice of going down a number of routes but what really appealed to us was the how deliberate a lot of the choices were in how the Vercel team had constructed the Next.js framework. Being framework creators ourselves with the dominant framework Go Micro for Go, we could appreciate the efforts required and strong opinions needed to drive such adoption and success. Vercel has done a phenomenal job in this way. Beyond praising Vercel's efforts. The Next.js framework includes a lot of key components needed for the Jamstack including server side rendering, api routes and typescript support. For us these were mandatory feature requirements when building against not only our APIs but third party providers. Micro for the Backend Micro is an open source cloud platform for API development. With modern day complexity in writing software for the cloud, Micro has attempted to distill that down to a handful of primitives and a framework for building services in Go. Micro took learnings from the original Go Micro framework and focused on not just gRPC based service development but actually packaging together a runtime and platform which exposes those services automatically as APIs. What this means is we can write microservices on the backend using gRPC and protobuf and immediately provide value to consumers and clients on the frontend via HTTP/JSON. To learn more about that check out the project at micro.mu or the hosted platform at m3o.com. Building on Netlify We initially chose Netlify for hosting as we saw many people adopting it for Jamstack apps. Initially this proved really great for static content. As our apps got more complex and we started to build out the Distributed demo we found Netlify no longer scaled with our basic needs. The first example we can share is Netlify Functions for Next.js API routes. Next.js routes can be turned into Netlify Functions which are essentially hosted as AWS Lambda functions. It's a clever way of pushing certain requirements to the server side, like calling third party APIs with keys you don't want to expose to the client. Next.js is great in this regard and plugins like netlify-plugin-nextjs and next-on-netlify let us do this really quickly but the performance left a lot to be desired. Our APIs are primarily hosted in London on DigitalOcean and while Netlify has a CDN for static content, the Lambda functions are deployed in a single region in US-East on AWS. For those who've suffered this pain you know exactly what that means. We were making cross atlantic calls from JS in the client to api routes on lambda and then finally to our apis. Needless to say this didn't scale for us. We weren't able to reach out the Netlify team to get help and so in frustration had to go down the self hosted route. Note we did test out Vercel and found the experience to be faster but self hosting on DigitalOcean just made more sense for our demo needs. Switching to Self Hosted One of the things DigitalOcean now provides is App Platform, a container hosting solution which lets you pick regions, does TLS certificate management for your custom domain and automatic builds from Git. This turned out to be a perfect solution for self hosted Next.js apps. Next.js at the end of the day is a React and node.js based application. As much as you may want to separate out the static content to something like Netlify and functions on Lambda, it equally just makes sense to host the entire thing in one place and run many copies of it much like we did in the old php and rails days. Because the APIs are colocated with the frontend we find this experience fairly fast, sub 100ms for all the API calls but we know it's not an ideal demonstration of the Jamstack's architecture and so we'll be working towards hosting on Vercel in the future to showcase that experience. How It All Fits Together We're running Distributed as a Next.js application on the frontend talking to Micro APIs on the backend. All of this is constructed as API routes in Next.JS firing requests at our M3O platform and the various APIs we need. Let's walk through a typical request. For example, when loading a group we need to get the group info, user profile, chats and more. We could do this as a GraphQL APIbut that would require too much stitching together in terms of the schema on the backend. Instead we're using protobuf and RPC for rapid development there and Micro automagically exposes that as a HTTP/JSON API. So a typical flow is like so. Frontend makes a request to /api/groups/[id] which loads the api code in the Next.js app We validate the user is logged in by calling the /users/Validate endpoint and ff authenticated load the group data by id using /groups/Read Skipping ahead, we'll load group messages via /threads/ListConversations and private messages using /chats/ListMessages We can check for already read messages via a "seen" API and then subscribe to the streams API for instant messaging Finally we render everything based on the content loaded for the user .gist-data { max-height: 600px; overflow: auto;} Here's a code "snippet" for those interested. From an MVP standpoint this is just a very quick and rapid way for us to build against numerous separate APIs on the backend all hosted in the same place. For anyone interested in the "call" function. It's simply a small function we're using to call the Micro APIs on the backend. Remember Micro turns any RPC based service into a HTTP/JSON API automatically via an API gateway. M3O provides hosting for all this. Performance & Productivity Aside from the structural benefits of a framework like Next.js we find it really unlocks significant productivity by providing an opinionated approach to frontend development. That coupled with Micro on the backend and our APIs hosted on M3O it's enabled us to rapidly ship this MVP within the space of 4-6 weeks with mostly 1 person doing the work. That really speaks to the power of the combination of Next.js and Micro. For this demo we built APIs for user management, group messaging, websocket streaming, sending invite emails and audio/video through Twilio WebRTC. One can only imagine where it would go with a dedicated team and full product focus. On the performance side, Next.js is blazingly fast by all measures. Whether it be the local reload for development or the server side rendering. It all adds to a really snappy experience on both the development and consumption side of things. With the backend we tried to pair this with Go based APIs written with Micro to ensure not just speed of development but also speed of delivery. All in all, we think Next.js and Micro are the perfect pairing for any Jamstack and API based development. Conclusions Thanks for reading this post on how we built Distributed on the Jamstack using Next.js and Micro. Find the source code for distributed on Github. If you want to build and host your own version signup to M3O and start running the same services from our open source repository micro/services. Reach out on slack or twitter if you have any questions.
  • Most popular web framework in Go
    2 projects | reddit.com/r/golang | 19 Mar 2021
    1) A lot of features are not necessary because standard library has all of the base needs and some more covered. If not, there are some great libraries like micro to help take care of the rest.
  • What library or framework is used to write microservices for production ?
    7 projects | reddit.com/r/golang | 14 Feb 2021

What are some alternatives?

When comparing dapr and go-micro you can also consider the following projects:

tye - Tye is a tool that makes developing, testing, and deploying microservices and distributed applications easier. Project Tye includes a local orchestrator to make developing microservices easier and the ability to deploy microservices to Kubernetes with minimal configuration.

micro - A distributed cloud operating system

go-zero - go-zero is a web and rpc framework written in Go. It's born to ensure the stability of the busy sites with resilient design. Builtin goctl greatly improves the development productivity. [Moved to: https://github.com/zeromicro/go-zero]

Nomad - Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.

grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC

go-kit - A standard library for microservices.

OpenFaaS - OpenFaaS - Serverless Functions Made Simple

camel-k - Apache Camel K is a lightweight integration platform, born on Kubernetes, with serverless superpowers

gocelery - Celery Distributed Task Queue in Go

torrent - Full-featured BitTorrent client package and utilities

Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.

phoneinfoga - Information gathering & OSINT framework for phone numbers