33rd Degree to knowledge


I'm not sure I can be treated as a java master, but fortunately thanks to Warsaw Java User Group I had a chance to attend the 33 Degree Conference. Schedule looked very impressive as there were many rock-star speakers and outstanding talks. It was really hard to choose valid path, but after taking some hard decisions I've created the custom agenda. I've never liked keynotes, so let me start from regular talks :)

I've already noticed that Estonia is quite unique in the market of superior Java tools - companies like ZeroTurnaround and Plumbr are doing really nice job. I like them especially when they are talking about as interesting things as JVM internals :) Nikita Salnikov-Tarnovski made very nice presentation titled How much memory do your objects really need? Apart from the fact that he is showman the talk was really interesing! He introduced java-object-layout tool which can analyze object layout schema in different JVM's - another advantage is that this project uses internally sun.misc.Unsafe ;)

I've also decided to check what Sławek Sobótka knows about my mother, and why she has never told me something important about automated testing. Fortunately after one hour of listening accurate metaphors and well grounded strategies I see that she didn't do that intentionally - ufff.... In the other case it would be very depressing fact.

Next step on my list was Baruch Sadogursky talking about Developing for multi-component environment while keeping your sanity. He described (IMHO very mature) process for maintaining developers environments in JFrog - using Chef, Vagrant and GIT. It was so professional that I still can't understand why he uses Windows instead of Linux? :)

Another good presentation was about Architecture without Architects. Erik Dörnenburg exchanged term "architect" with "gardener" - which sometimes adds new plants but mostly takes care of the existing ones. I totally agree with him! Especially when we compare the level of the details between software systems and civil engineering plans. The conclusion was that each developer has to take care of the system quality - not only "the chosen one". At the end he also shown some nice tools for visualizing source code like CodeCity - it looks delightful.

Last but not least (unfortunately aggrieved by going parallel with Venkat Subramaniam) was Andres Almiray. Groovy developer is definitely competent to talk about Polyglot Programming in the JVM. He  described similarities and differences between Groovy, Scala and Clojure. As Groovy has very nice and close to Java syntax, Scala is very powerful I thoroughly can't understand pros of Clojure... but I really understand why there are so many haters of this specific language ;)

Sadly I had no chance to attend the last day of the conference and listen about polyglot persistence and Vaadin 7 but maybe I'll have another opportunity in the next year :)

Comments

Wojtek Erbetowski said…
Not a fan of keynotes? Maybe we should suggest to drop them and replace with more regular lectures :)
March 19, 2013 at 11:19 AM
StackHolder said…
That's really nice idea :) In fact on the JDD'12 there were no keynotes :)
March 19, 2013 at 2:35 PM
Unknown said…
KeyNotes were great! Idea of 33Degree is that it's for Java Masters - so not only technical speeches, some of them was suitable for eg. team leaders how to lead a team. Do you know that some .NET guys came on this conference?
March 20, 2013 at 2:27 PM
StackHolder said…
Ok, but why it have to be keynote and not just a regular talk? In my opinion there were nothing new in "7 things" or "decisions decisions".
March 20, 2013 at 3:13 PM
Unknown said…
Well, dear Watson, I;ll tell You why - because of sponsors. They paid for possibility of talking to all atendies.
March 21, 2013 at 11:59 PM
StackHolder said…
That's the point dear Sherlock :)
March 22, 2013 at 1:48 PM
Post a Comment

Popular posts from this blog

Overview of the circuit breaker in Hystrix

Libraries provided by Netflix , usually look simple, but after a deep dive, you will realize this stuff is pretty complicated. In this article, I want to explain behavior and usage of the circuit-breaker pattern being a part of the Hystrix . Following the Wikipedia definition "Circuit breaker is used to detect failures and encapsulates logic of preventing a failure to reoccur constantly (during maintenance, temporary external system failure or unexpected system difficulties)." What does it mean? For example, let's consider the circuit as a connection between two services. It operates normally (aka stays closed) when the connection is stable, and the target service is healthy. We can execute our requests (assume 100 per second) without any problems. But when our target service is down (what we know after a few unsuccessful tries), it no longer makes any sense to try 100 times per second. So we open our circuit and serve responses from a predefined fallback, as we kno
Read more

Understanding Spring Web Initialization

Few years ago majority of us were used to write XML config files everywhere, to setup even simple Java EE application. Today using Java or Groovy to configure projects is becoming preferred way - you just need to take a look at Gradle or functionalities introduced in further versions of the Spring Framework to gen up on this. Now I'll deal with configuring Spring contexts for web application. Java EE provides ServletContainerInitializer interface, which allows libraries to be notified of a web application startup. Since Spring 3.1 we have SpringServletContainerInitializer class which handles WebApplicationInitializer by instantiating all found classes implementing this interface, sorting them basing on @Order annotation (non-annotated classes gets the highest possible order, so they are processed at the end) and invoking onStartup() method.
Read more

Do we really still need a 32-bit JVM?

Image
Even today (and it's 2015) we have two versions or Oracle HotSpot JDK - adjusted to 32 or 64 bits architecture. The question is do we really would like to use 32bit JVM on our servers or even laptops? There is pretty popular opinion that we should! If you need only small heap then use 32bits - it has smaller memory footprint, so your application will use less memory and will trigger shorter GC pauses. But is it true? I'll explore three different areas: Memory footprint GC performance Overall performance Let's begin with memory consumption. Memory footprint It's known that major difference between 32 and 64 bits JVM relates to memory addressing. That means all references on 64bit version takes 8 bytes instead of 4. Fortunately JVM comes with  compressed object pointers  which is enabled by default for all heaps less than 26GB. This limit is more than OK for us, as long as 32 bit JVM can address around 2GB (depending on target OS it's still about 13 times l
Read more