Subscriptions include a calendar year of issues (March - December) regardless of when you subscribe. When ordering after March, your subscription includes access to the previous issues of the current year. Each month, you will receive an email with a link to download the magazine PDF and associated code samples.
In object modeling, mixins provide a way to create abstractions that define a common functionality that can be mixed into different abstractions. As Java programmers we did not quite have the ability to make use of this powerful concept, especially because Java does not provide multiple inheritance. In languages that do provide multiple inheritance, like C++, this is quite difficult to use in practice due to problems with method collision. Scala elegantly supports compile time mixins through traits. In this first part of the series, we'll learn about traits in Scala and how to use them. In the second part, we'll learn how to apply multiple traits both at class and instance levels.
In the first installment of this series, we discussed the need for integration, and some of the potential pitfalls, especially when attempting to roll your own integration system. We then proceeded to discuss some of the patterns in Gregor Hohpe's and Bobby Woolf's aptly named "Enterprise Integration Patterns" and their corresponding implementations in Spring Integration. We discussed the core patterns that make up the founding blocks of Spring Integration - "Message Channel", "Message" and "Message Endpoint". In this article we will explore a few more patterns that will allow you to route, filter and manipulate messages as well as talk to external systems. We will learn how to do this while leveraging Spring's declarative model that lets you focus on your domain, and let Spring Integration handle the specifics of messaging.
In spite of all of the great things Spring brings to Java development, one criticism it has received a lot of over the years is its heavy use of XML for configuration. It's true that Spring configuration has traditionally required XML. Lots of XML. It seems that XML has fallen out of favor with many developers. And for those who are card-carrying members of the He-Man XML Haters Club, it's hard to see the benefits of Spring through the haze of XML. If you're among the XML haters, then this article is for you. Each version of Spring has taken steps to lighten the XML burden and I'm going to show you a few tricks from the latest versions of Spring that make it possible to develop a Spring application with minimal or even no XML whatsoever. To illustrate these techniques, I've written a simple Guestbook application using common Spring XML configuration. Throughout this article, we'll swap XML configuration for Java configuration, until there is no more XML left in the project. If you want to follow along, you can download the before and after projects from this magazine's download URL.
In the past few years we have seen a veritable explosion in various ways to store and retrieve data. The so-called NoSql databases have been leading the charge and creating all these new persistence choices. These alternatives have, in large part, become more popular due to the rise of Big Data led by companies such as Google, Amazon, Twitter, and Facebook as they have amassed vast amounts of data that must be stored, queried, and analyzed. But more and more companies are collecting massive amounts of data and they need to be able to effectively use all that data to fuel their business. For example social networks all need to be able to analyze large social graphs of people and make recommendations for who to link to next, while almost every large website out there now has a recommendation engine that tries to suggest ever more things you might want to purchase. As these businesses collect more data, they need a way to be able to easily scale-up without needing to re-write entire systems.
First, let me take this opportunity to thank you for your continued support of No Fluff Just Stuff. The emphasis of this magazine is all about quality content just like our software conference series. For those of you not familiar with the No Fluff Just Stuff Symposium series let me share a little history. I started NFJS in 2002 to offer high quality technical content in a conference format and offered in over 30 cities throughout the U.S. and Canada. The credo of NFJS is simply: Local Venue, World Class Conference. NFJS offers individuals the opportunity to attend an outstanding conference right in your own backyard whether you live in Milwaukee, or Denver, just to name a few. The NFJS conference series is focused on great technical content(stuff) and little to no fluff - advertising, vendors, etc...
NFJS, the Magazine is an eclectic mix of articles centered on software development and all that entails. Whether you are a developer, architect or manager, you should find all of the articles in NFJS interesting and enlightening. All of the article authors are speakers on the No Fluff Just Stuff Tour and published thereby insuring a great read. We want this magazine to be time efficient for the reader. To me, NFJS the Magazine is all about outstanding content that is easily consumable. The other great thing about the format of this magazine is that you can easily read articles out of sequence over the months and refer back to something anytime. Unlike traditional magazines, NFJS has a much longer shelf life and makes a great reference source.
We are very excited to bring you NFJS, the Magazine ten times a year. I hope you find NFJS, the Magazine to be a great informational resource. Drop me an email and let me know your thoughts.