TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Why do "Databases as a Service" often die?

3 pointsby captaincrunchalmost 13 years ago
I've recently (in the last 1-2 years) seen a lot of databases as services die, or disappear. Is there a reason for this, or just another opportunity to get it right?<p>By DB-AA-S I don't mean throwing up a MYSQL server and charging service fee's, I mean actual sites where you can create a database and use it through the companies front end.

4 comments

riffraffalmost 13 years ago
I guess if you don't want to manage a db by yourself, it's usually still more convenient to use one db-aa-s in the cloud platform you are using for the rest, e.g., using postgres on heroku, RDS on AWS, mysql on appengine etc.<p>You win on integration, latency, management, billing etc.
ddorian43almost 13 years ago
I think latency is one reason.
hboonalmost 13 years ago
Are you referring to something more like DabbleDB rather than MongoHQ?
maggioantalmost 13 years ago
What are some examples that you've seen die?