Speaking of right tool for the right job
Instead of a list of 300, lets pivot and first think about common categories
Then consider what the purpose of a tool is within a category
And common use cases we hear from customers
For example
If part of your application, such as orders, required strict schema, data accuracy, and consistency, relational is a great choice
If you were building a massive online game, with millions of players coming and going, requiring high through put reads and writes, with endless scale, key-value is a great choice
If part of your application needed to make a recommendation, based on highly connected data, graph is a great choice
Lets take a closer look
Our offer a family of databases so developers never have to trade off functionality, performance, or scale
There is no compression algorithm for experience
We have a deeper understanding of how to run highly available databases at scale
Our roadmap is 90% driven by customers, new model, we will invest
A common question I get is what is coming in the future
While I don’t know exactly what the future looks like, its important that we invest in things that last
For example, I don’t think a customer will ask us to make a database
Scale less, perform slower, and have outages.
This is why we are always investing in scale, performance, and operations
We aspire for our operations to be indistinguishable from perfect, so you can spend your time on building
AWS IoT Things Graph
AWS IoT SiteWise
AWS IoT Events
AWS Elemental MediaConnect
Amazon EC2 P3dn instances
On-Demand Hibernated
Amazon Managed Blockchain
AWS RoboMaker
EC2 A1 Instance
C5n
CloudWatch Logs Insights
Amazon Kinesis Data Analytics for Java applications
Firecracker
AWS Lake Formation
AWS App Mesh
AWS Toolkit for Popular IDEs
AWS Step Functions service integrations
Amazon Managed Streaming for Kafka (Amazon MSK)
AWS CloudMap
APIGW web socket support
Lambda Ruby support
ALB lambda as a target