Seven Databases in Seven Weeks, Second Edition »

This is the only comprehensive guide to the world of NoSQL databases, with in-depth practical and conceptual introductions to seven different technologies: Redis, Neo4J, CouchDB, MongoDB, HBase, Postgres, and DynamoDB. This second edition includes a new chapter on DynamoDB and updated content for each chapter.

April PragPub »

• Dark Scrum: Hills to Die On
• The Impossible Every Day
• In Which I Get Hacked
• Clojure for Full Stack Development

Plus: On Tap, Swaine’s World, Technically Awake, New Manager’s Playbook, The PragPub Puzzle, Antonio on Books, From the Pragmatic Bookshelf, The BoB Page, and Shady Illuminations.

Recently Released:

• Craft GraphQL APIs in Elixir with Absinthe 
• Java by Comparison 
• Software Design X-Rays 
• Rediscovering JavaScript 

Data is getting bigger and more complex by the day, and so are your choices in handling it. Explore some of the most cutting-edge databases available—from a traditional relational database to newer NoSQL approaches—and make informed decisions about challenging data storage problems with Seven Databases in Seven Weeks, Second Edition: A Guide to Modern Databases and the NoSQL Movement, now in print and shipping from pragprog.com/book/pwrdata. Read on for a Q&A interview about the book, direct from the authors.

And since it's April, there's a new edition of PragPub magazine ready for reading. No fooling. Now available from theprosegarden.com. Read on for details.

/\ndy

Seven Databases in Seven Weeks, Second Edition: A Guide to Modern Databases and the NoSQL Movement

While relational databases such as MySQL remain as relevant as ever, the alternative, NoSQL paradigm has opened up new horizons in performance and scalability and changed the way we approach data-centric problems. This book presents the essential concepts behind each database alongside hands-on examples that make each technology come alive.

With each database, tackle a real-world problem that highlights the concepts and features that make it shine. Along the way, explore five database models—relational, key/value, columnar, document, and graph—from the perspective of challenges faced by real applications. Learn how MongoDB and CouchDB are strikingly different, make your applications faster with Redis and more connected with Neo4J, build a cluster of HBase servers using cloud services such as Amazon's Elastic MapReduce, and more. This new edition brings a brand new chapter on DynamoDB, updated code samples and exercises, and a more up-to-date account of each database's feature set.

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.

Now in print and shipping from pragprog.com/book/pwrdata.

Q&A With author Luc Perkins

Q. Why did you choose to work on the second edition of Seven Databases in Seven Weeks?

A: Well, I began becoming intimately acquainted with the NoSQL space about five years ago, when I took on the role of technical writer at Basho Technologies, the company behind NoSQL database Riak. From the very beginning I found the space endlessly interesting, so full of promise and inspiring technology yet also very tricky to navigate.

Relational databases are quite interesting to me as well, but they tend to be very structurally similar. NoSQL databases on the other hand, tend to be much more individualistic, you could say. Each has its own special strengths and weakness and quirks and presents you with a set of trade-offs you’ve probably never encountered in another database. So the book was an opportunity to take my more localized knowledge of the space and really stretch my knowledge and my thinking outward.

Q: What was the hardest part about working on the book?

A: In general, I’d say making the book up to date. Unsurprisingly, a ton has changed since the original edition. The NoSQL space is notoriously fast moving and it’s hard enough to keep up with one database, let alone seven. That means that I had to check every single code snippet and CLI command and claim and diagram in the book to make sure that it still worked, presented accurate information, etc. Then I had to make sure that newer features are mentioned or showcased when necessary. For a book that’s really seven books in one, this was quite a task, though an extremely rewarding one.

Q: What are some of the main differences between the first and second edition?

A: First, and most importantly, everything in the book works now. We’re all used to bit rot in code but it happens in books, too. Database systems change a lot over time. Many of the CLI commands and code snippets from the first edition eventually started throwing cryptic errors or flat-out not working at all.

But there are some other, more specific changes. The chapter on Riak was removed and replaced with a chapter on Amazon’s DynamoDB. Riak is a fascinating database but its future is very uncertain. DynamoDB is also a fascinating database but it feels like a living, breathing project. Furthermore, the querying language for Neo4j was updated to Cypher (instead of the original and now largely defunct Gremlin).

