diff --git a/content/en/case-studies/newyorktimes.html b/content/en/case-studies/newyorktimes.html index 1236bdd269..c65b5fe883 100644 --- a/content/en/case-studies/newyorktimes.html +++ b/content/en/case-studies/newyorktimes.html @@ -5,15 +5,14 @@ cid: caseStudies css: /css/style_case_studies.css --- -
-

CASE STUDY:
The New York Times: From Print to the Web to Cloud Native - +
+

CASE STUDY:
The New York Times: From Print to the Web to Cloud Native

-
+
Company  New York Times     Location  New York, N.Y.      Industry  News Media
@@ -25,7 +24,7 @@ css: /css/style_case_studies.css

Challenge

When the company decided a few years ago to move out of its data centers, its first deployments on the public cloud were smaller, less critical applications managed on virtual machines. "We started building more and more tools, and at some point we realized that we were doing a disservice by treating Amazon as another data center," says Deep Kapadia, Executive Director, Engineering at The New York Times. Kapadia was tapped to lead a Delivery Engineering Team that would "design for the abstractions that cloud providers offer us." -
+

Solution

The team decided to use Google Cloud Platform and its Kubernetes-as-a-service offering, GKE.
@@ -40,14 +39,20 @@ css: /css/style_case_studies.css
-
-
- - -
-
- "I think once you get over the initial hump, things get a lot easier and actually a lot faster." — Deep Kapadia, Executive Director, Engineering at The New York Times
+
+
+
+ +
+
+
+

+
+
+
+ "I think once you get over the initial hump, things get a lot easier and actually a lot faster." — Deep Kapadia, Executive Director, Engineering at The New York Times
+