According to Technology Director Jean Pierre Lessa e Santos Ferreira, international data transfers are often treated as an exclusively legal matter, resolved through a contract or compliance clause. In practice, much of this requirement directly affects system architecture: where data is stored, how it travels, and which technical components need to be redesigned to comply with these restrictions.
Understanding these issues before designing a system helps avoid costly rework later, when the architecture is already in production and a regulatory requirement forces data to be moved even though it should never have left the appropriate location in the first place.
Why Has This Become an Architectural Issue, Not Just a Legal One?
A contractual clause may state that data from one country must not be processed in another, but it is the system that ensures this requirement is actually followed. If an application automatically replicates data across regions to improve performance without taking this restriction into account, the legal requirement is technically violated, even if the contract is correct on paper.
Jean Pierre Lessa e Santos Ferreira notes that this is one of the most common pitfalls: treating the requirement as solely the responsibility of the legal team, without involving those who design the infrastructure, results in systems that violate the rules without anyone realizing it until a formal audit takes place.
Which Data Requires Special Attention When Crossing Borders?
Not all data is subject to the same requirements. Sensitive personal data, such as health or financial information, is often subject to stricter data localization requirements than internal operational data, such as system performance metrics.
Jean Pierre Lessa e Santos Ferreira emphasizes that mapping these differences early in the system design process helps prevent a common mistake: applying the same strict rule to every type of data. This can unnecessarily increase costs and constrain the architecture when only a specific portion of the data actually requires such restrictions.
How Does the Architecture Change When Data Must Remain in a Specific Country?
When data residency requirements apply, the architecture must take into account where each database is physically hosted, rather than simply which cloud provider has been contracted. This may mean maintaining separate regional replicas instead of a single global database that is automatically synchronized.
Jean Pierre Lessa e Santos Ferreira considers this regional segmentation generally more expensive and complex to maintain than a centralized architecture. For this reason, it should be implemented only where the requirement actually exists, rather than adopted as a default approach for the entire system.
What Happens When a Cloud Provider Processes Data Outside the Country Without the Team Realizing It?
A cloud provider may temporarily process data in a different region than expected, for example during an automatic failover, without this being immediately obvious to the team that configured the system. This type of unnoticed data movement is one of the most common causes of unintentional non-compliance.
Jean Pierre Lessa e Santos Ferreira stresses that carefully reviewing exactly where each contracted service processes and stores data, including backups and disaster recovery replicas, is just as important as reviewing where the primary data is hosted.
How Do You Decide Between Replicating Data by Region and Keeping Everything Centralized?
The answer depends on which requirement carries the most weight for the system: response speed for the end user, maintenance costs, or regulatory compliance. None of these three factors should be considered independently of the other two.
Jean Pierre Lessa e Santos Ferreira explains that the most robust decision comes from mapping, data by data, which restrictions actually apply and designing the architecture accordingly, rather than choosing either to centralize everything or replicate everything as a single rule for every system the company may build.
