Apollo framework overview prompt

Create a restrained 16:9 editorial technical illustration that summarizes the entire Apollo distributed configuration framework, not a single request trace. Use a clean light background, high contrast, crisp Chinese labels, and a left-to-right control/data flow.

Show five clearly separated zones:

1. Configuration operators and OpenAPI callers entering Portal on port 8070.
2. Portal as the management plane for UI, permissions, audit, environment routing, and release orchestration.
3. Admin Service on port 8090 as the write plane for Item changes, Release snapshots, gray release, rollback, and ReleaseHistory.
4. Config Service and Meta Server on port 8080 as the read plane for service discovery, hierarchical config selection, long polling, HTTP 304, incremental/full sync, and server cache.
5. External Apollo clients as a repository boundary, labeled Java/.NET/other SDKs, with the Java client source explicitly shown outside the apolloconfig/apollo server repository.

Place ApolloPortalDB beneath Portal. Place ApolloConfigDB beneath Admin Service and Config Service, with Item, Release, ReleaseMessage, GrayReleaseRule, and ServerConfig as small data labels. Show the write direction Portal to Admin Service to ApolloConfigDB; show ReleaseMessage scanning from the database to Config Service; show notification and configuration pull from Config Service to clients.

Use distinct but balanced colors for management, write, read, data, and external-client zones. Avoid gradients, decorative shapes, copied logos, screenshots, code listings, tiny file paths, or claims about exact runtime latency. This asset is a conceptual framework summary; precise initialization and request ordering remain in the article's Mermaid diagrams. Keep the result prompt-only until image generation is separately authorized.