An event-driven, portable runtime for building microservices on cloud and edge
Background Reading
https://github.com/daprhttps://github.com/dapr/dapr
https://github.com/dapr/docs
"A building block is as an HTTP or gRPC API that can be called from user code and uses one or more Dapr components. Dapr consists of a set of building blocks, with extensibility to add new building blocks."
https://github.com/dapr/docs/blob/master/concepts/bindings/README.md
"Using bindings, you can trigger your app with events coming in from external systems, or invoke external systems. This building block provides several benefits for you and your code:"
https://github.com/dapr/docs/blob/master/concepts/bindings/README.md#supported-bindings-and-specs
- Generic
- Cron (Scheduler)
- HTTP
- Kafka
- Kubernetes Events
- MQTT
- RabbitMQ
- Redis
- Twilio
- SendGrid
- AWS Services (see link above)
- Google Services (see link above)
- Azure Services (see link above)
Articles
- 2020
- Most commonly asked questions about Dapr
- Dapr is “An event-driven, portable runtime for building microservices on cloud and edge.”
- "Service meshes are closer to infrastructure layer and operator concerns"
- "Dapr is closer to applications layer which developers are [responsible] for"
- "There is an overlap between Dapr and Service meshes …"
- "It is a `Runtime` that operates along with your application using a sidecar architecture — your application does not run `inside it`. In standalone mode, Dapr simply runs as a different process and in Kubernetes, it runs as a (sidecar) container in the same Pod as your application"
- "(Myth) Dapr depends on Docker"
- Dapr Distributed Application Runtime with Azure CTO Mark Russinovich
- 2019
- Announcing Distributed Application Runtime (Dapr), an open source project to make it easier for every developer to build microservice applications
No comments:
Post a Comment