Blue Lucy Technology

A deep dive into the platform

Architecture The Blue Lucy platform follows a distributed microservices architecture, meaning the overall operational capability is structured as a collection of loosely coupled services. This architecture is robust, resilient and conforms to the separation of concerns paradigm. The singularity of purpose which is a key tenet of separation means the platform is easy to maintain and extend. Equally there are significant opportunities for re-use of components which speeds up our development so that as new business requirements come in - such as a new 3rd party system to connector - we can implement the capability with unparalleled speed.

Overview The overall architecture comprises the database and two core Blue Lucy components: the Application Programming Interface (API) and the Workflow Runner (WFR).

The database is the single data repository of the system with the API and WFR being stateless services which allows automated horizontal scaling. Blue Lucy hosted services are typically deployed in a Highly Available (HA) configuration comprising two API engines and two WFRs arranged behind a load balancer.

The API and WFR The API and WFR are containerised services and will run in any compute infrastructure which means that the platform is not only agnostic to the cloud infrastructure environment in which it runs but may also be run on prem' in any suitable container orchestrator such as Kubernetes. This affords maximum operational flexibility including running cloud-ground hybrid systems - an important capability in an industry in which most systems and media is currently located at the facility. Around 80% of our platform deployments are cloud-ground hybrid. The distributed architecture also supports worldwide operating models for globally distributed business operations.

Microservices Within the platform orchestration layer there is a further abstraction between the WFR and the microservices which perform the operationally specific functions at run time. The microservices are individual executable components in their own right and separate from the WFR itself. This enables the microservices to be developed independently of the WFR and provides an extra level of safety at run-time. This true microservice architecture gives the Blue Lucy business unparalleled development scale and means that microservices may be developed by third parties. Microservices may be updated or new ones applied to live systems without any downtime or interruption, the new services are simply picked up by the WFR when called.

Our microservices run in the WFR and interact with the platform API and the API of the third-party services directly, enabling real time updates between the platform orchestrator and subsystems. There are currently more than 600 microservices available off the shelf of which approximately 250 are integration connectors to media and business systems.

Alongside the microservices the platform also has a range of plugins which are similar in construct and are equally hot pluggable but are designed for the integration of event driven architectures and are deployed as listeners. Examples in use might be a plugin which is subscribed to a message queue listening for specific events, or an HTTP listener to extend the platform's API.

Integrate and extend The platform has an open REST API, which is the same API used by the platform's user interfaces (UI). The API programmatically is supported with embedded documentation created by Swagger and further documentation hosted in the online knowledge portal, Blue Lucy Central, which may be directly accessed within the applications. In addition, a full Software Development Kit (SDK) is available which allows developers to build microservices for the platform.

Available as a package from NuGet, the developer-friendly .NET SDK enables software engineers to code in their preferred IDE, such as Visual Studio, and provides helper features, such as IntelliSense, facilitating rapid and predictable development. The SDK supports rapid learning, with standard methods for accessing data, and provides a safe interface as the commands interact with the Blue Lucy API rather than lower level. The SDK allows developers to use any .NET-compatible library which provides the freedom to integrate any 3rd party component.

Using the SDK is more powerful than simply calling the API, as it utilises the WFR service to perform any 3rd party function or interaction. This has the potential to extend the useful functionality of the platform way beyond the usual media and broadcast systems to drive more business value for operator. The public SDK is the same tool that we use internally for development, so it is proven, robust and is regularly updated. An SDK is also available for Python, and the Python runtime environment is included with the WFR as standard.

Frameworks The platform is underpinned by .NET 10, the latest and fastest .NET framework which affords a truly cross-platform, open source, common language run-time environment. .NET 10 affords long term supportability, an excellent security model and is optimised for containerised deployments providing true enterprise level robustness.

For the tech ops and administrators factory' interface we use the Angular 20 framework from Google and for the production operations hub' view we use React developed and maintained by Facebook. Both frameworks provide an optimal user experience within the operational use cases. SignalR is used extensively in the user interface to provide real-time status updates as it eliminates the need for polling from the front-end to reduce chatter and provides users with instantaneous operational status updates.

For deployed platform observability we conform to industry standards, including supporting OpenTelemetry, to enable c

LINK:	https://bluelucy.com/blue-lucy-technology/...
	See more stories from bluelucy

Most recent headlines