Tilde Loop: Summer Tech Event
A month after we opened our office in Split we organised our first event – Tilde Loop: Summer Tech City Event. The event brought together the developer community in Split and the lounge room of The Works Coworking space was full of developers who came to listen to the panel discussion and network.
Before the panel discussion itself, Bruno Ziterbart, the founder of Tilde Loop, briefly presented the company. He pointed out that Tilde Loop is focused on programming, technological progress and the growth of each individual and team, and chooses clients accordingly. He highlighted startup Hero, which was acquired by Klarna for $168 million, and The Lowdown – a femtech startup that recently closed a seed round of investments of $2.5 million to upgrade its platform for women’s contraceptive health.
About software architecture
Soon we moved on to the main topic of the evening – software architecture.
The panel discussion was moderated by Marija Ziterbart, CTO of The Lowdown and director of the London office of Tilde Loop.
To begin with, all panelists shared their experiences on different types of software architecture that they encountered in their work, with a special emphasis on microservices and event-driven architecture.
After highlighting the advantages and disadvantages of microservices, they discussed the team structure and how it affects the software architecture.
Architecture and onboarding process
About the onboarding of new team members Leon Petrov said:
“From my experience, it’s easier to onboard new team members on well-structured microservices projects than on large projects that have a monolithic architecture. In that case, a large codebase lengthens the onboarding process.”
All the panelists agreed that the microservice architecture, in addition to easier onboarding, also ensures a better division of responsibilities because then it is known exactly which team deals with which microservice.
With a monolithic architecture, it can happen that due to the unclear division of responsibilities, certain bugs are ignored, which later causes problems.
Although in most cases microservices are understood as the best choice of architecture as the project grows, not everything is black and white. Mensur Duraković gave an example of a well-structured monolith he read about, which was still successfully used by a company with a large number of users.
They also touched on the monitoring of microservices, and Bruno Ziterbart said from his experience: “Two types of logs are monitored – logs related to the infrastructure and logs about errors that occur in the application. Each service and handler has its own ID so that it can be read from the log where the error is in order to fix it as soon as possible”, and he suggested Datadog as a monitoring tool.
Advice, questions, and networking
At the end of the discussion, the moderator asked the participants to share advice for developers who are starting to implement complex software architectures, after which they moved on to numerous questions from the audience.
When the curiosity of all present was satisfied, the networking continued with food and drinks in a great atmosphere.
We are satisfied with the response and feedback from the visitors and will certainly organise more events like this.