Program JavaZone

Foredrag Onsdag 2. september

Architecture Under Fire: The Decisions Nobody Tells You About

Room 4

Engelsk 45 min software architrecture decision making technical leadership architecture patterns trade-offs system design best practices

Mihaela Gheorghe-Roman

Mihaela is an Experienced Software Architect at Systematic, Romania, and an Oracle ACE Associate for Java. Ph.D in artificial neural network algorithms, Assistant Professor at the University of Cybernetics and Informatics in Bucharest, she is a dedicated lead developer and architect who enjoys sharing her knowledge.

In her professional career, spanning over 14+ years, she worked for telecom and defence domains with a focus on Java, Spring Boot, C, C#, Scala and Angular.

Apart from her passion for programming, she loves parrots, she is enthusiastic about traveling the world and doing a lot of sports, from running at marathons, martial arts and to different aerobic trainings.

Architecture books teach you patterns. They don't teach you how to choose between them when you're under pressure, facing incomplete information, and living with real consequences.

In mission-critical systems, architectural decisions aren't just about code quality - they're about operational success. A poor choice doesn't just create technical debt; it can impact system availability, security posture, and the ability to respond when things go wrong.

This talk explores the reality of architectural decision-making in high-stakes environments through several real scenarios:
- A legacy system that needs modernization - rewrite or evolve?
- A performance vs. maintainability trade-off with no clear winner.
- A microservices migration with strict operational constraints.
- A critical dependency that stopped being maintained.
- An availability commitment that might not be achievable.

You'll leave with a framework for making better architectural decisions when the stakes are high and the right answer isn't obvious.

Software architects, technical leads, developers, software engineers. How participants will benefit? They will leave with pattern recognition for architectural risk and red flags, techniques for making decisions with incomplete information, real examples of architecture decisions, outcomes and lessons learned from different situations. In terms of recommended experience, I would say that everyone is welcome to participate. It could be beneficial to have a basic understanding of common architectural patterns like monolith, microservices, layered architecture and distributed system concepts (high level is more than enough).

  1. Dream Machines & Walled Gardens Room 1
  2. Bra tools, ubrukelige svar: Læring fra ett år med MCP Room 2
  3. Building Production-Ready Kubernetes Operators: A Practical Guide Room 3
  4. SIMD for Java: how Elasticsearch already benefits from the Panama Vector API Room 5
  5. Bare spør! AI-agenter elsker produksjonsmetrikker Room 6
  6. Let’s use Spring Boot to build games, because why not? Room 7
  7. Demoscene Coding Kickstart Room 8
  8. De usette langtidskostnadene med dagens KI Room 6