AWS re:Invent 2018: Building with AWS Databases: Match Your Workload to the Right Database (DAT301)
We have recently seen some convergence of different database technologies. Many customers are evaluating heterogeneous migrations as their database needs have evolved or changed. Evaluating the best database to use for a job isn't as clear as it was ten years ago. We'll discuss the ideal use cases for relational and nonrelational data services, including Amazon ElastiCache for Redis, Amazon DynamoDB, Amazon Aurora, Amazon Neptune, and Amazon Redshift. This session digs into how to evaluate a new workload for the best managed database option. Please join us for a speaker meet-and-greet following this session at the Speaker Lounge (ARIA East, Level 1, Willow Lounge). The meet-and-greet starts 15 minutes after the session and runs for half an hour.
![AWS re:Invent 2018: [REPEAT 1] Deep Dive and Best Practices for Amazon Redshift (ANT401-R1)](/img/d.gif)
Пікірлер: 16
Oh man if he joined any university and taught databases I would drop everything to take that course. What an amazing talk.
He needs to teach at the University. More useful than anything my professors taught me
@realTonyJiang
3 жыл бұрын
University can not pay as much as aws xD.
Never saw an overview session as great as this is.
I wish I could convey technical information this succinctly and quickly.
oh my God this is great overview....
Awesome, thanks
Best speaker
Excellent talk
Great talk and great overview. Just how many database types does one organization need!?!?! LOL :-)
will the slide deck be available?
@liln4444
5 жыл бұрын
Slides can be found here: www.slideshare.net/AmazonWebServices/building-with-aws-databases-match-your-workload-to-the-right-database-dat301-aws-reinvent-2018?qid=dc6a3e4f-bb3d-425a-a2cf-1f37784447e1&v=&b=&from_search=1
1:36 Larry Ellison keeps poking at them that they still use Oracle databases. Guess they are finally jumping ship.
Why doesn't dynamodb support simple aggregations like mongodb does? I understand that table joins would be very inefficient accross multiple shards. However, I would have thought that aggregations would be more efficient....
@alexnarayanstechandetc
4 жыл бұрын
I think he said it - DynamoDB is for queries that you know before hand. Aggregations kind of bleed into that ad hoc style of querying that requires something else
@nichenjie
4 жыл бұрын
@@alexnarayanstechandetc Not necessarily. If you know the access pattern of the aggregation, you can pre-aggregate in DynamoDB. That's the DynamoDB's way of doing aggregation.