Pain Points Will Always Outlive Platforms

痛点永远比平台更长久

We wanted to sell software licenses to customers in over 120 countries without any payment restrictions. The platform stores we had been using didn’t allow direct sales in certain countries due to sanctions and regulatory compliance issues. 我们希望向全球 120 多个国家的客户销售软件许可证，且不受任何支付限制。由于制裁和监管合规问题，我们之前使用的平台商店不允许在某些国家进行直接销售。

The Problem We Were Actually Solving: Our architecture was designed to handle the complexities of international payment processing, but the platform stores’ limitations kept us from reaching a significant portion of the global market. Our revenue was stagnant, and we couldn’t grow our customer base as much as we wanted. We had to decide whether to work around the limitations of the platform stores or create our own infrastructure to handle direct sales. 我们真正要解决的问题是：我们的架构旨在处理国际支付处理的复杂性，但平台商店的限制使我们无法触及全球市场的很大一部分。我们的收入停滞不前，无法按预期扩大客户群。我们必须决定是绕过平台商店的限制，还是建立自己的基础设施来处理直接销售。

What We Tried First (And Why It Failed): Initially, we tried using third-party solutions that allowed us to bypass the payment restrictions, but these solutions came with high transaction fees, which cut into our revenue margins. We also implemented workarounds to manually process payments from restricted countries, but this introduced errors and inconsistencies in our bookkeeping. The system was brittle and prone to failures, and our customer support team was overwhelmed with inquiries about payment issues. 我们最初的尝试（以及失败原因）：起初，我们尝试使用第三方解决方案来绕过支付限制，但这些方案伴随着高额的交易费用，压缩了我们的利润空间。我们还实施了一些变通方法来手动处理受限国家的支付，但这导致了账务处理中的错误和不一致。系统变得脆弱且容易故障，我们的客户支持团队也被大量的支付问题咨询所淹没。

The Architecture Decision: After months of struggling with the limitations of the platform stores, we decided to build our own infrastructure for direct sales. We chose a headless e-commerce architecture with a RESTful API for payment processing and a modern warehouse as the data storage layer. This allowed us to handle payments and bookkeeping in a centralized location, eliminating the need for third-party solutions and manual workarounds. We also implemented robust error handling and monitoring to ensure that our system could withstand the increased traffic and volume of sales. 架构决策：在与平台商店的限制斗争了几个月后，我们决定构建自己的直接销售基础设施。我们选择了无头电商（headless e-commerce）架构，利用 RESTful API 处理支付，并采用现代数据仓库作为数据存储层。这使我们能够在中心化位置处理支付和记账，消除了对第三方解决方案和手动变通的需求。我们还实施了强大的错误处理和监控机制，以确保系统能够承受增加的流量和销售量。

What The Numbers Said After: Our pipeline latency decreased by 30% after the transition to our own infrastructure, allowing us to process payments and fulfill licenses in real-time. Our query cost on the warehouse decreased by 50% due to the improved architecture and data storage. We were able to hit an average freshness SLA of 5 minutes for our sales data, which gave us more accuracy and confidence in our business decisions. Our team experienced a significant reduction in support requests and errors, freeing up resources to focus on growth and innovation. 转型后的数据表现：在迁移到我们自己的基础设施后，我们的流水线延迟降低了 30%，使我们能够实时处理支付并交付许可证。由于架构和数据存储的改进，我们在数据仓库上的查询成本降低了 50%。我们的销售数据平均新鲜度 SLA 达到了 5 分钟，这使我们在商业决策上更加准确和自信。我们的团队收到的支持请求和错误报告显著减少，从而腾出了资源专注于增长和创新。

What I Would Do Differently: In hindsight, I would have started with a more incremental approach to building our own infrastructure. We should have begun by migrating a small subset of customers to our new system and monitoring their behavior and feedback before scaling up. This would have allowed us to identify and address potential issues earlier in the process. I would also have invested more in automated testing and CI/CD to ensure that our new system was thoroughly tested and validated before going live. By taking a more incremental and iterative approach, we could have minimized the risks and downtime associated with the transition and ensured a smoother experience for our customers. 如果重来一次，我会怎么做：回过头看，我会采取更渐进的方式来构建自己的基础设施。我们应该先将一小部分客户迁移到新系统，并在扩大规模前监控他们的行为和反馈。这将使我们能够更早地发现并解决潜在问题。我还会投入更多精力在自动化测试和 CI/CD 上，以确保新系统在上线前经过充分的测试和验证。通过采取更渐进和迭代的方法，我们可以最大限度地减少转型带来的风险和停机时间，并确保为客户提供更顺畅的体验。