Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Comparing Pulumi and Terraform: Imperative Language vs. Declaritive Language
Names and KTH ID
Deadline
Category
Description
This presentation will focus on comparing Pulumi and Terraform, two prominent Infrastructure as Code (IaC) tools, with a specific emphasis on language support and its effects on infrastructure management. Pulumi’s use of general-purpose programming languages (e.g., JavaScript, Python, Go) versus Terraform’s use of HashiCorp Configuration Language (HCL) introduces distinct advantages and challenges. The analysis will highlight which tool is better suited for various use cases depending on developer expertise and project complexity.
Relevance
Language support significantly impacts the ease and flexibility of infrastructure management. Pulumi allows developers to use familiar languages, potentially improving productivity and collaboration across teams, while Terraform's declarative approach offers simplicity and focus on infrastructure logic. Understanding the impact of these differences is essential for making informed decisions about which tool to adopt based on project needs and team capabilities.