Power Platform architecture notes from real delivery
Patterns we use in production and the failures they prevent: Dataverse schema design, Azure Service Bus integration, Fabric Link and event-driven architecture.
-
Messaging · Integration · Power Platform · Fabric · Dataverse
Dataverse to Fabric Link
External teams want direct database access to your CRM. The answer is no: Fabric Link gives fast, typed, governed access instead.
-
Messaging · Service Bus · Integration
The printer analogy: a story of events
You wouldn't print a million pages 10,000 at a time. So why does this architecture send 100 events, receive 100 responses, and call it event-driven?
-
Power Platform · Dataverse
The Dataverse schema decisions you can't undo
The Dataverse schema decisions that look harmless in week one and become your biggest problem by month eighteen, and how to get them right first time.
-
Power Platform · Messaging · Service Bus · Integration · Dataverse
Don't call external systems directly from Power Platform
Calling external systems straight from Power Automate or plugins breaks under load and fails silently. The Service Bus outbound fix.
-
Power Platform · Messaging · Service Bus · Integration · Dataverse
Don't write directly to Dataverse
Direct integrations into Dataverse lose data, create duplicates and fail silently. The Azure Service Bus inbound pattern that stops all three.