Pimcore / BigCommerce Connector
Atomicity, Consistency, Isolation, and Durability.
We developed a number of bespoke sync mechanisms to sync the data from pimcore to big commerce
The architecture is push style. Push is always triggers from the pimcore
Different Sync Use cases
- Data Wide Sync - Whole data which is either not synced or got updated after sync, gets synced
- Event based sync - when product gets updated it immediately syncs
- Manual Sync - added a sync button in Pimcore admin UI to manually sync a product to big commerce
- API for Inventory Sync - Very quick and lightweight inventory sync API is developed to cater loads of parallel inventory update requests
The connector makes use of AKS and its scalability services to parallelly process the sync request for products.
Each product sync adheres to ACID(Atomicity, Consistency, Isolation, and Durability). Not just at product level but overall system level as a product update has a wider impact as it can be part of bundles or nested bundles.
Sync also gracefully tackles product type changes. For e.g. a Product/Bundle variant, gets out of bundle and becomes simple product or vice-versa.
To ensure seamless data synchronization between Pimcore and BigCommerce, we developed various custom sync mechanisms tailored to different use cases. The architecture followed a push-style approach, with sync processes triggered from Pimcore. We implemented a comprehensive data-wide sync to handle the initial synchronization or resynchronization of the entire product catalog. An event-based sync mechanism immediately propagates updates to BigCommerce whenever a product is modified in Pimcore.
For manual intervention, we integrated a sync button into the Pimcore admin UI, allowing administrators to trigger on-demand synchronization of specific products to BigCommerce.To cater to high volumes of inventory updates, we developed a lightweight and high-performance inventory sync API, ensuring efficient and real-time inventory management across platforms.
Leveraging Azure Kubernetes Service (AKS) and its scalability features, the connector can process sync requests for multiple products in parallel, optimizing performance and throughput. Adhering to ACID (Atomicity, Consistency, Isolation, Durability) principles, each product sync operation maintains data integrity and consistency, considering the impact on related entities like bundles and nested bundles. The sync mechanisms gracefully handle product type changes, such as products moving in or out of bundles, ensuring seamless transitions.