Code implementation

[emindsajay]

Description

Implement code changes to optimize the Protocol Server latency, improving API response times, request handling, and overall system efficiency. The optimization will be based on the approved approach document and will focus on reducing response delays, optimizing database queries, implementing caching strategies, and enhancing concurrency management.

Goals

• Implement code modifications as per the approved optimization strategy
• Optimize API response times and reduce latency
• Improve database query performance and indexing
• Implement caching strategies to reduce redundant processing
• Optimize request handling and concurrency management
• Ensure protocol compliance and seamless interoperability

Expected Outcome

A highly optimized Protocol Server with significantly reduced latency, ensuring faster API responses and improved efficiency without affecting existing functionalities.

Acceptance Criteria

• Code changes for API optimization are implemented
• Performance benchmarks confirm latency improvements
• Functional testing ensures no regressions or breaking changes
• Protocol Server successfully interacts with multiple BPPs

Mockups / Wireframes

NA

Product Name

Beckn

Domain

TBD

Tech Skills Needed

Backend Development, API Performance Optimization, Database Query Optimization, Caching Strategies, Load Testing

Complexity

High

Category

Performance Optimization

Sub Category

Protocol Server Enhancements

[emindsajay]

PR is raised: #251

[emindsajay]

This implementation introduces a streaming response mechanism for search requests. When streamOnSearch is enabled, responses will be streamed in real-time instead of being stored in SyncCache. This improves response times and allows clients to process data incrementally.

1. Configuration Update

• A new configuration flag streamOnSearch is introduced under app settings.
• When streamOnSearch: true, the system streams responses instead of storing them in the cache.

2. Emitting Search Event

• When streaming is enabled, responses are emitted using eventBus:

  • If streaming is enabled, onSearch event is emitted.
  • If disabled, the response is stored in SyncCache.

• Opens a streaming connection when streamOnSearch is enabled.

• Listens to onSearch event and writes responses as they arrive.

• Ends the stream after the waitTime timeout.

Testing & Validation

• Enable streamOnSearch: true and verify real-time responses are streamed.
• Disable streamOnSearch: false and confirm responses are retrieved from SyncCache.
• Validate proper event cleanup to prevent memory leaks.