From my leadership experiences, working for different industries, I learned to get through more difficult moments. In #tech you need to plan wisely. You can set minimal viable architecture that supports the core business processes, and then can consider modular architecture that allows you to scale individual parts independently when needed: this will ensure future scalability in system architecture when facing budget constraints. Also, in the last few years, I learned to use cloud infrastructure and "as a service" platforms wisely. With that you can scale storage, computing power, and other resources dynamically, avoiding upfront costs, and adapting according to the need. Here it is key to have periodical reviews on your operational costs.

Design independently deployable and loosely coupled components with high functional cohesion. In software architecture books, this is defined as an "Architectural Quantum." As quanta get larger, scalability becomes more challenging and expensive. Monolithic architecture has very large quanta since the components are deployed as a single unit with a high level of coupling in the database. Modular monoliths or service-based architecture are a good next step if the budget is limited and will provide independently scalable modules or services. Meanwhile, microservices end up on the other end of the spectrum - small quanta, but introduces other complexities, like coordination overhead.

Anticiparse a los costos y reservar servicios (Savings Plans en caso de AWS). También evaluar arquitecturas serverless reducen costos iniciales y aseguran escalabilidad.