Portrait of Alexander Heusingfeld

Alexander Heusingfeld

Alexander Heusingfeld is a senior consultant for software architecture and engineering at innoQ in Germany. As a consultant, software architect and developer he supports customers with his long-term knowings of Java and JVM-based systems. Most often he is involved in the design, evaluation and implementation of architectures for modern web-applications and microservices in software modernization projects. His current focus is on team organization and software evolution.

He loves to contribute to OpenSource projects, speaks at IT conferences and Java User Groups and occasionally blogs at http://goldstift.de/.

Tel.: (+49) 2173 3366 0

Talks

Talk
Talk

Von „schlecht“ zu „viel besser“ in drei Iterationen – Softwaremodernisierung am Beispiel

Software Architecture Summit 2018, München / 10:00 - 13:00

Talk
Talk
Slides available

Architekturmodernisierung mit SCS und Microservices

OOP 2017 / 18:00 - 19:00

Talk
Talk

Dynamisch überwacht: Monitoring von Microservice-Architekturen

Microservices Summit 2016 / 10:00 - 13:30

Talk
Talk

Dynamisch überwacht: Monitoring von Microservice-Architekturen

Microservices Summit 2016 / 10:00 - 13:30

Talk
Talk

Microservice-Architekturen zur Modernisierung von Bestandssystemen

Microservices Summit 2016 / 14:30 - 18:00

Trainings

Training

Training

Flexible Architekturen: Microservices, Self-contained Systems und Continuous Delivery

iSAQB Modul FLEX

Hotel NH Düsseldorf City

Training

Training

Flexible Architekturen: Microservices, Self-contained Systems und Continuous Delivery

iSAQB Modul FLEX

Holiday Inn München-Unterhaching

More content

Article

Probleme bei der Einführung von Microservices: Seien Sie vorbereitet!

Article

Warum wollen Sie Microservices einführen?

Erst Ziele klären, dann Microservices machen

Article

Innovation Tokens – Gegen Informatikerromantik und Technologieüberflutung

Wie viel Innovation sollen wir zulassen?

Article

Deployment und Monitoring von Microservices

Link

Microservices im Experten-Check, Teil 3: Wie groß sollte ein Microservice sein?