进化中的Apache Phoenix：克服5个挑战以增加文档数据支持

Written by Viraj Jasani and Kadir Ozdemir.

由Viraj Jasani和Kadir Ozdemir撰写。

Adapting to new demands without compromising reliability is a significant challenge in the fast-paced world of data management. For Salesforce’s Big Data Storage (BDS) team, the mission was clear: transform Apache Phoenix, the backbone of many Salesforce applications, to handle flexible, document-style data while retaining its core strength as a high-scale SQL database.

在快速发展的数据管理世界中，适应新需求而不影响可靠性是一个重大挑战。对于Salesforce的Big Data Storage (BDS)团队来说，任务很明确：改造Apache Phoenix，使其能够处理灵活的文档式数据，同时保留其作为高规模SQL数据库的核心优势。

Originally built on Apache HBase, Phoenix was designed for massive, structured datasets and was optimized for SQL-based querying at scale. However, as Salesforce applications grew to serve varied industries like e-commerce and healthcare, Phoenix’s rigid schema limitations began to surface. The BDS team embarked on a quest to enhance Phoenix’s adaptability by integrating document database capabilities, allowing it to handle complex, unstructured data without sacrificing performance or reliability.

最初基于Apache HBase构建的Phoenix是为大规模、结构化数据集设计的，并针对大规模的SQL查询进行了优化。然而，随着Salesforce应用程序的发展，服务于电子商务和医疗保健等各种行业，Phoenix的刚性模式限制开始显现。BDS团队开始致力于通过集成文档数据库功能来增强Phoenix的适应性，使其能够处理复杂的非结构化数据，而不牺牲性能或可靠性。

This journey, however, was not without its challenges. The team had to navigate the complexities of merging structured and unstructured data handling while ensuring that the system remained robust and efficient. The goal was to create a versatile platform that could meet the evolving needs of diverse industries, all while maintaining the high standards of performance and reliability that Salesforce is known for.

然而，这段旅程并非没有挑战。团队必须在合并结构化和非结构化数据处理的复杂性中前行，同时确保系统保持稳健和高效。目标是创建一个多功能平台，能够满足不同行业不断变化的需求，同时保持Salesforce以高性能和可靠性著称的高标准。

Challenge 1: Balancing Evolution with Stability

挑战 1：在进化与稳定之间取得平衡

The BDS team faced an initial and crucial challenge: ensuring that the new document database capabilities would not interfere with Phoenix’s existing functionality. Phoenix had a depend...