Let that sink in
Re:AWS services explained in one line each
by scarface74 on Tuesday May 26, 2020 @08:31PM
(#23318151)
Especially since “EC2” is not just a VM. There are dozen services at least that come under EC2.
Also if you start trying to use DynamoDB like you would Mongo, you’re going to be really upset. The use cases, design considerations and performance considerations of DynamoDB compared to Mongo is night and day.
Actually DynamoDB unlike MongoDB is truly a distributed store, and it actually is closer to Cassandra, Riak (RIP), Aerospike maybe some others.
Re:AWS services explained in one line each
by scarface74 on Wednesday May 27, 2020 @12:50PM
(#23326078)
Yes. But DynamoDB basically requires you to know your access patterns up front and isn’t that flexible when it comes to querying - yes I’ve watched all of the reInvent videos about how to properly model your DDB tables.
That being said, if I needed the flexibility and wanted to stay in the AWS ecosystem, I would use DocumentDB with Mongo compatibility. It uses the same storage engine as Aurora, it’s much more flexible and it doesn’t have any of the well known downsides of Mongo.
Re:AWS services explained in one line each
by socceroos on Tuesday May 26, 2020 @09:46PM
(#23318570)
OK substitute VM with OpenStack then.
Re:AWS services explained in one line each
by scarface74 on Tuesday May 26, 2020 @09:53PM
(#23318602)
I’m really not trying to sound like the “do people still watch TV” guy, but I thought OpenStack fell off the hype curve years ago. Do people still use it.
Re:AWS services explained in one line each
by viraptor on Wednesday May 27, 2020 @06:59AM
(#23321580)
> fell off the hype curve years ago. Do people still use it.
Hype and usage are very different. It's not like a lot of people really used it during the hype either. There are a few places which actually need something like that and can't use k8s.
A list of actual competing software/products/services would be pretty useful.