By Editor in Chief Andrew Binstock
Welcome to the May/June issue of Java Magazine in which we look at how big data is done today. An unusual aspect of the platforms that handle big data is that they almost all run on Java — a testimony to its suitability for enterprise-scale needs.
However, today many of the primary tools don’t require enterprise size to be useful. Apache Spark, for example, can work effectively on small, human-size databases. We show how this is done with one developer’s project of querying a database of first names to find one for his unborn child. But even if you run Spark in enterprise apps, you’ll find that it is much easier to use than earlier tools that required extensive setup and fiddling with systems. Our lead article on Apache 101 shows just how simple it can be to work with big data and produce useful results.
We also look at handling large datasets the traditional ways in two articles: with high-volume JDBC and through enormous in-memory data structures. The latter article shows a clever way of storing tens of gigabytes in memory but off the heap.
For those readers who do unit testing on their code (almost everyone, I trust), we preview the new features coming up in JUnit 5.
The rest of the issue shows off Ceylon , a recently released JVM language from Red Hat; how to set up Java cloud apps; and, for beginners, how generics work in Java — all topped off by our famous language quiz, our no-holds-barred book review, and my editorial. Enjoy!
Note: In our quest to support more devices, we have moved away from the former Java Magazine app. Currently, the magazine is available on the web and in PDF. To get the PDF, access the web page from a laptop or desktop and use the download icon on the right side of the page.
We will shortly complete migration of our back issues. Thank you for your patience while this process completes. If you’re desperate for a specific back issue, drop me a note. We’ll find a way to get it to you.
Like what you see? Wish we’d cover something else? Please send along your feedback, which I read attentively. You can always reach me at firstname.lastname@example.org.