Комментарии:
Amazing explanation, no bs. You got a new follower
ОтветитьWould you be kind enough to share the flowchart link?
ОтветитьGreat explanation. The things I was wondering for years, you solved in 6 mins ❤. Thanks a lot
ОтветитьIs it a bad idea to use Dynamo DB or Aurora Serverless for a prototype or a hobby project?
Dynamo DB's storage is free for the first 25 GB and $0.25 per GB-month thereafter. With Aurora Serverless, you only pay for the database capacity, storage, and I/O when it is active.
When your prototype app or hobby project is small, I think both services can be suitable because they are economical for small apps that don't have a lot of traffic. Am I missing something?
very good explanation
Ответитьdid you intentionally forgot Redshift ?
ОтветитьQuick Question, isnt RDS a managed service? Why does the arrow for unmanaged loops to RDS?
ОтветитьAwesome - Thanks for making!!
ОтветитьDude that video made everything in my head click you are a legend!
ОтветитьKeep it size and industry needs based:
- Mariah DB for transactional information and small business.
- AWS Redshift for large scale reliable variable SQL needs.
- Dynammo DB for choatic information using NoSQL (key value or document).
I highly appreciate the way you have explained it all, lots of love from India
ОтветитьYou saved lot of my time to read through the docs for each and find the difference 🙏 thank you!
ОтветитьThank you, really good guidance right there.
ОтветитьGreat explanation but I was surprised at the very end, where Elastic Cache is suggested as persistence layer. The cache doesn't guarantee data durability. The application will lose its data if the underlying infrastructure/hardware changes.
ОтветитьWhere do RedShift and AWS Timeseries fall into?
Ответитьuseful video
ОтветитьGreat summary, thanks!
ОтветитьThis video helped me land a new job during a system design interview!! Thank you!!!
ОтветитьGood explanation of RDS. But what about self hosted Postgres on EC2 instance ? Is it cost effective solution for small project or startup? Or it is not as reliable as RDS is?
ОтветитьIt's clear, thank you
ОтветитьCan you share the scheme?
ОтветитьIs there any way I can get access to this flowchart? Its very well done and would be a great resource to explain my backend choices to my non-technical partners.
Appreciate your help, and amazing video!:)
Can we integrate AWS Mongodb with onprem Oracle AVDF ?
ОтветитьMeanwhile Oracle 👋👋
ОтветитьBut ElasticCache is used for performance. It is a cache for databases. It can be used for an rds database to avoid the query go to the engine and also reduce latency. I think this is important to mention. At least it is useful for data that rarely is updated. If we have data that changes very frequently, then read replicas is the way to go.
ОтветитьAdd neptune too in relationals -)
ОтветитьWhy automatically use elasticache if you don’t need relations or transactions? Isn’t it more expensive than RDS or dynamoDb?
ОтветитьDynamo db does not support transaction. Notnsure why you mentioned like that. It supports maximum upto 25 writes in a transaction ..
ОтветитьWell explained in a layman way
Ответитьwhat about geo queries ????
which db is best for geo spatial ???
Current Database services in AWS simplified 😉. Thanks for quick summary!
Ответитьgreat videos
ОтветитьVery well structured summary!
Ответить236/5000
Based on the fact that dynamodb is a key value databse, it works well for particular cases but for more advanced query scenarios such as paginated queries, ordering by several fields or aggregations, I would choose documentdb
Summary: choose Dynamodb ;p
ОтветитьWhat about DynamoDB that comes with AWS Amplify for prototyping?
ОтветитьAwesome vid on Traversy media ! Watching you now.
Ответитьvery helpful, thanks!
ОтветитьThank you!
ОтветитьReally useful! Thanks
Ответить