Software architecture and System Design
How a system is organised, scales and fails safely, decided before the first line of code. Systems Architect based in Toledo and Cascavel, working across Paraná, Brazil and abroad.
When you need an architect
When the system grew and became slow, expensive or fragile. When every new feature breaks another. When the company is about to build something that cannot fail: payments, health data, cooperative operations, a platform with many customers in the same database. Or when the team is good but never had someone deciding the structure before starting.
Architecture is not a pretty diagram. It is the list of decisions that cost the most to change later: where the boundaries between parts sit, who owns each piece of data, what happens when a service goes down, how the system serves ten customers and how it serves ten thousand.
What I deliver
An architecture review of what exists, with risks ordered by impact. The target architecture: domains, data, integrations, queues, caching, multi-tenancy, permissions, observability. Decision records (ADRs) so the team knows why each choice was made. A reversible, staged migration plan that does not stop operations. And review sessions with the team until everyone understands.
Topics I work on most
Distributed systems and data consistency; outbox patterns, idempotency and queues; multi-tenancy and RBAC; domain modelling and modular monoliths; capacity planning; graceful degradation and failure modes; migration strategy and reversibility. I write about each of them in the articles on this site.
For whom
Companies in Cascavel, Toledo, Foz do Iguaçu and across Paraná that operate critical systems; startups and SaaS anywhere in Brazil moving from first product to platform; engineering teams that want a senior architect for a few months without a full-time hire.
Frequently asked questions
What is System Design?
It is the discipline of designing how a system is organised to meet requirements of scale, reliability, security and cost: components, data, communication, failures. It is what decides whether a system can grow.
Do I need to rewrite my system to improve the architecture?
Almost never. Most systems improve in stages: separate one boundary, take one responsibility out of the database, put a queue where there was a synchronous call. Rewriting is the last option, and when it is the option, it is done in parts, with rollback possible.
Do you do architecture for PHP or legacy systems?
Yes. Architecture is about structure and boundaries, not language. Some of the best results I have had were in legacy systems that gained clear boundaries without changing technology.
How is it priced?
An architecture review has a fixed price and takes two to four weeks. Ongoing architecture support is by period, with a defined weekly dedication.
Let us talk
Describe the system, the problem and the deadline. I reply within one business day.
write to me contato@fgxdev.com