Connecting the dots in data and AI systems

Simplifying MLE & MLOps with the FTI Architecture

Paul Iusztin
Decoding ML
Published in
9 min readOct 31, 2024

--

Figure 1: The mess of bringing structure between the common elements of an ML system.

Data and AI systems are a mess.

They are complex and hard to grasp.

If you just started working in AI or have been working for a few years, it’s hard to see how the worlds of data engineering, research (DS, ML), and production (AIE, MLE, MLOps) come together into a single homogenous system.

As a data engineer, you finish your work by ingesting the standardized data into a data warehouse or lake.

As a researcher, your work finishes when you train the best model on a static dataset and push it to a model registry.

As an AIE or MLE, your work finishes when serving the model to production.

As an MLOps engineer, your work finishes when the operations are automated and monitored adequately for long-term robustness.

But is there a more accessible and intuitive way to understand the entire end-to-end data and AI system?

Yes! Through the FTI architecture.

Let’s quickly dig into the FTI architecture and apply it to a production LLM & RAG use case.

Introducing the FTI architecture

--

--

Decoding ML
Decoding ML

Published in Decoding ML

Battle-tested content on designing, coding, and deploying production-grade ML & MLOps systems. The hub for continuous learning on ML system design, ML engineering, MLOps, large language models (LLMs), and computer vision (CV).

Paul Iusztin
Paul Iusztin

Written by Paul Iusztin

Senior ML & MLOps Engineer • Founder @ Decoding ML ~ Content about building production-grade ML/AI systems • DML Newsletter: https://decodingml.substack.com