Fr 11.10.

12:00-16:00

0501

-

1. Definition of 4 subteams

Do 17.10.

10:00 - 13:00

0503

Joint workshop with Social Workers (Prof. Zorn), 

confirmed

1. Eventstorming as method for domain exploration

-

Fr 25.10.

12:30-16:30

0501

Annegret Junker (adesso)

confirmed

1. Finalization of Event Storming
2. Identification of subdomains
3. Subteams pick their subdomain to work on

Each subteam documents the following in the wiki of its own Github repo:

1. results from Event Storming (in written form)
2. a domain vision statement in the  (see glossary definition here)
3. a first version of its own domain model (see glossary)
4. glossary entries for the domain model elements and other important terms (see here for instructions how)

Do 7.11.

10:00 - 13:00

3109

(2)
Archi-tecture Goals

(3) Micro-service precon-ditions

(4)
Service size

1. Setup of own dev env
2. Teams start to transform BC into JPA annotated entities
3. Teams start to implement simple CRUD services

1. simple CRUD services ready to show

Fr 8.11.

12:30-16:30

0501

Fr 15.11.

12:30 - 16:30

0501

Ansgar Schulze Everding (Rewe Digital)

confirmed

1. Discussion of lecture,  roadmapping for own sub-domain (=> wiki!)
2. Agreement on team time tracking for later evaluation
3. Consolidation of glossary entries
4. Update of domain model:
   1. integration / clustering of events
   2. decision: which entities does our subdomain own, what do we require from others?

1. In wiki: Roadmap for further steps in this project
2. Team time tracking decided & described in local decision
3. Update of glossary items
4. Updated domain model

Fr 22.11.

12:30 - 16:30

0505

NEW!

(2) - (3)
Docker-ization 

NEW! Introduction to Docker

• Intro / live demo: How can we package our code as Docker container?
• And how to deploy it to the build pipeline?

1. Teams set up Docker containers and build pipeline configuration

1. Running software in browser, can be queried using Postman

Fr 29.11.

12:30-16:30

0501

(1) Under-standing the Domain

(4)
Service size

• brief presentation of current status

1. All feedback comments addressed
2. Decisions and glossary updated (please take into account changes to domain boundaries, as discussed between the subteams!)
3. Event documentation complete
4. Events mapped to entities in domain model
5. High level REST API design available, based on events
6. CRUD REST API unter archi-lab.io accessible

Fr 06.12.

12:30-16:30

0501

(5)
REST

(6)
Eventing

API Ecosystems

APIs are omni-present nowadays and an important vehicle for enterprises to broaden their product offerings. Form an IT perspective, an API-led architecture is key to react on changed business requirements in an agile fashion. An API design-first approach is key to enable this kind of agility, especially with regards to µServices architectures and DevOps.

During the session, we’ll take a look at the following points:

• Meaning of APIs in a µServices architecture
• API Interaction patterns (Synchronous/asynchronous APIs, events)
• Consistent API design & API design-first approach
• API life cycle and how to incorporate it with a DevOps approach
• Characteristics of API-led architectures (Basic architecture components like API Gateways)
• API implementation (Alternative approaches to REST (GraphQL, gRPC), Reactive vs. Non-reactive API implementations)

Besides the respective theoretical concepts, we will look into some practical examples to make aspects of the concepts more transparent.

Sven Bernhardt (Opitz)

confirmed

• Teams discuss their API strategy with regard to "big picture"

1. Take Open API 3.0 into use in your service to model and mock your REST APIs
2. Model the events mapped in your domain model using Apache Avro (and generate the corresponding classes). This is supposed to be a PoC (proof-of-concept) to validate if this works for us.

Fr 13.12.

12:30 - 16:30

0501

(5)
REST

(6)
Eventing

• Teams revisit their event storming notes, build state diagrams, decide on which style to use
• Teams discuss their overall APIs (REST, events) and business logic: Is it sufficient to model the dummy UI scenario(s)?

1. REST API decisisions and structures specified & documented, endpoints available
2. Event structure  specified & documented, Kafka topics implemented 

3. UI Dummy in Node Red implemented

Fr 10.01.

12:30 - 16:30

0501

Transactions between Microservices

• Transaction patterns (event sourcing, Saga pattern, interaction between REST and messaging)
• Introduction to messaging and frequently used technologies

Sebastian Gauder (Rewe Digital)

confirmed

• Teams revisit their events (provider, consumer) and connection to message broker
• Possibility to discuss technical difficulties

1. Continuation of integration work as described above. 
2. Goal: Scenarios are fully implemented, and can be demonstrated

Do 16.01.

10:00 - 13:00

0503

-

• Subteams use Excel to walk through the methodology for their subdomain
• See 10 - Method Framework for Social Impact and Ethics Analysis (Work In Progress)

1. Include "your" Excel as a link in your Github wiki
2. Briefly sum up your main findings from the group discussion process in your wiki (2-3 sentences is sufficient)

Fr 24.01.

12:30-16:30

0501

UIs in a Microservice Landscape

• Popular MS patterns to connect UIs: API Gateway, Backend for Frontend
• Do’s and Don’ts when connecting clients
• UI integration concepts (HTML links, monolithic UIs, client / service side composition, Micro Frontends, ...)

Wolf Schlegel , Niko Hellwig (ThoughtWorks)

confirmed

• Teams discuss the best UI paradigm, and sketch the UI

• Reflection in the documentation: How appropriate is the UI structure as induced by the Node Red based dummy UIs?

Fr 31.01.

12:30-16:30

0501

Mo 3.2.

12:00 - 17:00

tbd