I recently attended Oracle Code New York City 2017, and I thought I'd go over my experiences and thoughts on them, from keynote speakers to the latest news. Without further ado, let's dive in!
Chris Richardson did an amazing walkthrough and discussion of the what/why/how/when of microservices. This is incredibly powerful material. Chris explains it very well and removes some of the misinformation around microservices. A full two hours from the keynotes are already on YouTube.
As I wrote some weeks earlier, I’m trying to implement features of the Spring Boot actuator in a non-Boot Spring MVC applications. Developing the endpoints themselves is quite straightforward. Much more challenging, however, is to be able to configure the mapping in a properties file, like in the actuator. This got me to check more closely at how it was done in the current code. This post sums up my “reverse-engineering” attempt around the subject.
In Spring MVC, in a class annotated with the @Controller annotation, methods can be in turn annotated with @RequestMapping. This annotation accepts a value attribute (or alternatively a path one) to define from which path it can be called.
There seems to be an ever-ongoing discussion about how powerful an entity object should be. That’s indeed a very valid discussion, as the choice that we make (often unconsciously) will have a huge impact on the final shape of our application. Let’s see what options do we have and try to analyze the consequences of each.
Language: Enterprise, Expertise: Intermediate — For reading operations, the transaction configuration readOnly flag should be set to true and in order to execute native queries, the @Query annotation parameter, nativeQuery flag, should be set to true.
Language: Java, Expertise: Intermediate — Spring provides a nice abstraction on top of the JDBC API using JdbcTemplate and also provides great transaction management capabilities using annotation-based approach.