Seven Databases in Seven Weeks, 2nd Edition

The book is an interesting heads-up on databases being used on different fields throughout the world.

You may or may not have heard about polyglot persistence. The fact is that more and more, software projects are making use of different technologies. And when it comes to the database world, the number of options is immense: it can be relational, document or columnar databases, key-value stores, graph databases, not to mention other cloud infrastructure options like service buses, blobs, storage accounts and queues.

What to use? Where? And how does that affects developers?

Choosing a database is perhaps one of the most important architectural decisions a developer can make. In that regard, I'd like to recommend a very interesting book that addresses some of that discussion: Seven Databases in Seven Weeks, 2nd Edition.

Why you should read this book

Because the book:

• provides practical and conceptual introductions to Redis, Neo4J, CouchDB, MongoDB, HBase, PostgreSQL, and DynamoDB
• introduces you to different technologies encouraging you to run your own experiences
• revises important topics like the CAP Theorem
• will give you an overview of what’s out there so you can choose the best tool for the job
• explore some cutting-edge databases available - from a traditional relational database to newer NoSQL approaches
• and make informed decisions about challenging data storage problems
• tackle a real-world problem that highlights the concepts and features that make it shine

Conclusion

Whether you're a programmer building the next big thing, a data scientist seeking solutions to thorny problems, or a technology enthusiast venturing into new territory, you will find something to inspire you in this book.

Reference

• Seven Databases in Seven Weeks, 2nd Edition

See Also

• My journey to 1 million articles read
• Skill Up: A Software Developer's Guide to Life and Career
• Hello, Startup - A book for developers building their startups
• Non-technical skills for software developers
• Interview questions for QA analysts