Pulumi vs. Wing [Main differences]
Wing is a general purpose programming language, designed to develop entire cloud applications - including their infrastructure and application code. Pulumi is an infrastructure as code tool that focuses on the infrastructure part of the application. You then need a way to stitch together that infrastructure and the application code. The main differences between them are:
- Wing code is cloud-portable, so you can write the code once and then compile to any cloud. Pulumi is not cloud-portable. Although it supports all clouds, you need to write specific code for each one.
- Since the Wing compiler sees both the infra and application code, it can automatically generate much of the infrastructure definitions that you have to manually define in Pulumi (IAM policies, network topologies, etc).
- You will be able to compile Wing to Javascript and Pulumi in the future (roadmap is here). You will be able to use our compiler plugins to customize the Pulumi output directly.
- Wing provides local simulation and visualization tools that let you develop locally with instant hot reloading. With Pulumi, you must deploy to the cloud in order to interact with your application, which can take several minutes.
Code samples
To get a deeper understanding of the differences, let's see the same app built in both Wing and Pulumi. This simple cloud app uses a Function to upload a text file to a Bucket,
import CodeComparison from '../../src/components/CodeComparison';
The below table contains the main differences that you can see in the code examples, and also some that cannot fit in such a small app, but we still would like you to know about :)
| Feature | Wing | Pulumi |
|---|---|---|
| Language | Wing | YAML + your choice |
| Line of code | 7 | 98 |
| Cloud Mechanics (IAM, Networking) | Generated automatically from intent | Manual |
| Extensibility | Custom resources | Custom/dynamic providers |
| Customizing lower levels | Compiler plugins to customize generated Terraform | Direct access to cloud-provider APIs |
| Local simulation | Built-in functional local simulator with instant hot reloading | No |
| Cross-cloud support | Same code compiles to different clouds | No (need to write different code for different clouds) |
| Provisioning engine | Same code compiles to Terraform and AWS-CDK (CloudFormation) | Proprietary |
| Testing | Same tests run on local simulator and cloud, without mocks | Need mocks for local testing |
You can get a sense of the development experience with Wing in our playground.