Back

Architecture philosophy

How I think about architecture

  1. Less customization, more platform

    Use native capabilities before building. Every custom adds ownership cost.

  2. Loose coupling

    VTEX shouldn't become the place where all business logic lives.

  3. Observability first

    An integration without metrics, logs and traceability isn't done.

  4. Performance as an architectural requirement

    Not a final polish: it shapes service boundaries, caching and storefront design.

  5. Decisions you can explain

    If you can't justify a trade-off to business and the team, it probably isn't ready.

Contact

Do you have a VTEX architecture that needs a review?

WhatsApp, LinkedIn or email.

I can help with:

  • Architecture review
  • Technical discovery
  • Migration strategy
  • Performance review
  • Technical leadership

Book a 30-min conversation

Buenos Aires, Argentina