Storage layer - Your storage choices for the services. Services Layer - Services such as session, search, account, inventory, orders, and so on. Presentation layer - Your single-page application (SPA) builder and content. Think about implementing the platform with smaller services separated into four layers: How would you then progress to a modernized fully containerized microservices architecture? Well, you can check out the complete architecture in this video, but here is a summary. Or maybe you are building an entire modernized commerce platform from scratch. Let’s say you have migrated to Google Cloud using GKE or Compute Engine. Here is a sample architecture for migrating and improving your commerce platform using GKE.Ĭlick to enlarge c. But once you’ve migrated, you’ll realize the benefits of a cloud-native, containerized architecture, including easier maintenance, improved flexibility, and scalability. This approach requires more changes than migrating your existing solution as-is. Migrate (and improve) your existing solution to a microservices architecture that uses containers and managed services in Google Cloud. This minimizes the changes required to get to the cloud, but you don’t get the benefits of a microservices architecture.ī. Migrate your existing solution as-is by hosting your existing solution in Google Cloud instead of running it in your own data center. There are three main ways to implement this approach: a. With the build-your-own approach, you assemble your own solution using building blocks from Google Cloud, including AI / ML tools and data management tools. Build your own commerce platform on Google Cloud For more on this sample architecture, see this short tutorial that walks you through the integration.Ĭlick to enlarge 2. Here is a sample architecture of a headless commerce implementation on Google Cloud using Commercetools, a Google ISV partner, as a backend and Cloud Run or Google Kubernetes Engine (GKE) as the frontend. Maintain consistent performance for the end-to-end client experience as you apply updates to the frontend. Make nimble updates to the frontend while maintaining compliance with security and other standards. first-party data) and then use that data to gain insights into shopping behavior and activate data-driven, personalized offerings to increase sales conversions. Update the client-facing site (for example, to handle seasonal campaigns) without needing backend skills and without risking regressions in the backend processing. When you decouple the backend from the frontend in a headless commerce approach it becomes easier for your teams to: Headless commerceĪs a retailer you might want to own and control the frontend for providing an engaging and differentiated shopping experience, and use ready-to-use backend commerce building blocks for capabilities such as product catalog and cart functionality, pricing, promotions, shipping, and account management. Let’s take a closer look at each of these approaches. The three main approaches to modernizing your digital commerce platform are headless commerce, build your own, and out-of-the-box.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |