- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hi,
You don't provide any traffic estimates,: I guess it's because you cannot estimate yet. It's key to determine the cost estimates that you ask for.
So, I would recommend to initially go with a serverless architecture for this application: use the standard serverless architecture API Gateway +SQS + Lambda functions + DynamoDB.
Multiple advantages:
- those services manage scaling, resiliency / HA for you: you can focus exclusively on your app code
- they are mostly in pay-as-you-go mode: no use -> no cost. See the pricing pages of those AWS services to see their cost
You have all the details of this pattern here: https://serverlessland.com/patterns/apigw-sqs-lambda-ddb-cdk
When you get to a steady flow of requests with high-volume, you will have to check if it becomes cost-efficient to manage your own lower layers with containers, EC2 instances, etc.)
The pay-as-you-go mode via serverless is usually the best way to start when you can't estimate you workloads: with it, you avoid any initial over/underprovisionning for your architecture.
BTW, you have to add the cost the APIs that you mention: Google, Yandex, DuckDuckGo, etc. Please, go their web sites to find their costs.
Best,
Didier
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 10 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren