使用 KMP 和 SQLite 重构 Myntra App Analytics 持久化

Introduction

引言

In the dynamic landscape of e-commerce, data is the bedrock of decision-making, and app stability is the foundation of user experience. At Myntra, where millions of users engage with our platform daily, ensuring the reliability of both is paramount. This necessity drove us to re-architect a critical piece of our infrastructure: the persistence layer of the Myntra app’s analytics SDK. This post details our journey of augmenting our legacy analytics SDK with a robust new persistence engine backed by SQLite[1], achieving significant gains in app stability and data integrity.

在电子商务的动态环境中，数据是决策的基础，应用稳定性是用户体验的基石。在 Myntra，每天有数百万用户与我们的平台互动，确保两者的可靠性至关重要。这种需求促使我们重新架构基础设施的一个关键部分：Myntra 应用的 analytics SDK 的持久化层。本文详细介绍了我们通过 SQLite[1] 支持的强大新持久化引擎增强遗留 analytics SDK 的历程，从而在应用稳定性和数据完整性方面取得了显著提升。

Background: The Limits of the Legacy Pipeline

背景：遗留管道的限制

For years, our legacy in-house analytics SDK was the workhorse for collecting user interaction data. However, as our app’s event volume grew, the SDK’s aging persistence and processing logic created significant bottlenecks that led to degraded app performance and compromised the reliability of analytics data our product teams depended on.

多年来，我们的 legacy in-house analytics SDK 是收集 user interaction data 的主力。然而，随着我们 app’s event volume 增长，SDK 的老化 persistence 和 processing logic 造成了显著的 bottlenecks，导致 app performance 下降，并 compromised 了产品团队所依赖的 analytics data 的可靠性。

On Android: The Legacy Pipeline and its Limits

Android 上：遗留管道及其限制

On Android, the legacy analytics pipeline followed a straightforward event processing model:

在 Android 上，legacy analytics pipeline 遵循一个 straightforward 的 event processing model：

• Capture, Persist & Batch: Events generated by used actions were held in an in-memory queue and then serialized into a persistent queue backed by SharedPreferences[2]. Once a batch threshold was met (typically 10 events), the batch was dispatched to the server.
• 捕获、持久化 & 批处理： 由用户操作生成的事件首先保存在内存队列中，然后序列化到由 SharedPreferences[2] 支持的持久化队列中。一旦达到批处理阈值（通常为 10 个事件），批次就会被发送到服务器。
• Background...