Key takeaways

JAX London 2018 Day 1: All the wisdom we gathered so far

Eirini-Eleni Papadopoulou
jax london 2018
JAX London 2018

JAX London Day 1 is over! During this amazingly rich day, we gathered a lot of knowledge and wisdom from the interesting and educational keynotes and sessions. Tips, tricks, crucial advice, important clarifications – we have it all! Let’s have a closer look at the key takeaways from JAX London Day 1!

We’ve had an amazingly rich and informative day 1! JAX London 2018 kicked off with Daniel Jones’ keynote on continuous delivery.

As Daniel Jones explained, continuous delivery helps us bring different parts together – you have a shared identity so you also share the same problems. But you don’t have to share your resources because everyone is part of the same project.

Continuous delivery dictates that everything that is important for one feature is important *now* – not in three months time. This helps to exploit the present bias not falling victim to it.

Jones concluded his talk by urging people that “one has the moral responsibility to change unfit process.”

Our busy day continued with two very informative sessions, that of Desy Kristianti on building a network of APIs using middleware integrations and Simon Ritter’s talk on delivering new features in the JDK.

Starting with a quick survey among participants during Ritter’s session, we realized that a lot of people are still using JDK 8. Not a lot of participants are using JDK 11 in production. Not yet, at least! What’s more, as it was clarified during the talk, even though there will be an LTS every three years, this does not automatically mean three years of free updates.

Oracle JDK (from JDK 11 and onwards) can only be used in production with a commercial support contract. The only free JDK 11 and later will be OpenJDK binaries. To continue to receive free updates to the JDK, you must update your JDK every six months

During Desy Kristianti session, we looked into the importance of API integrationAPI is the technical interface of the microservices; these two terms cannot be used interchangeably though. But what are the most important initiatives for IT decision makers? Kristianti mentioned the following things:

  • Modernizing legacy systems
  • Integrating SaaS apps
  • Migrating apps to the cloud
  • Setting up an eCommerce platform
  • automating business processes

Furthermore, she explored the advantages, disadvantages, and results of using middleware integration.

Up next we had yet another educational session with Liat Palace, who walked us through the implementation of the holistic DevOps approach in a large scale organization.

Palace challenged us:

If you want to see how your team works together, take them to the kitchen! See how they communicate and collaborate. Whatever happens in the kitchen is transferable to the office!

Have you ever wondered how to test your software if your team is not integrated and they don’t speak the same language? What do you do when you have a team that is responsible for operability and another team that is managing the program? In order to make everyone work together, you need to change your organization.

Bear in mind, however, that shifting an organization is not easy – it’s pretty much like changing a person’s DNA.

Liat Palace gave us some very useful tips:

  • Learn from others
  • If you need to change, you have to create the atmosphere of change
  • You need to look for partners, you cannot change an organization alone. You can go top down and bottom up.
  • Ask yourself the question: Is mixing Dev and Ops enough?
  • Pay attention to the software delivery pyramid: People – Technology – processes
  • Terminology alignment
  • Approach alignment
  • Problem state definition 
  • Assessment – You need to understand where you are. Needs to be done simultaneously – the project is running

Moving on from DevOps to cloud, the panel discussion held by Daniel Bryant, Jessica Deen, Sebastian Meyen, Steve Poole, and Martijn Verburg was an absolute hit!

The panelists talked about what cloud native means for Java developers, its present, future, as well as the fear around its adoption. Jessica Deen noted that you should be comfortable with the fact that you don’t know everything. There are new technologies being constantly released. Be comfortable with the fact that you can’t know everything.

Using cloud native technology makes you portable and resilient. But it is scary. And you should know that you are not alone in that. Even the people in this panel feel this fear. 

Jessica Deen

The panelists wrapped up their discussion by asking themselves the following question: What’s the cloud going to look like? Well, the answer was that we’re still just exploring. However, one thing is for certain. The monolithic days are behind us for good, according to Jessica Deen at least! 

We are absolutely thrilled to see everyone that made it here and we look forward to the wonders that await us tomorrow! Stay tuned!

Eirini-Eleni Papadopoulou
Eirini-Eleni Papadopoulou was the editor for Coming from an academic background in East Asian Studies, she decided that it was time to go back to her high-school hobby that was computer science and she dived into the development world. Other hobbies include esports and League of Legends, although she never managed to escape elo hell (yet), and she is a guest writer/analyst for competitive LoL at TGH.

Inline Feedbacks
View all comments