3 ms·
Postgres. Get a book by Joe Celko (SQL for Smarties, for instance) and really learn relational databases. They're not going anywhere. Any job you take, you can
by fusiongyro 13y ago
Postgres. Get a book by Joe Celko (SQL for Smarties, for instance) and really learn relational databases. They're not going anywhere. Any job you take, you can bet there's a relational database back there somewhere. Postgres is free and will surprise you less than any other. If you're very good at SQL, you will write a lot less code in the middle tier to post-process data on the way out. You won't be hindered by a lack of OO understanding--in fact, it may benefit you since you won't face the O/R impedance mismatch. Once you're good at SQL you'll be a lot less worried about other things in the backend, and the declarative nature will help you reason better. It will pay dividends no matter what step you take after that.
- nailer 13y ago> Any job you take, you can bet there's a relational database back there somewhere. My experience is a little different: - Current job: Mongo - Previous job: Mongo with a custom REST wrapper / ElasticSearch - Previous job: AppEngine Data Store - Previous Job before that: SQL only ever accessed with Django ORM Not that one shouldn't learn SQL if needed, I just don't think it's a mandatory part of modern web apps like it once was.
- fusiongyro 13y agoI don't think it's mandatory either, but I think this person would benefit along many axes, not just work-related.
- GeneralMaximus 13y agoDon't forget that PostgreSQL has a comprehensive online manual that includes, among other things, a complete SQL reference: http://www.postgresql.org/docs/9.3/static/index.html http://www.postgresql.org/docs/9.3/static/index.html
- methurston 13y agoCame to post the same thing. Don't get too hung up on the actual database, just learn SQL and relational databases. It's something you will use over and over again, even if it's just to peek into the back end to see what your framework, ORM, etc actually did with the data.
- buckbova 13y agoI'm going to agree, as a Sr Database Architect, that once you have these skills and some experience under your belt you will never want for jobs. There is one huge caveat. Sometimes it is so boring that I often daydream of attempting trephination on myself.
- ianstallings 13y agoBut man do you guys make a killing. Holy astronomical salaries batman!
- vladsanchez 13y agoPlease share your figures, I am a PGDBA needing to "benchmark" my salary. =P
- AznHisoka 13y agoBut the hard stuff is actually scaling, optimizing and administrating databases, not the SQL stuff right? I mean, sure optimizing SQL queries is important, but I find stuff like sharding, making sure the CPU load doesn't get too high, partitioning, archiving, and scheduling autovaccuum jobs the hardest part about databases. Joins and group bys? Piece of cake in comparison.
- adamnemecek 13y agoThat still falls under the expertise of a database architect.