Q: What’s your favorite database in the book?

A: Oh gosh, that’s very tricky, because I have a special fondness and a place in my heart reserved for each of them. But if I had to pick I’d say Redis. It has a pretty small surface area for such a widely used system and a very well-defined domain of problems that it seeks to address. If I had to build a new application that used all seven databases in the book, the Redis portion of the application would be the one I’d be most eager to work on.

Q: Do you have any general advice for readers? Databases are complex and it may not be readily apparent how even an extremely technically savvy reader should proceed.

A: I’d say take it nice and slow. The content is spread across “days” for a reason. You don’t have to follow the schema we present, of course, but this is not single-sitting material. Take a minute to really absorb the diagrams and technical definitions. Try to understand each database’s “worldview,” so to speak, and use that as a thinking cap for each chapter’s material. Try to imagine times when each database would be indispensable. And if you and a database just aren’t getting along, skip to the next one and come back later. You may come back with fresh insight and a new slate of questions.

Now in print and shipping from pragprog.com/book/pwrdata.

April PragPub Magazine

You’ve been hacked! It can happen at any time. When it happened to Swift programming guru Erica Sadun, she documented every bit of it: all the steps she took, the advice, the results — over the course of four increasingly irritating days. This month in PragPub we have the blow-by blow account of how one developer dealt with an invasion. It’s a cautionary tale.

Also in the newly-released April PragPub we are excited to launch a new monthly column: “Technically Awake” by Russ Olsen. Russ just finished writing Getting Clojure, which is about how to really think in Clojure, not just how to write Clojure programs. He will be bringing that kind of broader perspective to various topics technical in the coming months. His inaugural column deals with programming languages, why we like some and hate others, and why your first impression of a language is likely to be wrong.

In our Soapbox feature, where we invite someone to sound off on an issue of importance, software legend Ron Jeffries issues the opposite of a call to arms, asking, “Is this really the hill you want to die on?” It’s the beginning of a conversation he’ll continue on his blog about Agile development, Scrum, and whether some of the battles over software process are worth having.

Tim Ottinger reflects on all the things he — and probably you — used to think were impossible, and that are now a part of programming life. And Paul Butcher continues his series on Clojure for full-stack development. This month: the Web.

In our tech books section, Antonio Cangiano surveys all the new books and highlights one on learning the Haskell language. And we’re featuring an excerpt from Java by Comparison by Simon Harrer, Jörg Lenhard, and Linus Dietz.

Our other regular columnists are on hand as well. Marcus Blankenship writes on team leadership and the challenges of moving from programmer to manager. It’s a path he followed, and he knows it well. This month he offers his hard-won advice on avoiding learned helplessness. And John Shade and your editor both looked at the Facebook imbroglio and drew different lessons from it.

We hope you enjoy the April PragPub!

Now available from theprosegarden.com.

Upcoming Author Appearances

You Could Be a Published Author

Is there a tech topic you are deeply passionate about and want to share with the rest of us? You could become a published Pragmatic Bookshelf author! Take a look at our pragprog.com/write-for-us page for details, including our 50% royalty (yes, for real!) and world-class development editors.

Don't Get Left Out

Are your friends jealous that you get these spiffy email newsletters and they don't? Clue them in that all they need to do is create an account on pragprog.com (email address and password is all it takes) and select the checkbox to receive newsletters.

Are you following us on Twitter and/or Facebook? Here's where you can find us and keep up with the latest news and commentary, and occasional discounts:

Tell your friends! Tweet this

Follow us on Twitter: @pragprog, @pragpub, Andy Hunt @PragmaticAndy.

Andy Hunt
Publisher, Pragmatic Bookshelf

Books • eBooks • PragPub Magazine • Audiobooks and Screencasts
PragProg.com

Manage your subscription using your account, or permanently unsubscribe here.
Sent by the Pragmatic Programmers, LLC. • 9650 Strickland Rd Ste 103-255• Raleigh NC 27615