Team
KML Delivery Zones Epic Breakdown
The scoping session ran over time because of overlooked design considerations. We still need to follow up with the Ecom team on whether we need to validate customer addresses against delivery zones during the pre-validation step. I spent part of the session researching geospatial data types in MySQL to understand how we'd store and query polygon boundaries.
US Products Service Meeting
Discussed whether to build a separate service for US product data or integrate with Canada's existing product service. We're leaning toward integration to make the most of limited dev resources, but there are concerns to address: performance impacts from combining the datasets, handling bulk product updates from aggressive API consumers, event consumers writing to MySQL, building out foreign keys, and authorization differences between US and Canadian platforms.
Investigations
Continued talks with Budvue about their integration issues. They configured their queue to call our API at 750 requests per second, but their integration is only set for 600. Our burst rate cap is currently at 5,000, which we may need to downgrade depending on their actual usage patterns.