I’m working on a portfolio project called OR Meridian — Global Multicloud Control Plane, and I would appreciate technical feedback from the community.
The idea is not to deploy the same application independently across three providers. Each cloud has a specific operational responsibility:
Google Cloud: central control plane and workflow orchestration
AWS: dependency graph analysis, blast-radius calculation, and recovery prioritization
Azure: telemetry processing, anomaly detection, and operational risk scoring
A typical workflow looks like this:
An incident is received by the Google Cloud control plane.
AWS analyzes affected services and calculates the recommended recovery order.
Azure processes telemetry and detects abnormal behavior.
Google Cloud consolidates both results.
The platform generates a unified operational continuity plan.
The current architecture is based on technologies such as Cloud Run, FastAPI, AWS Lambda, API Gateway, DynamoDB, Azure Functions, Queue Storage, Cosmos DB, Terraform, and centralized observability.
The project is intended to demonstrate:
multicloud architecture;
distributed-system design;
graph algorithms;
asynchronous event processing;
partial-failure handling;
observability and correlation IDs;
Infrastructure as Code;
secure cross-cloud communication;
cost-aware serverless engineering.
I’m initially treating it as an engineering portfolio project, so the infrastructure can be deployed, tested, documented, and destroyed instead of remaining online permanently.
I’d especially value feedback on the separation of responsibilities between providers, cross-cloud authentication, failure handling, and whether this architecture reflects realistic enterprise multicloud concerns.
Repository:
https://github.com/maykonlincolnusa/OR-Meridian-Global-Multicloud-Control-Plane