Case Study Deskcasestudydesk.com
Cloud softwareSourced

Case Study: Invenco cut database costs to one-sixth after leaving Aurora Serverless v2 for Neon

Invenco Case StudySourced & dated by Case Study Desk
Key facts · TL;DR
Company
Invenco
Industry
Cloud software
Challenge
Aurora Serverless v2 caused Lambda connection issues and costly, complex non-prod environments.
Headline result
Invenco migrated from Amazon Aurora Serverless v2 to Neon, ending Lambda connection issues and cutting database costs to about one-sixth.

Key results

80%
Lower database cost
Neon at ~1/6 of prior AWS cost
1/6
Of prior AWS cost
vs Amazon Aurora Serverless v2

The challenge

Invenco ran its databases on Amazon Aurora Serverless v2, where hundreds of AWS Lambda functions caused connection issues and non-production environments were complex and expensive to duplicate per service.

The solution

Invenco migrated to Neon, consolidating non-production services into a single Neon project and using branching to spin off child environments from a shared staging branch. Neon handled the Lambda connections without the issues seen on Aurora.

Neon worked out of the box, handling hundreds of Lambdas without any of the connection issues we saw in Aurora Serverless v2. On top of that, Neon costs us 1/6 of what we were paying with AWS

CJ
Cody Jenkins
Head of Engineering, Invenco

The results, in context

Invenco reported that Neon costs about one-sixth of what it paid on AWS, an approximately 80% reduction, while handling hundreds of Lambdas without the connection issues it had on Aurora Serverless v2.

Products used

Neon Neon PostgresNeon Neon Branching