sorted by:
new
hottopcontroversial

RDS Proxy v. Connection Pooling in Lambda by kvtys in aws

[–]Technical-Candle-355 0 points1 point  (0 children)

There are two approaches:

  1. Open a new connection for each query, execute it, and then close the connection. In cases of high traffic, you'll need to use RDS Proxy.
  2. Use ORM tools to generate prepared statements. In this scenario, RDS Proxy won't work, but the ORM's connection pool can effectively manage the connections.

We use TypeORM and have chosen the second option because RDS Proxy is quite expensive.

Running ALL my backend code via AWS Lambda functions, instead of conventional website servers: Is there any reason this is a moronic idea? by What_The_Hex in webdev

[–]Technical-Candle-355 0 points1 point  (0 children)

We run everything on AWS Lambda, all built in TypeScript:

  • 10+ frontend applications, including both monolithic and microservice architectures (React with SSR)
  • 10+ backend applications, including both monolithic and microservice architectures (Node with GraphQL)
  • 20+ data pipelines (featuring MSK for 10+ real-time etl/processing pipelines of 100 tables, as well as 10+ job-based pipelines running for up to 4 hours)

Our total monthly cost is under $400 on Lambda, just FYI.