Talk Details

Spring, Jakarta EE, CDI and other pathologies

Conference
Architecture

If You code in Java You probably deal with the frameworks mentioned in the title. Maybe You even started to believe that they help You to write code faster, safer and easily testable. Well, that is just marketing. You encounter and solve problems cause by those platforms everyday and You simply ignore the costs ... because You do not know the alternatives. In this session I show why the king is naked (all the kings), why no serious project should use all those Bean based frameworks on production. I will show problems are caused by container dependency injections and present more then 10 reasons why annotations such as @Transactional fail miserably - and You do not even notice. Platforms that were created to solve problems of distributed programming and web development 20 years ago do not really help us that much in 2019. For, we have really better and safer alternatives now.

Scheduled on Saturday from 17:40 to 18:30 in Room 5

Dependency Injection Solution
Aspect
Spring
Functional Java
Enterprise Java

Jarek Ratajski

Engenius GmbH

I love programming since my first line of code I did on  the C64  in Basic. Somewhere in 90ties I've switched from C++ to java and spent then 18 Years developing mostly Java software working for various companies and projects.  Now I work for Engenius in Switzerland being Java/Kotlin developer during the days and Scala/Haskell open source hacker at nights.