Oh em gee! Traditional performance management is broken, who broke it?!? Well in all honesty, it has always been broken because, most companies don’t start thinking about performance monitoring until the application is in production. In fact, we’ve found that over 75% of the application performance issues make it to production where customers experience them. Just imagine if we did this with our QA issues.
Some time ago, I started working on an AutoValue extension for reading and writing Java properties files. Here’s a rough plan of what I thought it should do:
- have a simple and reliable implementation;
- be similar or reuse the existing AutoValue extensions as much as possible;
- easily replace the custom code in our projects for reading/writing the .properties files;
- support obfuscated builds out of the box.
I didn’t get it to the stage where the code is ready to become public yet, although, we’re open to that idea, I learned quite a bit about AutoValue, how its extensions work and in this post, I want to share that knowledge with you.
In this post, we’ll look at what AutoValue is and how it can help you keep your code cleaner and less verbose, at AutoValue extension mechanism and AutoValue Moshi extension works.
With the Java 9 version on the brink of release, we thought we’d ask 9 Java Champions for their opinions about the Java 9 release. In this blog post we’ll feature responses from four Java Champions on what they like and dislike about Java 9.
In this post, I want to share my setup to switch the active JDK version on the command line. Note, I’m use a Mac, and the scripts in this post will work on a Mac and, perhaps, on some Linux machines. If you have a good recipe on how you switch Java versions on the command line on Windows, please share with the community in the comments.
Let’s get to it then. When you download a new JDK release it comes as an installer, so you double click it, click the “Next” button necessary amount of times, and it puts the files somewhere on the filesystem. Or you do it manually.
Download and print out this cheat sheet so you can use it whenever you need. To get fuller explanations and more detailed content in the cheat sheet, continue reading this blog post!
GET THE RxJava CHEAT SHEET!
Well it’s really happening. JDK 9 that is — currently due for general availability on September 21st 2017. As we get closer to the release date, talk around many offices has been intensifying around what we as developers can actually expect from JDK 9.
This makes Java 9 the perfect topic for our next ZTLive webinar. We are thrilled to have two amazing speakers (and amazing human beings) to present on some great Java 9 topics: Venkat Subramaniam and Simon Ritter.
In this post I want to share a word about an awesome library for integration testing in Java — TestContainers. We’ll provide a little background on why integration testing is so important at ZeroTurnaround and our requirements for integration tests. You will learn how TestContainers helps us at ZeroTurnaround with our own integration testing. You’ll also find a fully-functional example of an integrated test for a Java agent.
Common statistical metrics are not applicable in performance testing. Incorrect metrics may cause you to ignore real problems and to optimize where it isn’t necessary. Let us look at the proper way to do performance testing.
In this post, I don’t want to spend time on discussing the module system in detail, but instead, I want to talk about what every Java developer can benefit from: the upcoming API and language changes.
So here’s a list of our favorite API changes in Java 9. Naturally, you can just look at the code examples in the post, to get the gist of what’s shown. But you can also fire up JShell and run these snippets as we talk about them to see for yourself what is going on. I’ll wait for you to start JShell up before continuing… ready? Not yet? Ok… done? Still not? Yeh, it takes a while to warm up… ok it’s started, great! Let’s begin.