If you ask Fran, I am the expert at building in the shadows... It is almost scary how good I am at doing it.
I keep trying to remind myself that for others to use it, they have to know that it exists!
But the reality is... I am building it for myself first and foremost, you come second. I know, how dare I put you there ;)
I am way to good at working in the shadows... Since our last update at v0.39.0, the project has grown substantially. Spanning versions v0.40.0 through v0.62.1 and brings complete OpenAPI support, a powerful HTTP client support, and an MCP server for AI integration.
TLDR:
Building integrations with event-driven services requires managing connections alongside your messaging logic. In our previous post on protocol-specific messaging functions, we explored how to generate low-level channel functions for NATS, Kafka, and other protocols. Now let's see how The Codegen Project's client generator takes this a step further by providing a convenient wrapper around those channel functions that handles connection management and exposes all relevant models like parameters and headers.
Building scalable event-driven applications requires robust messaging infrastructure that works seamlessly with your chosen protocols. We've covered payload generation, header management, and type-safe routing. Now let's explore how The Codegen Project's channels generator creates protocol-specific functions that streamline your messaging architecture while working with your favorite messaging systems.
Building event-driven applications often requires dynamic channel routing based on parameters like user IDs, tenant identifiers, or resource keys. Manually constructing these parameterized channels is error-prone and makes your code fragile. We've explored generating payload models, headers, and type-safe channels. Now let's see how The Codegen Project's parameters generator creates type-safe models for dynamic channel construction.
Building event-driven applications with multiple channels often leads to a common but critical problem: hardcoded channel names scattered throughout your codebase. One typo in a channel name can send events to the wrong destination or create silent failures. We've already explored generating models for payloads and headers. Now let's see how The Codegen Project's types generator provides compile-time safety for all your channel routing.
Building robust event-driven applications requires more than just payload validation - you need proper header management for authentication, tracing, routing, and metadata. In our previous post about payload generation, we showed how to generate type-safe data models. Now let's explore how The Codegen Project's headers generator can streamline your messaging infrastructure by handling the metadata side of your messages.
Building event-driven applications often means spending countless hours writing and maintaining payload models. What if you could generate these models automatically from your AsyncAPI specification while keeping full control over your infrastructure code? In this post, we'll explore how The Codegen Project's payload generator can save you time and reduce errors.
Since the release of v0.33, we've been diligently enhancing the Codegen CLI to make generated code safer, more intuitive, and aligned with real-world development practices. Spanning versions v0.34.0 through v0.39.0, this update introduces significant improvements, including automatic payload validation enabled by default and unified parameters.
TLDR:
The Codegen Project provides several ways to customize the generated code output through AsyncAPI extensions. In this post, we'll explore the available customization options and how to use them effectively.