5 ms·

Well, if you really need the autoscale feature to handle sudden and ludicrous spikes of traffic, you will most likely also use a database that autoscales too. i

by pgz 7y ago

Well, if you really need the autoscale feature to handle sudden and ludicrous spikes of traffic, you will most likely also use a database that autoscales too. i.e. DynamoDB. For most applications, it's really not needed though.

FpUser 7y ago
"DynamoDB uses synchronous replication across multiple data centers for high durability and availability" This does not seem scalable for OLTP type load on some busy store. Again I think you'll be way better of money wise hosting your own database on real hardware either on prem or colocated
- jrrv 7y ago
  DynamoDB is used by Amazon.com. "Across the 48 hours of Prime Day, these sources made 7.11 trillion calls to the DynamoDB API, peaking at 45.4 million requests per second." [1] [1] https://aws.amazon.com/blogs/aws/amazon-prime-day-2019-powered-by-aws/ https://aws.amazon.com/blogs/aws/amazon-prime-day-2019-power...
  - FpUser 7y ago
    You're forgetting specifics here and the amount of hardware resources thrown into it. I've already told that I am not discussing here FB/Google/Amazon scale stuff. It is their problem and not shared by more regular deployments
  - majewsky 7y ago
    TIL: A day has 48 hours at Amazon.
    - plumeria 7y ago
      The same day across multiple time zones could take 48 hours
      - Archit3ch 7y ago
        Of course Amazon would call that an Elastic Sundial.
lovetocode 7y ago
But like they said, it comes with a ton of caveats. DynamoDB is one of the most confusing technologies I have ever used.
- pcnix 7y ago
  Absolutely agree, I tried it out for a short personal project and was disappointed with the bad documentation and even worse libraries that I found. I'm assuming large companies have their own internal libraries/ORMs for this, and that's how it is intended to be used. In terms of the actual technology itself, it's very interestingly built, and as the poster above me mentioned, with a ton of caveats to the promises it makes.
- Aeolun 7y ago
  It’s because it is just really expensive (both in time and money) to do basic things like a table scan.
  - Dunedan 7y ago
    That's actually one of the caveats that comes with unlimited scalability: You must design your application to not require full table scans.
- eknkc 7y ago
  It is one of very few technologies that I need to get a pen and paper and some quiet time to decide on a table schema. Most of the time I need to redo it after coming up with new query requirements. I hate and love it at the same time.
LoSboccacc 7y ago
is there any transnational storage solution that actually handles well a traffic spike? my understanding is that most storage solution scales well when planned, but scaling during a spike only causes more stress onto the current replicas/partitions for all the time needed to boot and shift data toward new replica/partitions, and the new instances don't contribute in moving the load until the process is complete. so they work if you can predict a spike, but they can't handle a sudden spike, especially if the data to replicate/partition is sizeable.

by pgz 7y ago

FpUser 7y ago

"DynamoDB uses synchronous replication across multiple data centers for high durability and availability" This does not seem scalable for OLTP type load on some busy store. Again I think you'll be way better of money wise hosting your own database on real hardware either on prem or colocated

jrrv 7y ago
DynamoDB is used by Amazon.com. "Across the 48 hours of Prime Day, these sources made 7.11 trillion calls to the DynamoDB API, peaking at 45.4 million requests per second." [1] [1] https://aws.amazon.com/blogs/aws/amazon-prime-day-2019-powered-by-aws/ https://aws.amazon.com/blogs/aws/amazon-prime-day-2019-power...
- FpUser 7y ago
  You're forgetting specifics here and the amount of hardware resources thrown into it. I've already told that I am not discussing here FB/Google/Amazon scale stuff. It is their problem and not shared by more regular deployments
- majewsky 7y ago
  TIL: A day has 48 hours at Amazon.
  - plumeria 7y ago
    The same day across multiple time zones could take 48 hours
    - Archit3ch 7y ago
      Of course Amazon would call that an Elastic Sundial.

lovetocode 7y ago

But like they said, it comes with a ton of caveats. DynamoDB is one of the most confusing technologies I have ever used.

pcnix 7y ago
Absolutely agree, I tried it out for a short personal project and was disappointed with the bad documentation and even worse libraries that I found. I'm assuming large companies have their own internal libraries/ORMs for this, and that's how it is intended to be used. In terms of the actual technology itself, it's very interestingly built, and as the poster above me mentioned, with a ton of caveats to the promises it makes.
Aeolun 7y ago
It’s because it is just really expensive (both in time and money) to do basic things like a table scan.
- Dunedan 7y ago
  That's actually one of the caveats that comes with unlimited scalability: You must design your application to not require full table scans.
eknkc 7y ago
It is one of very few technologies that I need to get a pen and paper and some quiet time to decide on a table schema. Most of the time I need to redo it after coming up with new query requirements. I hate and love it at the same time.

LoSboccacc 7y ago

is there any transnational storage solution that actually handles well a traffic spike? my understanding is that most storage solution scales well when planned, but scaling during a spike only causes more stress onto the current replicas/partitions for all the time needed to boot and shift data toward new replica/partitions, and the new instances don't contribute in moving the load until the process is complete. so they work if you can predict a spike, but they can't handle a sudden spike, especially if the data to replicate/partition is sizeable.