Adobe Commerce Cloud vs ORO B2B Commerce Cloud architecture
Let's check the architecture of Adobe Commerce a Magento Cloud and ORO Cloud.
Adobe Commerce Cloud Architecture:
Adobe Commerce Cloud was built on the Magento platform. Magento is an open-source eCommerce platform written in PHP. Magento has historically had a free version (Magento Open Source) which anyone can download, self-host, and customize. They also offer managed Enterprise versions (Magento Commerce on-premise and Magento Commerce).
Adobe Commerce Cloud is essentially a bunch of disparate (and single-tenant, but more on that later) pieces of technology from multiple vendors that don’t work well together at a scale where hosing itself provided by Platform.sh.
In 2016 Magento selected Platform.sh to run the Magento Commerce Cloud. Magento didn’t build anything and went to market as a SaaS/PaaS provide using White Platform.sh hosting.
What Adobe was sold on when it bought Magento, was a concept of Magento Commerce Cloud, and after it will rebrand to the Adobe Commerce Cloud with the same broken “cloudy” architecture.
ORO B2B/B2C Commerce Cloud
The Oro Cloud Architecture based on Google Cloud Platform (GCP) Infrastructure-as-a-Service (IaaS). It explains the OroCloud environment infrastructure with its redundant components (such as web node, search index, relational database, and job/message queue) and breaks down topics related to backups, maintenance, disaster recovery, and system configuration.
I have released Terraform ORO Commerce template for AWS infrastructure Provisioning:
