- Más nuevo
- Más votos
- Más comentarios
There isnt enough information in the post to guide and design your architecture. A Solutions Architect would need a deeper dive into your application and how it operates to help design and answer the questions. I can think of handful of questions.
AWS Has over 200 services and growing constantly and depending on your requirements would dictate the solution.
You may wish to engage with a SA either directly with AWS or a partner such as where I am based
I agree that more context is needed in regards of traffic patterns and more, but given the numbers you gave, you probably better off to start with Serverless components such as lambda functions, API gateways and learn from there.
From database perspective, depending on access patterns, you may look into either dynamo or RDS. At this stage Aurora feels a bit of overhead, though you haven’t mentioned anything about how global your app is.
If it is of course you may want to look into Cloudfront and s3 for hosting front ends.
Above components are fairly cheap for traffic you mention and can easily be managed via aws budgets, and cost explorer.
Contenido relevante
- OFICIAL DE AWSActualizada hace 10 meses
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 18 días