Choosing between
locations.
The right deployment location can improve latency, keep users closer to your services and give you more flexibility as your infrastructure grows.
The short answer.
For most workloads, start with the location that gives your main users or critical systems the shortest practical network path. That often improves latency and responsiveness.
As your infrastructure grows, using more than one location can help you serve different regions and reduce dependence on a single site — but only when the application, data and failover design are built to use those locations correctly.
Lower latency
Keeping workloads closer to users can reduce network round-trip time and improve responsiveness.
Regional flexibility
Different locations let you place infrastructure nearer to customers, partners or internal systems.
Better resilience
Multiple locations can reduce location-level risk when the application and data architecture are designed for redundancy.
What changes with location?
Location affects network latency, user proximity, operational complexity and how you design resilience. The best choice depends on where your users, data and dependent systems actually are.
| Factor | Single location | Closest practical location | Multiple locations |
|---|---|---|---|
Latency | Depends on where users and connected systems are located. | Usually provides the shortest path for the primary audience. | Can provide low latency to several regions when traffic is routed appropriately. |
User proximity | Best suited to one main geographic audience. | Keeps the main user base near the workload. | Lets separate regions use infrastructure closer to them. |
Data location | Keeps application data concentrated in one location. | Can help meet architectural or organisational location requirements. | Requires clear decisions about where data is stored, replicated and processed. |
Resilience | Location-level redundancy is limited. | Does not by itself provide geographic redundancy. | Can support geographic resilience when replication, health checks and failover are correctly designed. |
Operations | Simplest to operate. | Usually straightforward for a single-region workload. | Adds coordination, monitoring, replication and recovery complexity. |
Best fit | Small or geographically concentrated workloads. | Most common starting point. | Multi-region services, growth plans or workloads requiring stronger location-level resilience. |
When to choose which setup.
Different projects have different needs. These common scenarios help you choose a practical starting point.
Closest to your users
Choose the available location with the best network proximity to your main audience when responsiveness is the primary goal.
Close to your business systems
Place infrastructure near databases, APIs, partner services or internal systems when those connections matter more than end-user distance.
Multi-location for growth
Add locations when you need to serve multiple regions or reduce reliance on a single site and your application is ready for multi-location operation.
Separate locations for resilience
Keep suitable secondary systems or recovery copies in another location when your recovery design requires protection from a location-level incident.
Why different locations matter.
Using the right location — or a carefully designed combination of locations — can improve user experience, make regional expansion easier and give you more options when planning recovery and resilience.
Better user experience
Lower network latency can make websites, applications and APIs feel more responsive.
Flexibility for more regions
Additional locations make it easier to place services closer to new markets as your customer base grows.
Cleaner growth path
You can add locations gradually instead of redesigning your infrastructure around one permanent geographic choice.
Smarter disaster planning
Separating suitable recovery systems or backups from the primary location can reduce the impact of a location-level failure.
Frequently asked questions.
Quick answers to common questions about choosing and using BALX locations.
Visit our support centreStart where you are.
Scale when you’re ready.
Choose the level of performance, isolation and control your workload needs today.