ASSA ABLOY Leverages Docker to Fuel Digital Transformation


ASSA ABLOY is the world’s largest lock manufacturer with 47,000 employees worldwide and well-known brands like Yale, Sargent and Assa in their portfolio. The vision for ASSA ABLOY is to become the most innovative provider of door opening solutions through growth of electro-mechanical and digital entry solutions. With increasingly global operations to deal with as well, ASSA ABLOY recognized the opportunity to leverage public cloud, microservices and containers to fuel this digital transformation.


Some developers at ASSA ABLOY started using Docker for microservice development back in 2014, but it was uncoordinated with manual, scripted deployments of containers onto individual servers, inconsistent practices, no separation between teams, and without any image standards. Additionally, ASSA ABLOY was concerned about cloud lock-in. They chose Docker EE which gave them a centralized container management platform with orchestration and a secure, private registry solution that would also be portable to different clouds and infrastructure platforms.


Today, ASSA ABLOY has Docker EE deployed in the cloud with the plan to extend across multiple regions, supporting multiple development teams. They are fully leveraging Docker Trusted Registry capabilities and have noticed these key improvements:
  • Secure Software Supply Chain: Prior to Docker EE, different teams could view, edit, and even delete other teams’ images. Now, they are isolated from one another with clear role-based permissions, and they are starting to use digital signing to validate ownership of images.
  • Seamless Dev to Ops Workflows: With the implementation of Docker EE, ASSA ABLOY is now enforcing the app progression from dev to test to pre-production to production with developers having more flexibility in dev and test and being more limited in their access to pre-production and production environments. Along with separate repositories that limit code changes in pre-production and production, this separation of roles and responsibilities also allows the infrastructure team to be responsible for things like network security and approved image layers.
  • Standardized Image Management: Adopting Docker EE drove a more disciplined approach to naming and labeling images and containers. These standardized practices are being used across different teams which enables administrators and operators to have a much easier time identifying and tracking applications. With garbage collection, they can also manage the fast-growing image library.