https://supergraph.io/Recent content on The Supergraph ManifestoHugoen-ushttps://supergraph.io/docs/references/faq/Mon, 01 Jan 0001 00:00:00 +0000https://supergraph.io/docs/references/faq/ FAQ # Supergraph vs alternative approaches # Connect domains Consume APIs Discover demand Technology Connector CI/CD Performance API Composability API portal Analytics Ecosystem integrations API gateway High N/A (no API aggregation features) Low Medium Medium Low IPaaS Low Low Medium Medium Medium Low Data virtualization Low Low - medium (usually designed for analytical workloads) High (usually only for non-API sources) Low (not API driven, usually SQL) N/A (no API analytics) Medium Supergraph Medium to High - depends on stack Medium to High - depends on stack Medium to High - depends on stack High High Depends on stackhttps://supergraph.io/docs/use-cases/federated-data-access-layer/Mon, 01 Jan 0001 00:00:00 +0000https://supergraph.io/docs/use-cases/federated-data-access-layer/Federated Data Access Layer # A federated data access layer (FDAL) is a data access layer that allows flexible and secure access to multiple, independently governed data sources. Typical consumers # FDAL consumers range from consumers that need low-latency, high-concurrency access to realtime data to consumers that need access to analytical data. Experience layer products & microservices BFFs - Backend for frontends Internal products & services - reporting, BI etc.https://supergraph.io/docs/articles/supergraph-in-disguise/Mon, 01 Jan 0001 00:00:00 +0000https://supergraph.io/docs/articles/supergraph-in-disguise/When should you supergraph? # The root problem Consuming data from multiple places requires integration or aggregation work This increases the burden on the producer since it takes time to build and is fragile The problem is combinatorially complex when there are multiple producers and multiple consumers Common symptoms # API consumers are frustrated by the lack of APIs that are optimized for their specific data retrieval use cases API producers are not willing to take on the burden of maintaining and operationalizing API aggregation and composition problems There is no operating model or ownership model for who should solve the integration problem Supergraph in disguise # If you’re working on any of the following projects or strategic initiatives, then you’re likely already building a supergraph.