News for hackers. Stuff that matters.

A comment on Court rules against Oracle in Pentagon 'war cloud' litigation. Parent comment

Re:Court rules against Oracle in Pentagon 'war cloud' litiga... by mrep on Friday July 12, 2019 @06:15PM (#20425009)
Sure you can probably port your code over just fine, but it's going to take 3 years for another cloud provider to build an entire airgapped datacenter and launch each internal service in it. Considering the CIAs 600 million dollar contract got an entire one dedicated for them, I wouldn't be surprised if this contract which goes up to 10 billion dollars ended up involving multiple new regions. As I said, another cloud provider won't be able to simply just take over those datacenters and install their software, they'll probably have to build their own airgapped datacenters which will take years.

So no, there is no way it's going to be easy for them to port over to another cloud provider.

[ Parent | on HN ]
Re:Court rules against Oracle in Pentagon 'war cloud' litiga... by toomuchtodo on Friday July 12, 2019 @10:02PM (#20426065)
If the DoD makes it a requirement that a new service provider can take ownership of the physical facility and it’s contents, a new provider could most certainly assume responsibility for the cloud system. It’s a contractual issue, not a technical issue, no different than China requiring AWS’ China data center region be operated by a Chinese company versus AWS proper.
[ Parent | on HN ]
Re:Court rules against Oracle in Pentagon 'war cloud' litiga... by mrep on Friday July 12, 2019 @11:27PM (#20426318)
I've worked for multiple major cloud providers and I assure you that launching the dependency chain to get most cloud services in production for 1 region takes 6 months minimum (they have entire teams dedicated to launching regions). That is after building the datacenter (years) and launching the main database services (which require custom server hardware as I previously mentioned) that power most of the main cloud services.

Google uses spanner, AWS uses dynamodb, and Azure uses Cosmodb which are all different database systems and thus they are all completely incompatible.

[ Parent | on HN ]