Infrastructure as Code (IaC): Part 3 of the blog series
Choosing the right approach for Terraform modules in Azure
In the third part of our blog series, we look at choosing the right approach for Terraform modules in Azure. We will look at different options, including custom modules, pre-built modules and third-party modules - and discuss the pros and cons of each. Because here too, not one size fits all!
User-defined modules:
Custom modules offer the greatest flexibility and adaptability. They allow you to precisely address specific requirements and use cases and adapt them to your way of working.
Advantages:
- Adaptability: modules that are perfectly tailored to your specific needs.
- Control: Full control over the code, standards and security requirements.
Considerations:
- Maintenance effort: User-defined modules must be regularly maintained and updated.
- Complexity: The development of custom modules can be complex and requires in-depth knowledge of Terraform and the Azure environment.
Design and maintenance of user-defined modules:
If you follow certain rules from the outset when creating modules, this makes both continuous use and maintenance easier. The following points will help you to keep your technical debt low:
- Modular structure: Divide your infrastructure into logically connected units. These units could each be represented by a module.
- Reusability: Make sure that your modules can be reused in different projects and environments.
- Documentation: Document your modules in detail to make them easier to use and maintain.
- Versioning: Use version control systems to track and control changes.
Prefabricated modules:
Microsoft offers a large number of ready-made Terraform modules that have been specially developed for Azure. These modules are well documented and are supported and regularly maintained by Microsoft, which makes their use attractive in many scenarios.
When and why should you use out-of-the-box modules?
- Quick start: Particularly useful if you want to get started quickly with proven best practices.
- Reduced maintenance effort: As these modules are maintained by Microsoft, a large part of the maintenance effort is eliminated.
- Security and compliance: Pre-built modules often meet Microsoft's security and compliance standards.
Use of third-party modules:
In addition to Microsoft, both the community and other companies offer modules.
These can be a valuable resource if they are well documented and maintained. As clever AG, we have our own battle-hardened module catalog, which has been developed and refined through a variety of different projects.
Advantages:
- Variety: A wide range of modules is available to cover different applications.
- Time saving: You can build on modules that have already been developed and tested.
Considerations:
- Trustworthiness: It can be difficult to guarantee the quality and security of third-party modules.
- Dependencies: They are dependent on maintenance and updating by third parties, which can lead to delays and problems.
Our conclusion
Choosing the right approach for Terraform modules depends on your specific requirements, resources and goals. Custom modules offer maximum flexibility, while pre-built and third-party modules can save time and effort.
Most of our customers therefore start with our module catalog for quick results, which we adapt and expand during the project so that it meets the customer's individual requirements.
In the next and final installment of our blog series, we will discuss best practices for integrating Terraform into CI/CD pipelines to ensure seamless and automated deployment.
Blog post author
Mirko is a Cloud Solutions Architect at celver and supports customers both in their transition to the cloud and in the optimization of existing environments. His job is to understand the needs and requirements of customers, translate these into architectural concepts and implement them. He mainly uses the Terraform framework to ensure a consistent and professional platform.
Case Study on the topic
More blog posts
