Core Service with Dapr utilizes the open-source Dapr framework for simplified development of microservices-based applications. Dapr provides essential building blocks for resilient and scalable distributed systems, including state management and messaging.

1. Core Services with
Dapr
Teesha Jain
Siddhant Vardhan Tiwari

2. Lack of etiquette and manners is a huge turn off.
KnolX Etiquettes
 Punctuality
Join the session 5 minutes prior to the session start time. We start on
time and conclude on time!
 Feedback
Make sure to submit a constructive feedback for all sessions as it is very
helpful for the presenter.
 Silent Mode
Keep your mobile devices in silent mode, feel free to move out of session
in case you need to attend an urgent call.
 Avoid Disturbance
Avoid unwanted chit chat during the session.

3. 1. Understanding Dapr
2. Dapr Building Blocks
3. Dapr Architecture
4. SideCar Architecture
5. Why Do we need Dapr
6. Demo

5. What is Dapr?
 Dapr, stands for Distributed Application Runtime, is an open-source framework designed to
simplify the development of microservices and distributed applications.
 Dapr (Distributed Application Runtime) was developed by Microsoft. It is an open-source project,
and Microsoft has been a key contributor to its development. However, Dapr is a community-
driven project, and contributions come from various individuals and organizations in addition to
Microsoft.
 The project is hosted on GitHub, allowing developers from around the world to participate in its
evolution and improvement.
 Dapr addresses the complexities of building distributed systems, allowing developers to
concentrate on business logic.
 It provides a consistent set of abstractions, ensuring uniformity across distributed application
development.
 Dapr promotes an event-driven architecture, enhancing responsiveness and scalability.

6. Dapr Building Blocks

7. Dapr Architechture

8. Sidecar Architecture
 Dapr exposes its HTTP and gRPC APIs as a sidecar architecture, either as a container or as a
process, not requiring the application code to include any Dapr runtime code. This makes
integration with Dapr easy from other runtimes, as well as providing separation of the application
logic for improved supportability.

9. Why Do We Need Dapr?
 Simplified Development: Abstracts complexities in building distributed systems.
 Language-Agnostic: Allows developers to use their preferred languages and frameworks.
 Event-Driven Architecture: Facilitates easy implementation of event-driven and reactive
architectures.
 Infrastructure Abstraction: Abstracts infrastructure details, ensuring portability across
environments.
 Consistent Building Blocks: Provides standardized components for common distributed system
concerns.
 Ecosystem Integration: Streamlines integration with external services through Dapr bindings.
 Accelerated Development: Speeds up development by offering a runtime for resilient, scalable,
and event-driven applications.