Every Monday, we take a step back and look at all the cool stuff that went down during the previous week. Last week Quarkus 1.0.0.Final arrived, five new JEPs were confirmed for Java 14 and we published a new interview in our series Women in Tech.
A new lightweight Java framework for Kafka Streams has been announced by StreamThoughts. It aims to improve the Kafka Streams ecosystem and includes a web-based, interactive user interface that helps with administrative tasks and offers a simple DAG representation. Take your first steps with Azkarra Streams and its interactive queries and start writing your app.
IntelliJ IDEA 2019.3 has been released with many new features for users of the Ultimate and open source versions. The team worked on providing a faster startup time and reduced memory consumption to all users of the IDE, while Ultimate users receive additional features.
What are the pros and cons of traditional testing and test-driven development? While traditional testing requires a lot of time and money, using TDD results in faster and cleaner code. Although, TDD requires learning new developer skills. This article examines the two methods and how Java software developers should utilize them.
There are several occasions when you will need to generate code during development. Find out when to generate your own code, what code redundancy is, and when code generation can happen in different cases. In this article, you will also get an overview about Java::Geci, a library for generating Java code in the middle of the compilation, deployment, and execution life cycles.
In this video, you will meet Quarkus, a Kubernetes native Java stack tailored for OpenJDK HotSpot and GraalVM, crafted from the best of breed Java libraries and standards. Alex Soto, software engineer at Red Hat, is passionate about the Java world and will guide you through Java particle acceleration using Quarkus.
We caught up with Red Hat’s Alex Soto at JAX London and spoke to him about Quarkus and his conference session, “Java Particle Acceleration using Quarkus”. Watch the interview and find out about Quarkus, the Supersonic Subatomic Java.
After two release candidates and 30 releases over 36 weeks – that’s one every nine days – the final version of Quarkus 1.0 is here. Don’t feel sad though, the pace won’t slow down and they’re already talking about their plans for Quarkus 1.1! Let’s take a closer look.
How much memory are you wasting with duplicate strings? In this article, Ram Lakshmanan goes through a Spring Boot PetClinic application and notes how much memory it wastes. If you can reduce the number of objects that are created to service new incoming requests, your response time will get a lot better.
Every Monday, we take a step back and look at all the cool stuff that went down during the previous week. Last week we featured a look at ways in which Java is staying young, such as with frameworks like Quarkus, Sourcetrail was open sourced, we looked at edge architecture and its impact on IoT and much more. Let’s take a closer look.
Java and Kotlin go hand in hand, especially when it comes to Android development. Kotlin version 1.3.60 just released and it contains a number of new updates and a few enhancements, including tooling improvements for debugging and Gradle scripts, a new worksheet mode for IntelliJ IDEA, improved error messages, and a preview of some Kotlin 1.4 features.
Java is no spring chicken and some are even referring to it as a “vintage language”. Despite its popularity, there are some complaints about it. In our new cloud-native world, why does Java need to evolve? In order to evolve to keep up with modern, cloud-native apps, Java needs to keep all of what makes it so dependable, while also being able to function in new app environments.
Take a tour of ycrash in this article by Ram Lakshmanan. ycrash helps capture critical artifacts, including garbage collection logs, thread dumps, core dumps, heap dumps, disk usage, and more when the problem happens. It applies machine learning algorithms and generates a report which gives you a complete view of the problem, down to the lines of code that caused it.