In our last article, we explored how engineering roles are expanding beyond traditional market data platforms into cloud, AI, observability and enterprise data. As technology estates become increasingly complex, it is important not to overlook another discipline that remains fundamental to every technology platform: operating system engineering.

When people talk about market data infrastructure, the conversation usually focuses on the technologies everyone can see. Real-time feeds, entitlement platforms, monitoring systems, cloud deployments and high-performance networks tend to dominate discussions. Yet every one of those technologies depends on something far more fundamental: the underlying operating system.

Whether it is a real-time distribution system, a monitoring platform, a cloud-native application, an entitlement service or a vendor appliance, none of it functions without a stable, secure and supported operating system (OS) underneath. It is the foundation upon which every market data platform is built.

Like the foundations of a building, it is rarely noticed until something goes wrong. But when problems emerge, unsupported versions, performance bottlenecks, security vulnerabilities or compatibility issues can quickly become major operational concerns. Despite the drive to modernise market data stacks with new technologies such as AI and cloud deployments, operating systems are among the most important yet often overlooked components of the market data stack.

Operating Systems: More Than an Infrastructure Component

At CJC, working at the operating system layer is a continual part of what we do.

For some clients, that means migrating critical platforms away from unsupported operating systems and onto vendor-supported releases. For others, it means helping them make strategic decisions about operating system selection, balancing application dependencies, security requirements, performance objectives and long-term support roadmaps.

These decisions are rarely isolated. Infrastructure teams manage the operating system. Market data teams own the applications. Security teams define compliance requirements. Vendors certify supported configurations.

Success often depends on bringing those perspectives together, and CJC’s role is often to ensure everyone is working towards the same outcome.

Why OS Upgrade Projects Are Rarely Simple

One of the biggest misconceptions in technology is that operating system migrations are straightforward upgrade exercises. Every migration represents a balancing act between security, supportability, operational risk, vendor certification and platform stability.

An organisation may be eager to migrate to the latest version of Red Hat Enterprise Linux to take advantage of security updates and extended vendor support, but business-critical applications may not yet be certified to run on that platform by the vendor. Security teams may prioritise accelerated upgrades, while operational teams prioritise stability and predictability.

The right operating system is rarely chosen because it is the newest available version. It is the one that delivers the best balance of security, supportability, compatibility and operational confidence for a specific environment.

An operating system upgrade is more than a maintenance activity; it represents a valuable opportunity to revisit performance baselines, modernise deployment processes, review automation strategies, and optimise platform configurations to strengthen foundations for future growth.

Performance Starts Below the Application Layer

Performance conversations often focus on the applications themselves, but some of the biggest gains can be found underneath them. In market data environments, where platforms can process millions of updates per second, operating system configurations can directly impact throughput, latency, resilience and scalability.

CPU scheduling, memory allocation, kernel parameters, network stack optimisation and storage performance all influence how effectively a platform performs under load.

For market data teams, this may include tuning interrupt handling, processor affinity, network buffer sizing, TCP stack optimisation, and storage configuration. These settings sit below the application layer and are largely invisible to end users, but their impact on overall platform performance can be significant.

The difference between a default operating system build and a carefully tuned environment is often reflected in lower latency, improved throughput and greater stability when it matters most.

Working Across Modern Deployment Models

The way organisations deploy technology infrastructure continues to evolve.

Traditional server builds have increasingly given way to automated deployment pipelines, Infrastructure-as-Code, configuration management platforms, containerisation and cloud-native deployment models. As a result, operating system expertise today extends far beyond installation and patch management.

Modern operating system engineering involves understanding deployment tooling, automation frameworks, configuration management, version control, testing pipelines and release governance. It means working closely with client engineering teams, cloud architects, DevOps specialists, application owners and third-party vendors to ensure that operating system changes integrate seamlessly into broader technology strategies.

While deployment models and engineering practices continue to evolve, the objective remains the same: delivering secure, supported and high-performing infrastructure.

Practising What We Preach

These challenges are not unique to our clients.

Across CJC's managed services environments, cloud-hosted solutions, observability platforms and internal systems, we handle the same balancing act – security, performance, automation, scalability and operational stability. That operational experience gives us a practical understanding of the realities organisations face. We do not simply advise on infrastructure strategy. We operate and support complex technology environments ourselves.

As a result, our recommendations are shaped not only by consultancy experience, but by hands-on operational responsibility.

Our 24/7 global teams continually evaluate operating system performance, deployment methodologies and automation strategies across both client and internally managed environments. This hands-on experience gives us practical insight into the realities of running modern technology estates, not just advising on them.

“The challenge with an OS migration isn’t simply getting onto a newer release. You have to balance vendor certification, application compatibility, security and operational stability. CJC’s engineers bring those disciplines together, combining market data expertise with hands-on infrastructure experience to help clients make changes that are supportable, repeatable and fit for production.” - Peter Williams, Chief Technology Officer at CJC.

Where CJC Can Help

Operating systems may sit beneath the application layer, but they have a direct impact on security, supportability, performance and resilience. Whether the challenge is migrating to a supported operating system, tuning a high-performance market data platform, modernising deployment processes, supporting cloud initiatives or managing complex infrastructure estates, success depends on getting the operating system layer right.

At CJC, we combine decades of market data expertise with deep infrastructure experience. We understand how applications, operating systems, deployment models and operational performance interact, enabling us to help organisations make informed decisions and deliver successful outcomes.

Planning an operating system migration, reviewing platform performance or modernising your infrastructure estate? CJC's infrastructure and market data specialists can help you build a stronger foundation for security, performance and operational resilience.

We'd be happy to discuss how CJC can help.