Development and Orchestration of Services

Ferris Executor (FX) is the core platform service, built to develop, orchestrate, deploy and even operate event based applications. With the Executor, teams build and operate fully automated service flows such as data ingestions, data quality, cross-cloud processes, large language models (eg. ChatGPT), or refactoring of legacy services.

The unique low learning curve approach significantly reduces the cost of deploying enterprise wide process and integration pipelines across disparate systems at speed. While at the same time creating a platform with practically unbound access and ease of integration.

FX is a ground-up rethink of how both sync and async microservices are built in multi-cloud, highly volatile and fragmented software environments.

On FX you are effectively writing large applications by connecting “blocks” of code (services) through events. An approach that is highly intuitive and in line with iterative agile practices.

Learn more

Streaming Automation and Edge Adaptors

Ferris is built as an Event based Serices Architecture, combing the notion of events (triggers) and services (individual tasks). In simple terms, it is a system where different components or services communicate and respond to events. Events are occurrences or notifications that can trigger specific actions or processes. Instead of services constantly polling or checking for updates, they subscribe to events and react when those events occur.

Examples of events may be the simple user registration in a web service, a stock trade on an exchange service, or the updating of patient records in a hospital system.

The end result of combining events and services are fully automated business processes, whereas the combination and orchestration of event and services chains are open and sheer endless.

A large and growing number of pre-built Edge Adaptors facilitates a fast and easy integration of source systems with Ferris. Where there are no pre-built adaptors, new ones can be built using Edge Templates.

Learn more

Kubernetes Platform

Ferris has incorporated Kubernetes as a fundamental element in its technology stack, streamlining the implementation of Ferris across diverse infrastructures. This includes setups such as cross-cloud, multi-cloud, and inter-cloud configurations.

In the realm of Kubernetes setups, there are two distinct flavors, each complementing the other:

• Firstly, there's the basic Static Container Management setup, offering extensive container orchestration capabilities across various clouds and programming languages.
• Secondly, the Event-driven Kubernetes setup supports services and automations triggered by events. In this configuration, pods remain dormant until awakened by specific trigger events. This approach ensures optimal resource utilization, keeping potentially expensive cloud compute resources at a bare minimum.

Ferris also introduced the Kubernetes based concept of " ephemeral events management," signifying that events occur fleetingly, lasting only for a brief moment. To accommodate this brief duration, Ferris has created a technology facilitating cross-cloud and multi-language events management. This technology is ultra effective, using a bare minimum of compute resources and allows for the flexible orchestration of events and services, regardless of their origin.

Learn more

Ferris Technology

The Ferris technology architecture is based on open technology components and standards to accomodate a maximum of openness and integration capabilities. We maintain strictr architecture and design principles to ensure:

• Scalability and performance
• Architectural flexibility
• Easy integration with other systems
• Reusability of any and all assets
• Engineering and DevOps autonomy
• Infrastructure resources efficiency
• Avoiding technology lock-in!

The Ferris Platform is built to serve enterprise grade applications. Integration, performance, realiability and robustness as well as a high degree of security are therefore core to our standards.

While we use open technologies and standards, such as Kubernetes and Kafka, we always aim to advance these technologies and make them even better!

Learn more