nitric VS Pulumi

For all those on the hunt for a framework, Nitric is here for you. It's a multi-language framework that helps teams quickly build cloud applications. Nitric unites backend and infrastructure code and automates the process of provisioning and deploying infrastructure. The first major version brings a bunch of changes including significant improvements to the Nitric CLI to support productive cloud development. There's also new architecture visualizations and a new SDK for building and extending Nitric providers. Congrats to the team on shipping your very first version 🥳.

Compare the following diagram to the one shown above. This flow addresses some of the concerns raised previously by using an automation framework to eliminate some of the assets that were originally manually crafted. We’re using our open source Nitric Framework in this example; other tools can be used to automate pieces of this flow as well.

For those interested in exploring this approach further, consider exploring Nitric.

In this exploration, we created a Profile Management API using Nitric, handled core profile operations, and extended it for image management.

On the server-side, you will typically use Zod validation in your route handlers, immediately after receiving a request. Here's an example using the Nitric framework:

Nitric is a serverless framework for rapidly developing and deploying cloud applications.

Nitric

I've been working on a framework to help with these exact sorts of applications. Internally it uses pulumi for deployments. The docs are all for Node.js currently, but we're actively adding other languages too. https://nitric.io

Nitric allows developers to build serverless functions that run on various compute services from multiple cloud vendors. One of the most commonly used is AWS Lambda. One of AWS Lambda's strengths - dynamic scaling - can also be a challenging drawback due to a phenomenon known as Cold Starts.

If you are following this blog series, you should already know the benefits of using Terraform to define and deploy your AWS resources and configuration. Other IaC solutions such as AWS CloudFormation, AWS CDK, and Pulumi work the same way but differs in the programming or configuration language.

Infrastructure as Code (IaC) is an important part of any true hosting operation in the public cloud. Each of these platforms has their own IaC solution, e.g. AWS CloudFormation. But they also support popular open-source IaC tools like Pulumi or Terraform. A category of tools that also needs to be discussed is API gateways and other app-specific load balancers. There are applications for internal consumption, which can be called microservices if you have a lot of them. And often microservices use advanced networking options such as a service mesh instead of just the native private network offered by a VPC.

Pulumi — Modern infrastructure as a code platform that allows you to use familiar programming languages and tools to build, deploy, and manage cloud infrastructure.

Another alternative to writing an operator would be to rely on kustomize or https://www.pulumi.com/.

Pulumi

Would it make sense to say Dagger is to Pulumi [1], as Terraform is to Togomak?

[1]: https://www.pulumi.com/

Infrastructure as Code (IaC): Define your infrastructure using code (IaC) to automate the provisioning of resources such as virtual machines, load balancers, and databases. Tools like Terraform, Pulumi, and AWS CloudFormation can help.

This example uses Pulumi which allows you to write the IaC in Python.

What are your opinions on the decision to the change to BSL? Will you move to use the cloud service, keep using current version, the open source fork, switch to pulumi or bicep?