---
title: "Discussion on \"Why I Built a Feature Module Engine — and Why Feature Flag Libraries Weren't Enough\" | Hashnode"
description: "Discussion on \"Why I Built a Feature Module Engine — and Why Feature Flag Libraries Weren't Enough\". A feature flag library tells you whether a feature is on or off. A feature module engine tells you what to do about it."
url: "https://hashnode.com/posts/why-i-built-a-feature-module-engine-and-why-feature-flag-libraries-weren-t-enough/6a557ceac653493c12c139f1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why I Built a Feature Module Engine — and Why Feature Flag Libraries Weren't Enough](https://powercsharp.hashnode.dev/why-i-built-a-feature-module-engine-and-why-feature-flag-libraries-weren-t-enough?utm_source=hashnode&utm_medium=feed)

A feature flag library tells you whether a feature is on or off. A feature module engine tells you what to do about it.

Jul 14 · 7 min read · powercsharp.hashnode.dev  
Read the article

-   [#csharp](https://hashnode.com/tag/csharp)
-   [#dotnet](https://hashnode.com/tag/dotnet)
-   [#dotnetcore](https://hashnode.com/tag/dotnetcore)
-   [#architecture](https://hashnode.com/tag/architecture)
-   [#software-architecture](https://hashnode.com/tag/software-architecture)
-   [#design-patterns](https://hashnode.com/tag/design-patterns)
-   [#feature-flags](https://hashnode.com/tag/feature-flags)

## Written by

[Mario Alberto Arce](https://hashnode.com/@marioarce)

@marioarce · San José, Costa Rica

  
[View profile](https://hashnode.com/@marioarce)

AWS Cloud Architect | Serverless & Event-Driven Systems | Enterprise Modernization (Monolith → Microservices) | .NET & API Architecture

## Responses

Markdown supported · ⌘↵ to post

No responses yet.