May Issue of NFJS, the Magazine published.
Here’s what is in this month’s NFJS, the Magazine
Tim Berglund – NoSQL
There’s a lot of buzz going around about the death of the relational database, as success story after success story mounts in the growing NoSQL category. NoSQL databases are counter-cultural, insurgent, and forever associated with massive data sets and web-scale transactional volumes. It’s hard not to want to jump on board, but the wise engineer knows to proceed with caution when a new technology is being hyped.
To know when to adopt a NoSQL solution, we must understand the engineering challenges to which the category is responding. We’ll have to remind ourselves what ACID transactions are guaranteeing, why two-phase commits are performance-limiting, what the CAP theorem means, and what exactly makes a relational database the thing that it is. This will prepare us to explore the landscape of NoSQL products, seeing how they differ in data model, scaling paradigm, transactional guarantees, and more. It’s an enormous field that’s only growing and getting more exciting by the week. To see through the excitement and make informed judgments, developers and architects have some learning to do. On the other side of that education is a richer set of options for storing and retrieving data.
Bob Gobeille – FOSSology
Free and Open Source Software (FOSS) is the cornerstone for software sharing. It allows us to build on the code shoulders of others and redistribute that code as a licensed work. Licensed? You don’t often hear the terms “free”, “open”, and “licensed” in the same sentence, but this is exactly what FOSS (aka FLOSS, aka Freedom) software is. The FOSSology project is used to find those licenses, copyrights and other information.
Peter Bell – Wrangling Your Requirements
What is the state of the art in requirements gathering these days? What is “just enough” design upfront? How do you minimize rework as new scenarios break your domain model? And how can you use “deliberate discovery” to reduce risk more quickly on projects?
Mark Richards – Understanding the Differences Between AMQP and JMS
As the Advanced Message Queuing Protocol (AMQP) specification matures and robust AMQP implementations such as RabbitMQ become more popular, the question comes to mind whether you should jump on the bandwagon and use AMQP instead of Java Message Service (JMS) as your messaging standard. Understanding the differences between AMQP and JMS is a great way of better understanding what AMQP is and whether you should use it. In this article I will describe AMQP through a comparison of the AMQP specification and the ever-popular JMS specification.
I’m very proud of the work we do on this new magazine. The staff and I have worked hard to produce a top-notch magazine that is unique in the realm of software development magazines. The magazine costs $50 per year, which includes 10 issues. Each issue has at least four articles. You can download in a print-quality PDF and two mobile formats: EPUB (for the Nook and iPad) and MOBI (for the Kindle). The articles are professionally edited and are written by top experts in their field, so the content is worth well more than the $50 you pay.
The April issue just published this morning and you can subscribe here: http://bit.ly/fETp6d. As always, if you have questions just comment on this post and I’ll respond quickly.
