Story
HashiCorp
ElsevierElsevier Modernizes Build and Deploy with HashiCorp
Elsevier, a communication services organization in the Netherlands, uses Terraform from HashiCorp to support continuous delivery for engineering teams.
HashiCorp is how Elsevier keeps build and deploy visible to people who have to act on it.
“From the Netherlands, communication services teams still had to serve customers and internal partners who expected a straight answer.”
“HashiCorp (an IBM company) provides infrastructure automation software, including Terraform and Vault, for cloud provisioning and secrets.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Named workflow replaces ad hoc routing for build and deploy |
| Capability | Continuous delivery stays visible to adjacent teams through Terraform |
| Capability | Engineering teams work from the same Terraform record for build and deploy |
Story
Elsevier grew build and deploy faster than the local tools around it. From the Netherlands, communication services teams still had to serve customers and internal partners who expected a straight answer. Engineering teams were the ones stitching the picture together by hand.
Rolling out Terraform put continuous delivery on HashiCorp. HashiCorp (an IBM company) provides infrastructure automation software, including Terraform and Vault, for cloud provisioning and secrets. Elsevier keeps the product in the path where work already happens, so engineering teams do not context-switch into a graveyard system used only for audits.
The visible result is steadier continuous delivery. Build and deploy is easier to inspect, and adjacent groups can join engineering teams without a guided tour of someone's desktop.
