Publishers that want to deliver content flexibly, quickly, and across every channel must think about their publishing infrastructure at the same time: a technologically future-proof foundation that delivers content with high performance, low latency, and strong security while scaling as demands grow. <\/p>\n\n\n\n
Josef illustrated this approach using the example of CH Media, where a change of ownership required the existing technology platform to be replaced under significant time pressure. He explained that the situation had been used as an opportunity to establish IT as a driver of innovation. What began as a technical necessity became the starting point for an entirely new architecture. <\/p>\n\n\n\n
The core architectural decision was to strictly separate content creation from content delivery and connect the two through an event-driven Content Delivery Hub. On one side are editorial teams publishing through a headless CMS supported by planning tools and AI-powered auto-tagging. On the other side are millions of readers accessing content via the web, native apps, and e-paper. <\/p>\n\n\n\n
Josef explained that the rationale behind this separation comes down to a striking imbalance: content changes only a handful of times a day, while the system handles hundreds of read requests every second \u2014 a ratio of roughly 1,000 to 1. A central hub that decouples the two sides and serves them independently reduces the load on the infrastructure while lowering operating costs. <\/p>\n\n\n\n
Josef’s second point focused on the role of AI. Rather than implementing AI services as scattered, standalone solutions across the system, he argued for managing them centrally within the Content Delivery Hub. He emphasized that publishers need to learn to manage these services in a unified way. <\/p>\n\n\n\n