When all you have is a hammer, everything starts looking like a nail. It's the same with software architecture: if you are familiar only with the three layer architecture, everything looks like this: front end - business logic - data layer.

Enter reactive programming. It has a lot of definitions, but it's essentially a way of writing code that's based on components that propel changes in a stream.

In this presentation, we're going to discuss the benefits and the pitfalls of choosing a reactive architecture.

Properly done, you will be able to:

have documentation automatically generated for entire data flows, not just for separate methods
have reduced dependency between components
plug in code between components, while still respecting Open Closed principle at all layers
easily add performance counters and test the performance of your components

Past Experience

We'll present a reactive architecture implemented in a few software projects in Qubiz that relies on components that communicate through events. While the code is proprietary, we also have a open-source Github alternative that allows you to play with the concept after the presentation.

Our speaker: Mihai Petrutiu

When he was in high-school, Mihai was considering becoming a priest or a fireman. Luckily, he changed his mind and became a software developer. We say luckily because he's an awesome developer who knows how to give inspiring presentations on just about anything technology. Passionate about software architecture, he is currently researching machine learning and Big Data.

Reactive programming: benefits and pitfalls

Follow this organizer to stay informed on future events

Events you might like

Seară de colinde/5-99 aniSeară de colinde/5-99 ani

Oradea - How to become an Airline Pilot in 2 yearsOradea - How to become an Airline Pilot in 2 years

Seară de colinde/5-99 ani

Oradea - How to become an Airline Pilot in 2 years