On 19-20 March 2019, Phantasialand in Brühl will be transformed into "Javaland" for two days and we will be there again this year with numerous colleagues. There is a lot to see, hear and learn, and in view of the full program each of us thinks about which of the topics interests us the most.

Andreas: > Visiting Javaland 2019 is split into two perspectives for me. Despite all the progress on a technical level, I still see great potential for improvement in the working methods. Especially when working with agile and less agile customers in a wide variety of projects. Against this background, I hope to get impulses from other teams and their successes and failures, which will help us to become even better in our daily work. For this reason I would like to go drinking with Luke Skywalker, while the architect talks about his crisis of meaning. After I then heard the secret of successful teamsthen I reinvent myself to be able to accept failure more easily , before i then im Junglewake up. At the same time, on the technical side, we see the importance of cloud and microservices becoming more and more important - also in the SAP universe. For this reason, there are also some lectures on these topics on my agenda. The whole thing is crowned by a road trip with a roller coaster, what more could you want...

Gerrit: > At Javaland, I would like to deal primarily with architecture and microservices in order to be able to better evaluate or understand the architectural decisions that are often given to us. Examples are database modeling (relational databases are great) and tracing of microservices, but also structuring of the applications themselves, as well as Event SourcingI am also interested in a few other topics that could be a bit more mathematical. One topic that particularly appeals to me is " Data Science meets Software Data". I used to deal a lot with statistics, so I'm interested in what conclusions can be drawn from the source code and other services (e.g. monitoring tools). Examples would be e.g. to check whether missing documentation of the source text actually leads to high effort when training new employees or whether no effect can be observed. I would like to talk to the speaker in particular about this. I would also like to know more about them Learn guts of the JVM. An important part of a conference is the exchange with other people. Learning from other conference participants how they use the technologies, what they use them for and what problems they have with them is an advantage over watching YouTube videos.

Leo: > I would like to use Javaland 2019 to gain insights into the technological trends that have been on the horizon for some time and are increasingly finding their way into our everyday developer life. For me, this mainly includes the microservices/SCS concept and container systems. While we are already using both in customer projects, it is important to get new input and best practices for development and maintenance. There is so much going on right now and you have to be careful not to let yourself be left behind by everyday life. At the end of Javaland I hope to have a better sense of the possibilities and to be able to monitor split systems and deal better with the new responsibilities (e.g. DevOPs). Apart from that, all Java-specific topics are of course very interesting for me. Examples include Java natively compiling, new features in the language (Valhalla, Amber, etc), speech recognition, and Spring's integrations with Docker & Kubernetes. My schedule for Javaland is pretty full, but I just let it come to me and try to take as much with me as possible.

Matthias: > Since I am currently working on a microservice, I am curious about this topic or the trend of microservice architecture. For me, this includes: What do “really good” microservices look like? Which architectural patterns and which technologies should/must one understand and use? What are the challenges and how can you tackle them? Does it always make sense to build microservices, or are there disadvantages? The focus is on what you can integrate into your daily work with existing microservices and what you have to consider when building a completely new one. The topic is currently so interesting for me because the competition between web applications is increasing and classic development models are often no longer so well suited (the "monoliths"). The advantages can be found quickly: Microservices make it possible to keep the code quality high, since instead of a huge, historically growing codebase, a codebase tailored to a purpose is created. This application can be more flexible in its architecture than an "all-in-one service". Instead of a large team that takes care of all parts of the application and may have to coordinate this in a time-consuming manner, there is distributed work by smaller teams who know their code very well. And most importantly, a bug in one service affects (not necessarily) the other services and can be re-delivered separately in the event of a bug.