Saulo Soares De Toledo

Doctoral Research Fellow - Programming

Norwegian version of this page

Email saulos@ifi.uio.no

Room 10th floor

Username

Visiting address Gaustadalléen 23B None 0373 OSLO

Postal address Postboks 1080 0316 OSLO

Other affiliations Faculty of Mathematics and Natural Sciences (Student)

Press photo Download business card

Research interests

Technical Debt
Software architecture
Microservices

Academic background

Master's degree in Computer Science. Area: Recommender Systems for Software Engineering (UFCG, Brazil)
Bachelor's degree in Computer Science (UFCG, Brazil)
Licentiate degree in Computer Science (Teaching, 4 years graduation) (UEPB, Brazil)

Work Experience

Senior/Master Developer (1 year+)
Senior Developer (1 year, 11 months)
Web developer (9 years+)
Computer Technician (2 years+)

Additional experience

Classroom Mentor (Udacity): Work 1-on-1 with students and help them to make progress, keep on track, and reach graduation. Areas: introduction to programming and front-end development with HTML, CSS and JavaScript.
Project Reviewer (Udacity): Review student project submissions, striving to give actionable and helpful feedback. Areas: introduction to programming and front-end development with HTML, CSS and JavaScript.

Professional certifications

Professional Scrum Master I (PSM I)
Certified Professional for Requirements Engineering - Foundation Level (CPRE-FL)
Certified Tester - Foundation Level (CTFL)
Zend Certified Engineer - PHP 5.3 (ZCE)
Microsoft Certified Professional (MCP)
Microsoft Certified Solutions Associate: Web Applications Charter Member (MCSA)
Microsoft Certified Solutions Developer: App Builder Charter Member (MCSD)
Microsoft Certified Solutions Developer: Web Applications (MCSD)
Microsoft® Specialist: Programming in HTML5 with JavaScript and CSS3

More about

Tags: Technical Debt, Architectural Technical Debt, Software Architecture, Microservices, Senior Developer, Programmer

Publications

Scientific articles and bookchapters

Soares De Toledo, Saulo; Martini, Antonio; Przybyszewska, Agata & Sjøberg, Dag (2019). Architectural Technical Debt in Microservices: A Case Study in a Large Company, In Paris Avgeriou & Klaus Schmid (ed.), Proceedings of the Second International Conference on Technical Debt. IEEE Press. ISBN 978-1-7281-3371-3. kapittel. Show summary
Introduction: Software companies aim to achieve continuous delivery to constantly provide value to their customers. A popular strategy is to use microservices architecture. However, such an architecture is also subject to debt, which hinders the continuous delivery process and thus negatively affects the software released to the customers. Objectives: The aim of this study is to identify issues, solutions and risks related to Architecture Technical Debt in microservices. Method: We conducted an exploratory case study of a real life project with about 1000 services in a large, international company. Through qualitative analysis of documents and interviews, we investigated Architecture Technical Debt in the communication layer of a system with microservices architecture. Results: Our main contributions are a list of Architecture Technical Debt issues specific for the communication layer in a system with microservices architecture, as well as their associated negative impact (interest), a solution to repay the debt and the its cost (principal). Among the found Architecture Technical Debt issues were the existence of business logic in the communication layer and a high amount of point-to-point connections between services. The studied solution consists of the implementation of different canonical models specific to different domains, the removal of business logic from the communication layer, and migration from services to use the communication layer correctly. We also contributed with a list of possible risks that can affect the payment of the debt, as lack of funding and inadequate prioritization. Conclusion: We found issues, solutions and possible risks that are specific for microservices architectures not yet encountered in the current literature. Our results may be useful for practitioners that want to avoid or repay Technical Debt in their microservices architecture.

View all works in Cristin

Published Aug. 27, 2018 11:22 AM - Last modified Feb. 9, 2019 9:06 PM