

Maurizio Rinder
Lead Software Developer at SQUER
Vienna, Austria
Actions
As a software engineer, I work mainly on application architecture, often focusing on clean code, solid principles, design patterns and domain-driven design. I believe in developing sustainable software that is easy to maintain, offers potential for growth and also gives space for people to improve their skills and enjoy their work.
Aside from my passion for Software Development and -Architecture, I enjoy archery, working out, playing music, and cooking.
My professional career as a software engineer started with 2013. From that year on I helped a startup company to realease its project, joined willhaben for around four years and the journey of new experiences goes on ...
Area of Expertise
Topics
Collaboration with the Hexagon Architecture
We live in a time where complexity rules. In the area of our profession as software engineers we discover more and more that it is not only technology or frameworks at times, but also business cases that are challenging. Business cases especially have a tendency to start by
being easy to implement until they get enriched by more and more rules and constraints.
To tame this kind of complexity it requires a different view on how we organise software projects in their inner structure and what parts of the software should be the centre of focus. The hexagonal architecture is one way to get this done without many sacrifices. It gives space for both parties namely technology and business likewise without interfering with each other. In addition to that it also gives opportunity to concepts of the Domain Driven Design principles and motivates collaboration.
In this talk we will take a look at the building blocks of hexagon architecture and analyse what benefits this brings for the team’s agile process management, collaboration and knowledge sharing. A demo and reference example made by willhaben jobs will support the analysis.
This talk shows what an architecture like the hexagonal architecture can enable; with the focus on inner-team collaboration
Outbox to the "Sea of Simulation"
Have you ever been wondering how you can transfer ships and cats from one software system to another? If this is the case, then this session is the right choice for you!
The outbox pattern is a handy way of implementing data transfer between multiple software systems. Together with Kafka and Debezium this triple builds up a powerful toolkit to ...
* sequentially split software systems into multiple separated services - aka execute the Strangler Fig pattern
* publish events that might be interesting for all other components
* have stable and fail-safe communication
In this session I will show you the basics on how Debezium works. With that knowledge I will then demonstrate how you can introduce the outbox pattern to an existing application.
This talk will demonstrate how to implement the Outbox Pattern using Kotlin, Kafka and Debezium.
Additionally we will disucss cases where the Outbox Pattern might be of good help.
Domain Driven Kitchen Madness
This presentation offers a thought experiment that helps to understand domain discovery lifecycle. Its major part is covered by a real-life example which guides through understanding, decomposing the business and finishes up with connecting those subparts together.
Kotlin Vienna User group Sessionize Event
Collab with the Hexagon Architecture
How does the Hexagon architecture enable collaboration in a team and how does it help to build T-shapeness?
This event uncovers those questions.
Building a ship for everyone with the Hexagonal Architecture
An event that shows how Hexagon Architecture and tactical Domain Driven Design patterns work together.
Will data haben with debezium
Exchanging data reliably within a microservice infrastructure is incredibly challenging. However, if handled properly, this type of data exchange offers new opportunities - not only for existing microservice projects, but also for those project teams looking to split their products up into smaller pieces of software.
Debezium is an application that captures data from databases and produces ready-to-consume Kafka messages. It is a helpful tool for building up message streams that can transfer important data changes to other components for further processing, making it an ideal tool for implementing the outbox pattern.
In this session, we will look at the basic setup of Debezium, implement a small application that uses the outbox pattern, and analyse the benefits this could have for starting a monolith break or transferring a proper message across your infrastructure.
Breaking the Monolith
In this talk I describe different artifacts that are necessary for a good project preparation.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top