"The big cloud native promise to our business is the ability to go from idea to production within 48 hours. We are some years away from this, but that’s quite feasible to us."
"We are always looking for ways to optimize and provide more value through technology. With Kubernetes we are showcasing two types of efficiency that we can bring: Dev efficiency and Ops efficiency. It’s a win-win."
+
+
+
diff --git a/content/en/case-studies/capital-one.html b/content/en/case-studies/capital-one.html
new file mode 100644
index 0000000000..ade270278d
--- /dev/null
+++ b/content/en/case-studies/capital-one.html
@@ -0,0 +1,96 @@
+---
+title: Capital One Case Study
+case_study_styles: true
+cid: caseStudies
+css: /css/style_case_studies.css
+---
+
+
+
CASE STUDY:
Supporting Fast Decisioning Applications with Kubernetes
+
+
+
+
+
+
+ Company Capital One Location McLean, Virginia Industry Retail banking
+
+
+
+
+
+
+
Challenge
+ The team set out to build a provisioning platform for Capital One applications deployed on AWS that use streaming, big-data decisioning, and machine learning. One of these applications handles millions of transactions a day; some deal with critical functions like fraud detection and credit decisioning. The key considerations: resilience and speed—as well as full rehydration of the cluster from base AMIs.
+
+
+
Solution
+ The decision to run Kubernetes "is very strategic for us," says John Swift, Senior Director Software Engineering. "We use Kubernetes as a substrate or an operating system, if you will. There’s a degree of affinity in our product development."
+
+
+
+
+
Impact
+ "Kubernetes is a significant productivity multiplier," says Lead Software Engineer Keith Gasser, adding that to run the platform without Kubernetes would "easily see our costs triple, quadruple what they are now for the amount of pure AWS expense." Time to market has been improved as well: "Now, a team can come to us and we can have them up and running with a basic decisioning app in a fortnight, which before would have taken a whole quarter, if not longer." Deployments increased by several orders of magnitude. Plus, the rehydration/cluster-rebuild process, which took a significant part of a day to do manually, now takes a couple hours with Kubernetes automation and declarative configuration.
+
+
+
+
+
+
+
+
+
+"With the scalability, the management, the coordination, Kubernetes really empowers us and gives us more time back than we had before." — Jamil Jadallah, Scrum Master
+
+
+
+
+
+
+ As a top 10 U.S. retail bank, Capital One has applications that handle millions of transactions a day. Big-data decisioning—for fraud detection, credit approvals and beyond—is core to the business. To support the teams that build applications with those functions for the bank, the cloud team led by Senior Director Software Engineering John Swift embraced Kubernetes for its provisioning platform. "Kubernetes and its entire ecosystem are very strategic for us," says Swift. "We use Kubernetes as a substrate or an operating system, if you will. There’s a degree of affinity in our product development."
+ Almost two years ago, the team embarked on this journey by first working with Docker. Then came Kubernetes. "We wanted to put streaming services into Kubernetes as one feature of the workloads for fast decisioning, and to be able to do batch alongside it," says Lead Software Engineer Keith Gasser. "Once the data is streamed and batched, there are so many tool sets in Flink that we use for decisioning. We want to provide the tools in the same ecosystem, in a consistent way, rather than have a large custom snowflake ecosystem where every tool needs its own custom deployment. Kubernetes gives us the ability to bring all of these together, so the richness of the open source and even the license community dealing with big data can be corralled."
+
+
+
+
+
+
+
+ "We want to provide the tools in the same ecosystem, in a consistent way, rather than have a large custom snowflake ecosystem where every tool needs its own custom deployment. Kubernetes gives us the ability to bring all of these together, so the richness of the open source and even the license community dealing with big data can be corralled."
+
+
+
+
+
+
+ In this first year, the impact has already been great. "Time to market is really huge for us," says Gasser. "Especially with fraud, you have to be very nimble in the way you respond to threats in the marketplace—being able to add and push new rules, detect new patterns of behavior, detect anomalies in account and transaction flows." With Kubernetes, "a team can come to us and we can have them up and running with a basic decisioning app in a fortnight, which before would have taken a whole quarter, if not longer. Kubernetes is a manifold productivity multiplier."
+ Teams now have the tools to be autonomous in their deployments, and as a result, deployments have increased by two orders of magnitude. "And that was with just seven dedicated resources, without needing a whole group sitting there watching everything," says Scrum Master Jamil Jadallah. "That’s a huge cost savings. With the scalability, the management, the coordination, Kubernetes really empowers us and gives us more time back than we had before."
+
+
+
+
+
+ With Kubernetes, "a team can come to us and we can have them up and running with a basic decisioning app in a fortnight, which before would have taken a whole quarter, if not longer. Kubernetes is a manifold productivity multiplier."
+
+
+
+
+
+ Kubernetes has also been a great time-saver for Capital One’s required period "rehydration" of clusters from base AMIs. To minimize the attack vulnerability profile for applications in the cloud, "Our entire clusters get rebuilt from scratch periodically, with new fresh instances and virtual server images that are patched with the latest and greatest security patches," says Gasser. This process used to take the better part of a day, and personnel, to do manually. It’s now a quick Kubernetes job.
+ Savings extend to both capital and operating expenses. "It takes very little to get into Kubernetes because it’s all open source," Gasser points out. "We went the DIY route for building our cluster, and we definitely like the flexibility of being able to embrace the latest from the community immediately without waiting for a downstream company to do it. There’s capex related to those licenses that we don’t have to pay for. Moreover, there’s capex savings for us from some of the proprietary software that we get to sunset in our particular domain. So that goes onto our ledger in a positive way as well." (Some of those open source technologies include Prometheus, Fluentd, gRPC, Istio, CNI, and Envoy.)
+
+
+
+
+
+ "If we had to do all of this without Kubernetes, on underlying cloud services, I could easily see our costs triple, quadruple what they are now for the amount of pure AWS expense. That doesn’t account for personnel to deploy and maintain all the additional infrastructure."
+
+
+
+
+ And on the opex side, Gasser says, the savings are high. "We run dozens of services, we have scores of pods, many daemon sets, and since we’re data-driven, we take advantage of EBS-backed volume claims for all of our stateful services. If we had to do all of this without Kubernetes, on underlying cloud services, I could easily see our costs triple, quadruple what they are now for the amount of pure AWS expense. That doesn’t account for personnel to deploy and maintain all the additional infrastructure."
+ The team is confident that the benefits will continue to multiply—without a steep learning curve for the engineers being exposed to the new technology. "As we onboard additional tenants in this ecosystem, I think the need for folks to understand Kubernetes may not necessarily go up. In fact, I think it goes down, and that’s good," says Gasser. "Because that really demonstrates the scalability of the technology. You start to reap the benefits, and they can concentrate on all the features they need to build for great decisioning in the business— fraud decisions, credit decisions—and not have to worry about, ‘Is my AWS server broken? Is my pod not running?’"
+
+
+
diff --git a/content/en/case-studies/ing.html b/content/en/case-studies/ing.html
new file mode 100644
index 0000000000..a395684807
--- /dev/null
+++ b/content/en/case-studies/ing.html
@@ -0,0 +1,94 @@
+---
+title: ING Case Study
+case_study_styles: true
+cid: caseStudies
+css: /css/style_case_studies.css
+---
+
+
+
+
CASE STUDY:
Driving Banking Innovation with Cloud Native
+
+
+
+
+
+ Company ING Location Amsterdam, Netherlands
+ Industry Finance
+
+
+
+
+
+
+
Challenge
+ After undergoing an agile transformation, ING realized it needed a standardized platform to support the work their developers were doing. "Our DevOps teams got empowered to be autonomous," says Infrastructure Architect Thijs Ebbers. "It has benefits; you get all kinds of ideas. But a lot of teams are going to devise the same wheel. Teams started tinkering with Docker, Docker Swarm, Kubernetes, Mesos. Well, it’s not really useful for a company to have one hundred wheels, instead of one good wheel.
+
+
+
Solution
+ Using Kubernetes for container orchestration and Docker for containerization, the ING team began building an internal public cloud for its CI/CD pipeline and green-field applications. The pipeline, which has been built on Mesos Marathon, will be migrated onto Kubernetes. The bank-account management app Yolt in the U.K. (and soon France and Italy) market already is live hosted on a Kubernetes framework. At least two greenfield projects currently on the Kubernetes framework will be going into production later this year. By the end of 2018, the company plans to have converted a number of APIs used in the banking customer experience to cloud native APIs and host these on the Kubernetes-based platform.
+
+
+
+
+
+
+
Impact
+ "Cloud native technologies are helping our speed, from getting an application to test to acceptance to production," says Infrastructure Architect Onno Van der Voort. "If you walk around ING now, you see all these DevOps teams, doing stand-ups, demoing. They try to get new functionality out there really fast. We held a hackathon for one of our existing components and basically converted it to cloud native within 2.5 days, though of course the tail takes more time before code is fully production ready."
+
+
+
+
+
+
+ "The big cloud native promise to our business is the ability to go from idea to production within 48 hours. We are some years away from this, but that’s quite feasible to us."
+ — Thijs Ebbers, Infrastructure Architect, ING
+
+
+
+
+
ING has long embraced innovation in banking, launching the internet-based ING Direct in 1997.
In that same spirit, the company underwent an agile transformation a few years ago. "Our DevOps teams got empowered to be autonomous," says Infrastructure Architect Thijs Ebbers. "It has benefits; you get all kinds of ideas. But a lot of teams are going to devise the same wheel. Teams started tinkering with Docker, Docker Swarm, Kubernetes, Mesos. Well, it’s not really useful for a company to have one hundred wheels, instead of one good wheel."
+ Looking to standardize the deployment process within the company’s strict security guidelines, the team looked at several solutions and found that in the past year, "Kubernetes won the container management framework wars," says Ebbers. "We decided to standardize ING on a Kubernetes framework." Everything is run on premise due to banking regulations, he adds, but "we will be building an internal public cloud. We are trying to get on par with what public clouds are doing. That’s one of the reasons we got Kubernetes."
+ They also embraced Docker to address a major pain point in ING’s CI/CD pipeline. Before containerization, "Every development team had to order a VM, and it was quite a heavy delivery model for them," says Infrastructure Architect Onno Van der Voort. "Another use case for containerization is when the application travels through the pipeline, they fire up Docker containers to do test work against the applications and after they’ve done the work, the containers get killed again."
+
+
+
+
+
+ "We decided to standardize ING on a Kubernetes framework." Everything is run on premise due to banking regulations, he adds, but "we will be building an internal public cloud. We are trying to get on par with what public clouds are doing. That’s one of the reasons we got Kubernetes."
+ — Thijs Ebbers, Infrastructure Architect, ING
+
+
+
+
+ Because of industry regulations, applications are only allowed to go through the pipeline, where compliance is enforced, rather than be deployed directly into a container. "We have to run the complete platform of services we need, many routing from different places," says Van der Voort. "We need this Kubernetes framework for deploying the containers, with all those components, monitoring, logging. It’s complex." For that reason, ING has chosen to start on the OpenShift Origin Kubernetes distribution.
+ Already, "cloud native technologies are helping our speed, from getting an application to test to acceptance to production," says Van der Voort. "If you walk around ING now, you see all these DevOps teams, doing stand-ups, demoing. They try to get new functionality out there really fast. We held a hackathon for one of our existing components and basically converted it to cloud native within 2.5 days, though of course the tail takes more time before code is fully production ready."
+ The pipeline, which has been built on Mesos Marathon, will be migrated onto Kubernetes. Some legacy applications are also being rewritten as cloud native in order to run on the framework. At least two smaller greenfield projects built on Kubernetes will go into production this year. By the end of 2018, the company plans to have converted a number of APIs used in the banking customer experience to cloud native APIs and host these on the Kubernetes-based platform.
+
+
+
+
+
+ "We have to run the complete platform of services we need, many routing from different places," says Van der Voort. "We need this Kubernetes framework for deploying the containers, with all those components, monitoring, logging. It’s complex."
+
+
+
+
+
+ The team, however, doesn’t see the bank’s back-end systems going onto the Kubernetes platform. "Our philosophy is it only makes sense to move things to cloud if they are cloud native," says Van der Voort. "If you have traditional architecture, build traditional patterns, it doesn’t hold any value to go to the cloud." Adds Cloud Platform Architect Alfonso Fernandez-Barandiaran: "ING has a strategy about where we will go, in order to improve our agility. So it’s not about how cool this technology is, it’s about finding the right technology and the right approach."
+ The Kubernetes framework will be hosting some greenfield projects that are high priority for ING: applications the company is developing in response to PSD2, the European Commission directive requiring more innovative online and mobile payments that went into effect at the beginning of 2018. For example, a bank-account management app called Yolt, serving the U.K. market (and soon France and Italy), was built on a Kubernetes platform and has gone into production. ING is also developing blockchain-enabled applications that will live on the Kubernetes platform. "We’ve been contacted by a lot of development teams that have ideas with what they want to do with containers," says Ebbers.
+
+
+
+
+
+Even with the particular requirements that come in banking, ING has managed to take a lead in technology and innovation. "Every time we have constraints, we look for maybe a better way that we can use this technology."
+
+
+
+ Even with the particular requirements that come in banking, ING has managed to take a lead in technology and innovation. "Every time we have constraints, we look for maybe a better way that we can use this technology," says Fernandez-Barandiaran.
+ The results, after all, are worth the effort. "The big cloud native promise to our business is the ability to go from idea to production within 48 hours," says Ebbers. "That would require all these projects to be mature. We are some years away from this, but that’s quite feasible to us."
+
+
+
+
diff --git a/static/css/case_study_styles.css b/static/css/case_study_styles.css
index c056d2c97e..2a604f7f18 100644
--- a/static/css/case_study_styles.css
+++ b/static/css/case_study_styles.css
@@ -767,7 +767,7 @@ hr { background-color: #999999; }
h2 { margin-bottom: 15px !important; }
-.subhead { padding-bottom: 2% !important; padding-top: 0% !important; }
+.subhead { padding-bottom: 2% !important; padding-top: 1% !important; }
.details { margin-left: 1.9%; padding-right: 5%; font-size: 16px !important; padding-bottom: 2% !important; }
diff --git a/static/css/style_case_studies.css b/static/css/style_case_studies.css
index f8a97f2bc8..815e1da7d2 100644
--- a/static/css/style_case_studies.css
+++ b/static/css/style_case_studies.css
@@ -35,7 +35,7 @@ h1 {
.subhead {
font-size:26px;
- font-weight:100;
+ font-weight:300;
line-height:40px;
padding-bottom:1%;
padding-top:0.5%;
diff --git a/static/css/styles.css b/static/css/styles.css
index 93cb323487..f18ef1b184 100644
--- a/static/css/styles.css
+++ b/static/css/styles.css
@@ -755,13 +755,13 @@ html.search #docsContent h1 { margin-bottom: 0; border-bottom: 0; padding-bottom
#home #caseStudiesWrapper div { position: relative; display: inline-block; vertical-align: top; width: 100%; min-height: 230px; padding: 125px 10px 15px; margin-bottom: 30px; background-position: top center; background-repeat: no-repeat; }
-#home #caseStudiesWrapper div:nth-child(1) { background-image: url(/images/community_logos/northwestern-mutual.png); }
+#home #caseStudiesWrapper div:nth-child(1) { background-image: url(/images/community_logos/capitalone.png); }
-#home #caseStudiesWrapper div:nth-child(2) { background-image: url(/images/community_logos/openai.png); }
+#home #caseStudiesWrapper div:nth-child(2) { background-image: url(/images/community_logos/ing.png); }
-#home #caseStudiesWrapper div:nth-child(3) { background-image: url(/images/community_logos/nyt.png); }
+#home #caseStudiesWrapper div:nth-child(3) { background-image: url(/images/community_logos/northwestern-mutual.png); }
-#home #caseStudiesWrapper div:nth-child(4) { background-image: url(/images/community_logos/nordstrom.png); }
+#home #caseStudiesWrapper div:nth-child(4) { background-image: url(/images/community_logos/openai.png); }
#home #caseStudiesWrapper p { font-size: 20px; }
diff --git a/static/images/CaseStudy_capitalone_banner1.jpg b/static/images/CaseStudy_capitalone_banner1.jpg
new file mode 100644
index 0000000000..6044f20d69
Binary files /dev/null and b/static/images/CaseStudy_capitalone_banner1.jpg differ
diff --git a/static/images/CaseStudy_capitalone_banner3.jpg b/static/images/CaseStudy_capitalone_banner3.jpg
new file mode 100644
index 0000000000..939dd3cd7e
Binary files /dev/null and b/static/images/CaseStudy_capitalone_banner3.jpg differ
diff --git a/static/images/CaseStudy_capitalone_banner4.jpg b/static/images/CaseStudy_capitalone_banner4.jpg
new file mode 100644
index 0000000000..cdff604b66
Binary files /dev/null and b/static/images/CaseStudy_capitalone_banner4.jpg differ
diff --git a/static/images/CaseStudy_ing_banner1.jpg b/static/images/CaseStudy_ing_banner1.jpg
new file mode 100644
index 0000000000..b5d4290b8f
Binary files /dev/null and b/static/images/CaseStudy_ing_banner1.jpg differ
diff --git a/static/images/CaseStudy_ing_banner3.jpg b/static/images/CaseStudy_ing_banner3.jpg
new file mode 100644
index 0000000000..6a344e6896
Binary files /dev/null and b/static/images/CaseStudy_ing_banner3.jpg differ
diff --git a/static/images/CaseStudy_ing_banner4.jpg b/static/images/CaseStudy_ing_banner4.jpg
new file mode 100644
index 0000000000..5ccbe56a7c
Binary files /dev/null and b/static/images/CaseStudy_ing_banner4.jpg differ
diff --git a/static/images/capitalone-logo.png b/static/images/capitalone-logo.png
new file mode 100644
index 0000000000..95dea65028
Binary files /dev/null and b/static/images/capitalone-logo.png differ
diff --git a/static/images/case_studies/capitalone_feature.png b/static/images/case_studies/capitalone_feature.png
new file mode 100644
index 0000000000..f57c7697e3
Binary files /dev/null and b/static/images/case_studies/capitalone_feature.png differ
diff --git a/static/images/case_studies/ing_feature.png b/static/images/case_studies/ing_feature.png
new file mode 100644
index 0000000000..f6d4489715
Binary files /dev/null and b/static/images/case_studies/ing_feature.png differ
diff --git a/static/images/case_studies/newyorktimes_feature.png b/static/images/case_studies/newyorktimes_feature.png
index 3aeb476072..693a742c3e 100644
Binary files a/static/images/case_studies/newyorktimes_feature.png and b/static/images/case_studies/newyorktimes_feature.png differ
diff --git a/static/images/case_studies/northwestern_feature.png b/static/images/case_studies/northwestern_feature.png
index d6ee500034..7c1422f32b 100644
Binary files a/static/images/case_studies/northwestern_feature.png and b/static/images/case_studies/northwestern_feature.png differ
diff --git a/static/images/case_studies/openai_feature.png b/static/images/case_studies/openai_feature.png
index b2b26521bb..b2b667c0bb 100644
Binary files a/static/images/case_studies/openai_feature.png and b/static/images/case_studies/openai_feature.png differ
diff --git a/static/images/community_logos/capitalone.png b/static/images/community_logos/capitalone.png
new file mode 100644
index 0000000000..845cebda56
Binary files /dev/null and b/static/images/community_logos/capitalone.png differ
diff --git a/static/images/community_logos/ing.png b/static/images/community_logos/ing.png
new file mode 100644
index 0000000000..8271efbf56
Binary files /dev/null and b/static/images/community_logos/ing.png differ
diff --git a/static/images/ing_logo.png b/static/images/ing_logo.png
new file mode 100644
index 0000000000..fc8560ecea
Binary files /dev/null and b/static/images/ing_logo.png differ
-
- 
+ 
+ 
- 
- 
