Java has become one of the world's most mature platforms, bringing several paradigms beyond OOP.?
Indeed, OOP has several benefits to an architecture design; however, as with any solution in Software engineering, it is not a silver bullet. Thus, it also has trade-offs.
In the newest Java LTS, we can explore more the miracles of Records or even sealed classes on several points, including data-oriented.
But are the frameworks ready for this? Can we use it with JPA? and why not?
This news will bring several articles to answer this and other points, such as the C4-model.
- PostgreSQL 14 Breaks the .NET and Java Drivers for PostgreSQL: If you’re using Postgresql, this is something to worry about. However, if you're using a high-level persistence framework such as Jakarta JPA, Spring Data, etc. this is abstracted for you!
- Data-Oriented Programming in Java: In this article, Brian Goetz talks about new possibilities in code design with a new paradigm: Data-Oriented Programming. This is inspired by the latest Java features such as Record and Sealed classes.
- Transitioning into the Staff+ Engineer Role - from Player to Coach: When transitioning to that next Staff+ role, you need to understand what the company expects, either through career frameworks or your manager.
- Helidon 3.0 is released: The newest Helidon version has support for Jakarta EE 9.1 and Microprofile 5.0; thus, it is one of the first versions after the Jakarta Big Bang.
- The Spotify System Model: Automated Architecture Visualization at Spotify: Spotify engineers recently published how they standardized architecture diagrams at the company. They defined a standard system model named the Spotify Software Model and adapted the C4 model to visualize it.
- Data Software Design Pitfalls on Java: Should We Have a Constructor on JPA?:? In this article, explore details on code, especially inside the Jakarta EE world, mainly to answer the questions: should we have a constructor on JPA, and why?
- The Future of Java by Mark Little: Learn about the latest innovations in Java, including how Kube-native Java,? Quarkus, OpenJDK, and Eclipse Adoptium are proving to be increasingly important in a Kubernetes environment and how you can be on the leading edge of Kubernetes-native Java developers.
- Diagrams as Code 2.0: The essence of "diagrams as code 2.0" is a way to define a model of our software architecture and the views we'd like to see, ultimately resulting in a consistent set of diagrams generated for us.
- Java's Encapsulation - When the getter and setter became your enemy: Encapsulation is the key to a good code design, but how to achieve it?? Java developers automatically think about putting getter and setter in a private attribute.
