- 最新
- 最多得票
- 最多評論
Hey! AppSync, including its merged API feature, may indeed be used in production environments. It's especially effective for serverless architectures, offering scalable, secure, and real-time data synchronization capabilities that integrate seamlessly with other AWS services, making it a robust choice for deploying serverless applications at scale.
I would recommend you to watch this video Serverless Berlin Meetup - Yan Cui - Lessons from running AppSync in production. In this video Yan Cui (AWS Serverless Hero) explain his lesson from running AppSync in production it could help you to answer many of the question it can surge in the way.
Can we merge APIs from different AWS accounts into one AppSync API for data source navigation?
Yes, it's possible to merge APIs from different AWS accounts into one centralized AppSync API. This setup involves configuring a single AppSync endpoint to route requests to the appropriate data sources across multiple accounts, based on custom logic within AppSync resolvers and using AWS IAM roles for secure cross-account access.
Can we create a unified API endpoint to access data sources across multiple accounts?
Indeed, you can consolidate APIs into one AppSync API endpoint, allowing users to access data from multiple AWS accounts through a single interface. This approach simplifies client interactions by providing a unified schema and endpoint, with careful attention to cross-account security and access control.
相關內容
- 已提問 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前