The current features of AWS AppSync are enough for any developer, but it has some areas for improvement. AWS AppSync can provide first-class support for SQL RDS since writing SQL via VTL is clunky and limited. I suggest native richer SQL resolver support because that is what I am looking for in AWS AppSync. My next suggestion is to promote JS-based resolvers as default, which will be better for the development experience since most developers use JS-based resolvers in their day-to-day life. Another suggestion is to provide built-in distributed tracing, which is a must. It needs to have a built-in distributed tracing view so that anyone can see reports and easily trace any issues. I suggest improving VTL debugging enhancement, observability, better SQL resolver support, strengthening local development tooling, promoting JS resolvers, and adding query performance insight could significantly improve the developer experience.
AWS Cloud Developer at Mobil80 Solutions and Services Pvt. Ltd.
Real User
Top 5
Jan 14, 2025
In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial. Regular updates might soon address this need. Currently, incorporating features like IAM roles and permissions during API creation is essential.
I would like to have the ability to run AppSync on-premises. It is entirely AWS at the moment. If you wanted to switch from AWS to Google Cloud or Azure, you can't. You are experiencing significant vendor lock-in. Moving to other clouds is impossible without significantly rearchitecting your applications.
Cloud Data Integration enables seamless data management and connectivity across multiple cloud platforms and on-premises systems, facilitating improved data access and analytics for better decision-making.
Cloud Data Integration offers robust capabilities for unifying data from diverse systems into a single, accessible source. This approach ensures consistency, availability, and streamlined processes across an organization's data ecosystem. Users highlight its ability to tackle...
The current features of AWS AppSync are enough for any developer, but it has some areas for improvement. AWS AppSync can provide first-class support for SQL RDS since writing SQL via VTL is clunky and limited. I suggest native richer SQL resolver support because that is what I am looking for in AWS AppSync. My next suggestion is to promote JS-based resolvers as default, which will be better for the development experience since most developers use JS-based resolvers in their day-to-day life. Another suggestion is to provide built-in distributed tracing, which is a must. It needs to have a built-in distributed tracing view so that anyone can see reports and easily trace any issues. I suggest improving VTL debugging enhancement, observability, better SQL resolver support, strengthening local development tooling, promoting JS resolvers, and adding query performance insight could significantly improve the developer experience.
In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial. Regular updates might soon address this need. Currently, incorporating features like IAM roles and permissions during API creation is essential.
I would like to have the ability to run AppSync on-premises. It is entirely AWS at the moment. If you wanted to switch from AWS to Google Cloud or Azure, you can't. You are experiencing significant vendor lock-in. Moving to other clouds is impossible without significantly rearchitecting your applications.