← Back to context Comment by moneywoes 5 years ago Silly question but how does this compare to SQS? More cost friendly I assume? 1 comment moneywoes Reply rmbyrro 5 years ago SQS vs "Postgres Queue", I think mainly:- Closed/lock-in vs. Open/lock-free- Rigid data access pattern vs. Very flexible SQL access-Managed by AWS vs. Managed by you/your team (although you could use one of those managed Postgres services to reduce ops burden)- Integrates well with other AWS services (e.g. Lambda, SNS, DynamoDB, etc) vs. No integrations with AWS ecossystem out of the box
rmbyrro 5 years ago SQS vs "Postgres Queue", I think mainly:- Closed/lock-in vs. Open/lock-free- Rigid data access pattern vs. Very flexible SQL access-Managed by AWS vs. Managed by you/your team (although you could use one of those managed Postgres services to reduce ops burden)- Integrates well with other AWS services (e.g. Lambda, SNS, DynamoDB, etc) vs. No integrations with AWS ecossystem out of the box
SQS vs "Postgres Queue", I think mainly:
- Closed/lock-in vs. Open/lock-free
- Rigid data access pattern vs. Very flexible SQL access
-Managed by AWS vs. Managed by you/your team (although you could use one of those managed Postgres services to reduce ops burden)
- Integrates well with other AWS services (e.g. Lambda, SNS, DynamoDB, etc) vs. No integrations with AWS ecossystem out of the box