Skip to main content

SMDS-ADR-001

StatusIN PROGRESS
ImpactHIGH
Driver
Date26 Aug 2024

Decisions

  • SMDS CMD - Geo V2 API Latency

Context

SMDS CMD is a key consumer of the SMDS Geo V2 API, which is essential for geography data integration and validation during customer and facility onboarding. Previously, SMDS used the Geo V1 API, but since migrating to V2 in September of last year, several issues have surfaced.

The migration introduced backward compatibility challenges, leading to data inconsistencies when dealing with earlier versions. These discrepancies have impacted the accuracy of geographical data, crucial for our operations. Additionally, the Geo V2 API has experienced latency issues, creating bottlenecks in the onboarding workflow and affecting overall efficiency.

While CMD has implemented alternative approaches to mitigate these challenges, the issues with data consistency and latency persist. It is essential to continue working closely with the Geo team to explore solutions and ensure the smooth operation of SMDS CMD.

Discussion Topics

  • Architecture and Design of the Geography API
  • Database Profiling and Schema Design
  • API Integration between CMD and Geo
  • Payload Analysis and API Performance Review

Action items

  • Configure Level 1 (L1) and Level 2 (L2) caching.
  • Partition data based on the active/inactive flag.
  • Review and optimize indexing strategies.
  • Improve data pruning and join operations for better performance.
  • Analyze and optimize access patterns to enhance efficiency.
  • Evaluate current queries for performance issues and apply necessary optimizations.

Participants

Sumeet Shekhar Atul Raj Ajit Vijay Daware Gopala Krishnan Rajendran N N Hemanadha Reddy Naga Eswari Gundubogula Harshit Chouhan User f2cfd

Ramesh Varma KutcherlapatiPriyanshu Roy Srikant Sahoo Snehal Kale Sudhir Kumar Kunchakuri Yashwanth Kurru (Deactivated) Rahul Singh

:solution-architecture: References

Was this page helpful?