3 ms·
So it's slow and needs memcached or something? That's dissapointing. What usecases would you use it for? Never going down just doesn't seem that big of a deal
by petervandijck 16y ago
So it's slow and needs memcached or something? That's dissapointing. What usecases would you use it for?
Never going down just doesn't seem that big of a deal for me, their aws mysql service also "never" goes down, so I might as well use that and gain all the sql advantages, right?
- alexbosworth 16y agoNever going down in a database doesn't just mean that it doesn't have downtime, it also means that as a whole system it's immune to bad queries. Bad queries can destroy you in MySQL, if you are doing dynamically created queries that hit un-optimized areas, it can bring down all the other queries too. I'd typically use Memcache with MySQL too, so there isn't any real difference in that case. One use case I like SimpleDb for is for small scripts that need a very simple data store.
- jrockway 16y agoIt depends on what you think "slow" means. It's the same speed when you're running one concurrent query as it is when you're running a hundred million concurrent queries. That's what we call "scaling".