WEBSITE DELIVERY IN CHINA
Your CMS, commerce platform, PIM, search and other global systems do not need to move to China just because your visitors are there.
StreamX reacts when those systems change, prepares the content and data your China experience needs, and distributes it to infrastructure inside mainland China before visitors request it.
THE PROBLEM
A website that works well globally can behave very differently in mainland China.
The problem is not only where the page is hosted. Modern websites depend on CMS content, APIs, search, product data, scripts and third-party services. When those dependencies sit outside China and remain part of the visitor request path, every request can become dependent on the cross-border connection through the Great Firewall of China (GFW)
A China-specific domain does not make the systems behind the experience local. If the page still depends on services outside mainland China at request time, cross-border connectivity remains part of delivery.
A mainland-China CDN can serve cached responses locally. It does not move the origin, search, commerce or APIs into China.
If those systems are still needed at request time, the dependency remains.
Pages, APIs, search and other services that perform normally elsewhere can become slow or unreliable when requests cross the border. A page may load, while the services behind it respond seconds later or fail altogether, creating an inconsistent experience for users in mainland China.
Running separately in China often means different infrastructure, services, components or release processes.
Over time, the China implementation becomes another stack that has to be developed, tested, released and maintained alongside the global one.
Monitoring from Europe or the US can show a healthy application while visitors inside China experience slow resources, failed requests or unavailable services.
Without testing from inside China, the delivery problem is easy to miss.
Opening global CMS, PIM, commerce or enterprise systems to requests from China exposes interfaces to systems that often contain far more than public website content.
The same systems may also hold product IP, technical documentation, customer records or supplier data.
THE SOLUTION
StreamX materializes the content and data needed for the China experience and distributes it to the local delivery environment. Lightweight services such as search can run there against locally available state.
This keeps the China stack focused on what needs to operate locally, without duplicating your global CMS, commerce platform, PIM or other systems of record.
Your CMS, commerce platform, PIM and other core systems continue to own the content and data. StreamX connects to their changes instead of recreating those platforms inside China.
StreamX materializes the content and data intended for delivery and distributes that state into China. The delivery environment receives the outputs it needs without exposing the full backend systems behind them.
Some experiences need more than page delivery. StreamX can run dedicated services such as search inside the China environment, using locally materialized data instead of calling a global service at request time.
When content, product data or other source information changes, StreamX updates the affected delivery state automatically. China stays aligned with the global source systems without a separate publishing or synchronization process.
StreamX provides the processing and delivery layer between your global systems of record and your customer-controlled environment in mainland China.
Instead of retrieving content and data from global systems when a visitor in China requests it, StreamX processes source changes as they happen and keeps the required delivery state materialized in the China environment.
1
StreamX reacts to changes from your CMS, commerce platform, PIM and other systems of record.
2
The StreamX service mesh determines what needs to be processed for the China experience when each source changes.
3
StreamX generates the affected pages, product data, search records and other outputs needed for local delivery.
4
Updated state is synchronized to a StreamX Delivery Cluster running in your Bring Your Own Cloud (BYOC) environment in mainland China, where it is available before visitors request it.
Your CMS, commerce platform, PIM and other source systems remain global.
StreamX reacts to their changes and materializes the pages, product data, search records and other delivery state the China experience needs.
Some capabilities still need a local runtime.
Analytics, personalization, identity and other visitor-data services can remain part of the China-specific stack where the use case and data model require it.
INDUSTRIES
This model is especially valuable when China matters commercially, but duplicating the global platform would create unnecessary complexity.
It also helps level the technology playing field. Companies competing with Chinese brands can deliver a more local digital experience without rebuilding their entire global stack inside China.
TECHNOLOGY
StreamX is technology-agnostic at the architecture level. The implementation depends on the systems that own the experience.
CHINA OPERATING MODEL
StreamX provides the technology for materializing, synchronizing and delivering the experience. The broader China operating model remains under the customer's control.
Owns decisions around:
China operating model
applicable registrations and permits
domains and infrastructure
security and data policies
services and data used by the China experience
Provides:
source-system integration
change processing and materialization
synchronization to the China environment
StreamX Delivery Cluster
lightweight experience services such as search
Support the deployment where required, including:
solution development and integration
frontend and application work
mainland-China cloud setup
networking and DNS
security configuration
deployment and operational integration
GETTING STARTED
1
Understand how the current website behaves from inside mainland China.
2
Map the systems, runtime dependencies, data flows and the proposed China delivery boundary.
3
Validate the architecture using your website, source systems and success criteria.
4
Deploy the StreamX Delivery Cluster into your China BYOC environment and connect it to the global publication and data flows.
Answers to some of the most common questions about how StreamX works for China delivery.
No.
A CDN distributes responses through an origin-and-cache model.
StreamX materializes content and data when their sources change and distributes that state to the China environment ahead of the visitor request.
A CDN can still be part of the final delivery architecture.
No. You don’t need to have your ICP filing or license in place before talking to us, but you will need the appropriate ICP status to operate your site from infrastructure in mainland China. If you don’t have it yet, we can factor that in during the project planning.
A CDN caches static assets. It doesn't give you the kind of in-country control MLPS 2.0 asks for over dynamic content, and it doesn't do anything for search or personalization.
No.
The architecture is technology-agnostic. StreamX integrates with content, commerce, product and other source systems through supported connectors and APIs.
Adobe Experience Manager, Edge Delivery Services and Adobe Commerce are supported technology paths.
No, and that's on purpose. China depends on understanding your stack and your compliance status before anything gets scoped, so a sign-up-and-go model doesn't really fit here.
Yes.
Search records are synchronized into an index in the China environment. Visitor queries run against the local index rather than retrieving results from a global search service.
No technology alone determines that.
Applicable requirements depend on the organization's services, infrastructure and data flows. StreamX provides a clear technical delivery boundary that can be assessed as part of the wider China operating model.
Serving materialized website content through StreamX does not require sending visitor personal data to the global CMS simply to retrieve that content.
Identity, analytics, payments, personalization and other services create their own data flows and need to be assessed separately.
Mostly. StreamX doesn't touch how or where content gets authored, it picks up from whatever gets published through your existing CMS. If what you actually need is a fully independent authoring, localization, and approval workflow for a China-based team, that's a different problem than the one StreamX solves.
The China StreamX Delivery Cluster runs using the Bring Your Own Cloud model.
The mainland-China cloud environment is provisioned for and controlled by the customer. StreamX software is deployed into that environment.
Don't duplicate your global platform just to deliver the experience in China.