Introducing OpenTransit: A Free, Open-Source Fork of MassTransit v8

Sharifuzzaman Nakib — Fri, 05 Dec 2025 14:25:06 +0000

MassTransit has been the most trusted and most popular messaging framework in the .NET world for years. But with MassTransit v9 moving to a commercial model, many developers suddenly face uncertainty about the future of open, community-friendly messaging infrastructure.

OpenTransit is our answer to that shift: a fully open-source, community-led **fork of MassTransit v8 — built to keep the ecosystem **free, stable, and moving forward.

Supported .NET Versions?

OpenTransit will target .NET 10 and above. For most MassTransit v8 users, this shouldn’t create any friction — nearly all of them are already on .NET 5 or later, so moving forward will be straightforward.

For Current MassTransit V8 Users

MassTransit v8 will remain supported until the end of 2026, so there’s no pressure to make any immediate decisions. Keep using v8 confidently.

In the meantime, we’re actively working on OpenTransit — digging deep into the codebase, documenting everything properly, and laying the groundwork for a smooth transition. The documentation has already begun, and you can start exploring it now from here.

When MassTransit v8 reaches the end of support, we’ll release the first production-ready version of OpenTransit.

You may stay connected with us on Discord. Your feedback and suggestions during this phase will help shape the framework’s future.

Last but not the least:

Please share this project with your teammates and other .NET developers. The more voices we hear, the stronger OpenTransit becomes.

Using HTTPS on Next.js local development server

Sharifuzzaman Nakib — Wed, 03 Mar 2021 12:04:14 +0000

In today's world, HTTPS is everywhere.
So we should keep our development environment the same as the production environment. Because some things may not work in HTTP but work in HTTPS and vice versa.

The Next.js development server runs on HTTP by default. In this post, we will discuss how to run the Next.js development server on HTTPS.

Prerequisite:

First, we need to get an SSL certificate. Mkcert is the recommended option here which is simpler than the alternatives.
mkcert will create a CA and SSL Certificate for the servers for us. We will explain later how they work.

So first we need to install mkcert.

After installing, we will generate a CA i.e Certificate Authority first.
mkcert -install will do this.

Then, we have to generate a certificate for specific servers.
let we want to generate a certificate for localhost since most of the time we use this as a server.
Here, mkcert localhost will do this.
This will generate a certificate and a key named as *.pem and *-key.pem respectively.

The CA and Certificate(with the key)

The client( Browser or tools like postman) uses the CA certificate to authenticate the CA signature on the server certificate, as part of the authorizations before launching a secure connection. [Courtesy: Wikipedia]

So on next.js, we will create a custom server with the certificate( *.pem ) and key( *-key.pem ). This server will run on HTTPS!.
We have explained how to create the server with code in the next section.

The client such as Browser(Chrome, Firefox) or tools like Postman will use the CA to verify the Certificate of the server. The CA's are stored on Browser's trusted root store. Fortunately, we may not need to add the CA to the trusted root store for Chrome or Firefox. The mkcert does this. We just need to restart the browser. If for some reason it doesn't work then we need to add the certificate to the trusted root store manually. Hope we don't need this extra task :) :)

But in case we need to add the CA file manually to a browser or tool, first, we need to locate the CA file.
This can be done by mkcert -CAROOT command.
It will show the directory location where the CA is stored. There will be a certificate with a key. This key shouldn't be shared with others. The directory may be hidden. In that case, we may need to copy the files to another directory so that browser or other tools can locate the files.

To add the CA on postman you only need to add the certificate, not the key. See it here

Creating the Next.js Custom Server(which runs on HTTPS!)

First copy the certificate( *.pem ) and key( *-key.pem ) to a directory on the next.js project. Let the directory is on the project root and named as https_cert.

Now create a file named server.js on the project root and paste the following configuration. Don't forget to change the certificate and key name according to your certificate and key on httpsOptions.


const { createServer } = require("https");
const { parse } = require("url");
const next = require("next");
const fs = require("fs");
const port = 3000;
const dev = process.env.NODE_ENV !== "production";
const app = next({ dev });
const handle = app.getRequestHandler();

const httpsOptions = {
    key: fs.readFileSync("./https_cert/localhost+1-key.pem"),
    cert: fs.readFileSync("./https_cert/localhost+1.pem")
};

app.prepare().then(() => {
    createServer(httpsOptions, (req, res) => {
        const parsedUrl = parse(req.url, true);
        handle(req, res, parsedUrl);
    }).listen(port, (err) => {
        if (err) throw err;
        console.log("ready - started server on url: https://localhost:" + port);
    });
});

Now on the terminal, run node server.js.
This will start a server on https://localhost:3000.

If there are API routes, then these will be available on https://localhost:3000/api/*.

DEV Community: Sharifuzzaman Nakib