API Gateway

AWS services exhibit inconsistent API naming conventions (List vs Describe vs Get), response formats (items vs item), and field naming (StreamName vs StreamARN, CreationTime vs other patterns). This inconsistency forces developers to constantly refer to documentation, increases mental load, reduces code reliability, and can introduce production bugs when assumptions fail.

Developers often start Lambda projects without frameworks, forcing manual setup of API Gateway and CloudWatch integrations. As architectures grow, the 50MB default deployment size limit becomes a constraint, requiring webpack bundling per function to stay under limits and improve deployment speed.

Deploying an app requires managing resources scattered across different AWS console sections (S3, CloudFront, Route 53, EC2/Fargate/Lambda+API Gateway, RDS/DynamoDB, billing alarms). These services don't integrate well out-of-the-box, forcing context switching and manual coordination.