[DB Station&Service] Insights into the Cloud-Native Architecture of the Traveller Information Publication Plattform IRIS+

Insights into the Cloud-Native Architecture of the Traveller Information Publication Plattform IRIS+

How to edit? (delete this section after editing)

1. Rename the page title above - choose a catchy title for your session. This is what the other will see in the overview list to rise their interest. So try not to just state the topic but what you intend to do with it in the session. For instance, not just 'displays' but 'how to make displays exciting for travelers' (or whatever else you want to focus on)
2. Fill out session summary below
3. Delete this info section - click on the frame and hit delete on your keyboard
4. Save this session page - click the Save button in the lower right corner of this page

Here is an example for a session page: Example for a session page.

Session Summary

Summary
Topic	Insights into the Cloud-Native Architecture of the Traveller Information Publication Plattform IRIS+
Session host(s) Enter your own name, if you suggest this session. Anyone that may later co-host, can then add his name here in the same way.	Jörg Riechers
Duration	1
Type	45 min presentation  + 30 min dialog

Key issues, questions, desired results

This session will explain the architecture of  our newly built publication platform IRIS+ with the specific perspective of cloud computing. You will learn the differences between “traditional” software platforms (even if they are  operated in a cloud environment after a “lift and shift” migration) and modern microservice architectures in the context of traveler information processing. What are the advantages of this architecture? Which challenges we had to address during the development and the operation phase of our project? After the presentation we would like to discuss specific questions and share similar experiences on a conceptual or technical level.

Material

Add potential material for the session.

Session Results and Notes

This section is reserved to keep notes about the session results during or after the session. so that this information is available to all participants after the BarCamp.