Waste-Management Platform Architecture Restructuring

Problem

A B2B marketplace for waste logistics had grown over time and was getting slow to change. The platform needed a clearer structure, a team that knew who owned what, and a release process that took less effort.

Approach

• I reviewed the existing platform and worked with the development lead on how to restructure it.
• I refactored the architecture to make the platform faster and easier to develop.
• I looked at whether the platform should be split into services or stay as one system, and wrote down the reasons for each decision.
• I led architecture reviews and set coding standards for the whole team.
• I took over the team that worked on new features and maintenance, and I gave each person the work they fit best.
• I presented architecture proposals to the CTO and to enterprise clients.
• I looked at Google Cloud as a hosting option for the company.

Architecture and design decisions

• I defined the boundaries between the parts of the platform.
• I compared a microservices setup with a single system before choosing a direction.
• I wrote every major decision down as an architecture decision record, so the reasons stay readable for people who join later.

Reliability and performance

• I automated release scheduling and deployment for the release that went out every two weeks.
• I added automated code checks with about 300 rules, so code from every developer followed the same standards.

Outcomes

• Active preparation and execution time for each release went down by 40%.
• The platform became faster and easier to develop on after the restructuring.
• I led a team of 5 developers.
• The whole codebase followed one set of checked coding standards.
• New developers had written onboarding documentation to start from.

Known gaps

• This page does not describe the internal design of the platform or the services it was split into.
• I do not have measured numbers for the performance gain or for how much faster development became.
• The page does not say what the final choice between microservices and one system was, or what came out of the Google Cloud review.
• The 40% figure covers active release work only. It does not cover total release time.