Red Hat Forum Poland - Keynote and a Journey Through 3 Pitfalls

Every year in the fall Red Hat organizes events known as Red Hat Forums. These are smaller versions of the experience you can have at Red Hat Summit, without having to travel to either Boston or San Francisco (they switch coasts every year). To make it even easier they are organized all over the various regions of the world, from North America, Europe, and Asia.

On occasion I'm asked to help out by presenting a keynote and sessions during one of the European Red Hat Forums. This year Ive been invited to speak at the Red Hat Forum Poland, presenting three sessions of which one is the opening technical keynote.

Join me in Warsaw, Poland on 5 Nov 2019 for an amazing lineup of keynotes and sessions covering a wide range of topics; Infrastructure & Hybrid Cloud, IT Management & Automation, Cloud-Native Development, and Middleware & Agile Integration.

I'll be talking in the keynote covering an overview of the Red Hat Technological News. After that I'll cover two breakout sessions on the following topics.

5 Questions Everyone's Asking About Microservices (Question 5)

When discussing the development impact on existing applications while transitioning to microservices, there are five questions that keep popping up in one form or another. They are the same regardless of the size of the organization and seem to become part of strategy discussions later in the process as organizations move towards microservice architectures.

These articles cover questions that everyone should ask about microservices. Their based on experiences from interactions with organizations in the process of conquering microservices for existing development and for delivering modern applications.

Previously we covered four questions; the performance impact of microservices,  a question on state and monoliths, one about data and microservices, and on testing microservices.  In this fifth and final article we look at the confusion around using API management or service mesh.

Digital Architecture Design Day 2019 Keynote

On Thursday, November 14 in 's-Hertogenbosch, Netherlands a unique conference for IT architects will be hosted at the Congress center 1931. It's called the Digital Architecture Design Day 2019 (DADD) and they've been so kind as to invite me for a keynote slot.

What's the DADD you ask? Well, in their own words, "It's a community driven event that will reveal the best ways of putting strategy into practice for information intensive, medium to large sized ecosystems that deal with a complex environment. Our goal is achieving sustainable change and coherent solutions by exchanging visions from global thought leaders, best practices, learnings and ideas. Digital Architecture Design Day is a one day conference festival incl. evening program and walking dinner: playground of creativity, innovation and hands-on experiences. People come for the insight, but stay for the networking and fun!"

With a conference full of architects you can expect some of the keynotes to have titles focused on customer centrist design, digital transformation, and other technically focused topics. Nothing wrong with that, but I thought it might be fun to share a story with you about how being more open might just be the secret sauce for your career as an architect.

How's that work?

5 Questions Everyone's Asking About Microservices (Question 4)

When discussing the development impact on existing applications while transitioning to microservices, there are five questions that keep popping up in one form or another. They are the same regardless of the size of the organization and seem to become part of strategy discussions later in the process as organizations move towards microservice architectures.

These articles cover questions that everyone should ask about microservices. Their based on experiences from interactions with organizations in the process of conquering microservices for existing development and for delivering modern applications.

Previously we covered three questions; the performance impact of microservices,  a question on state and monoliths, and one about data and microservices. In this fourth article covers a question around testing stateful microservices.