Best Practices für moderne Softwarearchitektur & 3 approaches in API Development

Dear Java Community,

the new year has only begun and we already start to work on our new years resolutions -> more knowledge sharing!

So I am happy to announce our next OpenValue Meetup on 23rd of January!

We will start this years Meetup-Season with two high quality talks! In the first Session, Enis will help us to bring our API-Development skills to the next level in showing us three approach on how to develop our APIs effectively!

Right after that, Falk will show us common patterns and best practices to improve our confidence and workflow when designing the architecture for complex software systems.

Come to our office at “Am Wehrhahn 41, 40211 Düsseldorf”, and join us on our journey to get and share high quality Java and software development knowledge!

We’re taking care of food, (cold) refreshing drinks!

Don't miss out on this and RSVP to confirm your attendance.
Agenda:

• 17:30 Walk in
• 18:00 First Talk
• 18:45 break
• 19:00 Second Talk
• 19:45 Drinks and Discussions

First Talk:

"Three approaches in API Development"
by Enis Spahi

Code First, API First and Consumer First are three approaches in API development. But which one is best fit for my API?
In this talk I will present a live demonstration of Code First, API First, Consumer First approaches in API development. I will highlight how each approach impacts the interactions between providers and consumers. Additionally, I will explore some additional use-cases where we can mix-and-match these three methodologies. During this part I will uncover the capabilities around OpenAPI Specification, the power of OpenAPI Generator and Pact Contract testing to improve provider and consumer experience.
By the end of this talk, the audience will gain practical insights into selecting and applying the right API development approach for their projects.

Second Talk:

"Vorgehensmuster und Best Practices für moderne Softwarearchitekturarbeit" by Falk Sippach

Die Arbeit an unseren Softwaresystemen wird immer komplexer. Insbesondere der explizite Entwurf und die Kommunikation der Softwarearchitektur sind entscheidend um flexible, wartbare und skalierbare Systeme zu gestalten. Wir schauen uns gemeinsam verschiedene, praxiserprobte Praktiken an, um Architekturarbeit dynamischer zu gestalten und den Architekturentwurf effizient in Projekte nach agilen Vorgehensweisen integrieren zu können.

Wir diskutieren Ideen für die grundlegende Architekturarbeit (z. B. das Sichtbarmachen von Architekturanforderungen in Form von Szenarien und technischen Schulden), das Treffen von Entscheidungen (z. B. letzter vernünftiger Moment und gerade genug Architektur vorweg), die Zusammenarbeit und Interaktion (z. B. Architektur-Communities und -Katas) und die Reflexion (Testen von Architekturzielen). Ihr könnt viele dieser Vorgehensmuster und Best Practices leicht auf Eure eigenen Projekte übertragen.