5 ms·
Dapr's solving distributed systems development at scale. Basically as you grow your team from a handful of people to many separate teams all working on differen
by asim 6y ago
Dapr's solving distributed systems development at scale. Basically as you grow your team from a handful of people to many separate teams all working on different products, the technical architecture also evolves from monolith to SOA and then microservices. It's the natural logical evolution of anything at scale. Dapr is attempting to provide the primitives you'd need to build any sort of software at scale. Usually this buckets into; authentication/authorization, configuration, data storage, pubsub messaging and a handful of other things.
Full disclosure: I'm the author of Micro (https://github.com/micro/micro https://github.com/micro/micro) which bakes in the same primitives but also focuses solely on development in the Go language.
- regularfry 6y agoYes, but what is it? A set of libraries? Container config? A cli tool? You need to dig quite far through the docs to find that out.
- asim 6y agoIt is a server which sits alongside your application. You can access it via http or grpc. They additionally provide multi-language sdks for it. Think database + sdks but for distributed systems.
- e12e 6y ago> It is a server which sits alongside your application. You can access it via http or grpc. Why? If I have microservice A and B - how is A and B different/better with this sidecar?
- reifnir 6y agoIt is a sidecar which sits alongside your application. You can access it via http or grpc. They additionally provide multi-language sdks for it. Think database + sdks but for distributed systems. Most importantly to me, it offers both REST and interface-based programming models allowing the consumer to decide how they want to operate with it.