Platform Architecture
Architecture Reflects Belief
Every architecture encodes a belief about what matters.
Microservices encode a belief about team independence.
Monoliths encode a belief about simplicity.
Event-driven systems encode a belief about responsiveness.
Our architecture encodes a belief about learning.
Learning is the centre of everything.
Not users. Not data. Not AI.
Learning.
The architecture should make this obvious to anyone who reads it.
The Platform Exists to Create Learning
A platform is not a collection of services.
It is a system that creates value.
Our platform exists to create learning.
Every endpoint. Every event. Every computation. Every stored byte.
All of it should contribute to one outcome.
People learning better than they could without us.
If a component cannot explain how it contributes to learning, it should be questioned.
Five Layers of Responsibility
The platform is structured in five layers.
Each has a single, clear purpose.
Each depends only on the layers beneath it.
Each can evolve without disrupting the layers above it.
The Experience Layer
This is where learners, educators and institutions interact with Maigie.
Web applications. Mobile applications. APIs. Integrations.
The Experience Layer has one responsibility.
Presenting the learning environment clearly and beautifully.
It does not contain business logic.
It does not make learning decisions.
It translates the platform into human experiences.
The Coordination Layer
Between experience and learning sits coordination.
This layer orchestrates workflows. Manages sessions. Routes requests. Handles authentication. Coordinates events.
It is the nervous system connecting the surface to the core.
It knows how things flow.
It does not know what things mean.
The Learning Layer
This is the heart.
The Learning Layer contains the domain model.
Learners. Learning Spaces. Classrooms. Courses. Knowledge. Progress. Memory. Relationships.
Every concept that defines our understanding of learning lives here.
This layer makes decisions.
This layer enforces rules.
This layer holds truth.
If the platform were reduced to a single layer, this would be the one we keep.
The Intelligence Layer
Intelligence sits alongside the Learning Layer.
It observes. Remembers. Reasons. Plans. Acts.
It does not own learning data.
It interprets learning data.
The Intelligence Layer makes the platform think.
Without it, the platform stores.
With it, the platform understands.
The Foundation Layer
Beneath everything sits infrastructure.
Databases. Queues. Caches. Storage. Compute. Networking.
The Foundation Layer has one responsibility.
Keeping everything running reliably.
It knows nothing about learning.
It knows everything about availability.
Clear Boundaries
Each layer communicates through defined interfaces.
The Experience Layer never talks directly to the Foundation Layer.
The Intelligence Layer never bypasses the Learning Layer.
The Coordination Layer never makes domain decisions.
Boundaries create clarity.
Clarity enables evolution.
Evolution ensures longevity.
Learning Remains Central
In many platforms, the core becomes hollow over time.
Business logic leaks into the API layer. Intelligence operates independently. The database becomes the source of truth.
We resist this.
The Learning Layer remains the authority.
Intelligence serves it.
Experience presents it.
Coordination connects it.
Foundation supports it.
Learning is always the centre.
Designed for Evolution
No architecture survives unchanged.
Ours is designed to evolve gracefully.
Layers can be rebuilt independently.
The Experience Layer can adopt new technologies without touching the domain.
The Intelligence Layer can adopt new models without changing the learning logic.
The Foundation Layer can migrate infrastructure without disrupting coordination.
This is not accidental.
It is the result of clear boundaries and single responsibilities.
The platform will look different in ten years.
The principles that shape it should not.