Bay Area ColocationWhen Proximity to AWS Matters
By: Sean Tario
SUMMARY – A client had vetted and aligned a hybrid hardware/colo and elastic hosting (AWS) solution that could help. Although they were unsure of where to put their infrastructure for sub 2 millisecond AWS access to ensure further bottlenecks would be pushed out much further down the road. Open Spectrum paired them with: Bay Area datacenter provider with a robust and expansive local network that doesn’t charge an arm and a leg for power and space, provides a solid SLA, and is 1 millisecond away from other data stored on AWS’s infrastructure located in the Bay Area.
A scaling, well-funded Bay Area company seeking colocation with unique network requirements.
The client was hitting bottlenecks within the software, systems and database architecture originally designed to push a proof of concept out the door. Scaling rapidly, they scrambled, vetted and aligned a hybrid hardware/colo and elastic hosting solution (AWS) that appeared to help. They were unsure of where to put their physical infrastructure so they could access AWS sub 2 milliseconds to ensure further bottlenecks would get pushed out much further down the road. They were working with a tight deadline, and their hardware provider recommended Open Spectrum Inc, knowing that they would know exactly which data center, if any, could provide a viable solution.
A Bay Area data center provider with a robust and expansive local network provided:
- Single cabinet within a facility sitting only a few miles away from one of the regional AWS data centers, where it was determined the client data was hosted A cross connect from the data center directly to the AWS data center with latency minimized to sub 2 milliseconds
- Power and space at reasonable rates
- A flexible and client friendly MSA and SLA
Within a few hours, we had made calls to the network operations engineers at a hand full of local facilities we knew could be a fit to confirm the AWS Direct Connect product was available and exact latency between the facility and the specific AWS data center the client knew their data was hosted within. Within 3 days, all pricing and contracts had been worked through and contracts in hand.
Had the client tried to navigate this process on their own, it would have taken them weeks, at least, to narrow the list of viable facilities and weeks longer to try and speak with the right people at each provider who run and provide the specific latency test needed to ensure quality of service for their application.