#8 in Information theory books
Use arrows to jump to the previous/next product
Reddit mentions of Seven Databases in Seven Weeks: A Guide to Modern Databases and the NoSQL Movement
Sentiment score: 5
Reddit mentions: 8
We found 8 Reddit mentions of Seven Databases in Seven Weeks: A Guide to Modern Databases and the NoSQL Movement. Here are the top ones.
Buying options
View on Amazon.comor
Pragmatic Bookshelf
Specs:
Height | 9.25 Inches |
Length | 7.5 Inches |
Number of items | 1 |
Weight | 1.4 Pounds |
Width | 0.9 Inches |
Some great suggestions here around complimentary languages. Let me chime in on the tools. Depending on where you want your career to go deploying Ruby without Heroku wouldn't hurt at all.
I've made no assumption on what you already know so please don't feel like you need to know all of this but as Rubyist these are things I look for in candidate's that I hire :).
PS: I've not included Databases in all of this which I think is obvious to say is important when fleshing out a CV.
PPS: Two books I would recommend highly (can easily be read on holiday in the sun)
Both of these books are fairly light hearted, give you a grounded understanding of the core differences in languages and databases, assume your a programmer already and IMO are very interesting reads for someone that is keen to look at languages from different angles. Prolog == mind blown
Good Luck
dont really think you've been learning in the right places. you're getting a bunch of things mixed up.
first node is backend, just like rails and php etc. javascript can be used both in front and backend. which is unique.
You have to break it down to one question: what do you need it for? do you need a single page application (backbone, angular etc)?
do you have a backend? do you need a backend? (yes you do)
do you just need fast rendering and not a single page att all? (node.js with hapi or express).
do you need a document database (mongo, couch) or a graph (neo4j, level) or a relational (mysql, postgres), or maybe an in memory (redis, level)? use the one thats best for the need.
pick the tools to do the job not the other way around.
learn about the MEAN stack, read seven databases in seven weeks.
DDaRT followed by Seven Databases in Seven Weeks was very a useful refresher for me.
You don't, just try them on your own computer or even spend some money with AWS could do.
I recommend going through this: http://www.amazon.com/Seven-Databases-Weeks-Modern-Movement/dp/1934356921
Here's the book, I'm considering the buy: http://www.amazon.co.uk/Seven-Databases-Weeks-Modern-Movement/dp/1934356921
Relational databases operate the same way under the hood. There are significant differences between how postgresql and sql server work, but in the end, once you know one relational database, it will translate pretty well to others.
If you really want a tour on different databases, try this:
http://www.amazon.com/Seven-Databases-Weeks-Modern-Movement/dp/1934356921
It showcases 7 different approaches to databases.
> MSCA: SQL Server
Is a good choice. At the same time I see such programs and certificates as credentials for those who already have some experience.
If you
> have a good working knowledge of relational databases in general and know the general dialect of SQL pretty well already
it might be the right choice. It is not perfect but quite good.
> I've done a bunch of practice on sqlzoo.net and gone through a few database/SQL courses on Lynda.com
Take a look at https://lagunita.stanford.edu/courses/Home/Databases/Engineering/about and https://academy.vertabelo.com/blog/18-best-online-resources-for-learning-sql-and-database-concepts/ also.
A bit more:
Books from
https://en.wikipedia.org/wiki/Christopher_J._Date
https://www.amazon.com/Seven-Databases-Weeks-Modern-Movement/dp/1934356921/
https://www.amazon.com/Database-Systems-Complete-Book-2nd/dp/0131873253
Sometimes that's the best way to learn. When I'm unfamiliar with something I do some research try to get an idea of what is commonly used and when to pick what. I try to pick the simplest thing possible. Sometimes it's a guess and leads down the wrong path, but you learn and adjust.
For persistence I'd recommend starting with PostgreSQL or MariaDB/MySQL unless your application really needs something else.
Also read Seven Databases in Seven Weeks.