4 ms·
Migrating Graphite from SQLite to PostgreSQL
- andrewvc 13y agoAs a fan of both databases, I just have to say, you don't always need all the constraints. Also, at the very least, graphite should have been able to enforce them at the app level in addition to at the DB level.
- obfuscurity_ 13y agoI completely agree. I was rather disappointed to find that it didn't.
- yeukhon 13y agoIs it by default it ships with SQLite or just Doc?
- obfuscurity_ 13y agoI'm not sure what you're asking here. Graphite uses SQLite by default. What is "Doc"?
- yeukhon 13y agoSo it ships with SQLite. Doc as in documentation - telling users to get started let's try SQLite.
- obfuscurity_ 13y agoIt is configured to use SQLite by default, but it doesn't ship /embed/vendorize it. You're required to install the sqlite bindings yourself.
- yeukhon 13y agoThere is no reason why one would use SQLite in real production. Even during testing and dev, I am a firm believer of testing against real database that you are going to use in production. The problem "it's hard to setup a new database" is a result of not willing to invest in re-provisionable system.
- untog 13y agoThere is no reason why one would use SQLite in real production. Yes there is. Small storage for a local app? SQLite is ideal.
- obfuscurity_ 13y agoExcept that while Graphite is a "real web application", it's generally internal-facing only. As such, I never looked at it as needing a true "production-ready" RDBMS with real concurrency. And to be honest, we got by just fine with it in production at Heroku and GitHub, at heavy volume, running in a single server on SQLite. It never bit us, and all things considered, was a reasonable choice. That said, knowing what I know now, I would've never done that. ;-)
- yeukhon 13y agoI disagree because it is internal facing lol. If the software is capable of running on a true production-ready DBMS, there is no point why it can't be done already. If SQLite is cheap to use because it's a single file, well, a sudo apt-get install PostgreSQL and then a few commands to set up the database and user password won't take you longer than 10 minutes. That's what I am arguing. There is no reason why we would use SQLite for heavy loading application such as logging. And I think we can now agree that's indeed true and I think we should promote people to use production-ready DBMS even during dev and testing, because those are the one you are going to use in production :)
- alixaxel 13y agoMeh, SQLite is awesome. So is PostgreSQL, but this rant is uncalled for.
- obfuscurity_ 13y agoHow is the article a rant? Or are you referring to the one of the comments above?