Skip to content

Latest commit

 

History

History
30 lines (19 loc) · 2.01 KB

adr-3-data-reader.md

File metadata and controls

30 lines (19 loc) · 2.01 KB
Raw

ADR 3: Use API based synchronous Data Readers

Date: 2023-09-15

Status

Proposed

Context

Choosing between synchronous and asynchronous communication in a software system is a critical decision that can significantly impact system architecture, performance, scalability, and reliability. The choice between these two communication patterns should be made based on Performance, Scalability, Reliability requirements.

Decision

We decided to implement API-based synchronous data readers in our system. This decision aligns with our goals of achieving real-time data access and ensuring that our applications receive immediate responses when querying data. API-based synchronous data readers will provide a straightforward and efficient means of retrieving data, improving the responsiveness and user experience of our applications.

Consequences

Positive

  • Real-Time Responsiveness: Synchronous services provide immediate responses to client requests, making them suitable for scenarios where real-time or near-real-time interaction with the system is essential.

  • Simplicity: Synchronous APIs are typically simpler to design, implement, and use, as they follow a request-response model that is easy to understand and work with.

  • Predictable Latency: Synchronous services offer predictable response times, which can be important for applications where response time is critical, such as user interfaces or interactive systems.

Negative

  • Scalability: Scaling synchronous services can be challenging, as they may require additional resources to handle concurrent requests. Horizontal scaling may be necessary to meet increased demand.

  • Resource Utilization: Synchronous services may hold resources (e.g., threads) for the duration of a request, potentially impacting resource utilization and increasing the risk of resource exhaustion.

  • Complex Workflows: Implementing complex, multi-step workflows with synchronous services can be challenging, as it may involve coordinating multiple synchronous calls.