---
title: "Mario Alberto Arce (@marioarce) | Hashnode"
description: "AWS Cloud Architect | Serverless & Event-Driven Systems | Enterprise Modernization (Monolith → Microservices) | .NET & API Architecture"
url: "https://hashnode.com/@marioarce"
---

@marioarce

# Mario Alberto Arce

@marioarce · San José, Costa Rica · Joined June 2026

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

[Website](https://medium.com/@marioarce)

### [The Cache Family](https://powercsharp.hashnode.dev/the-cache-family?utm_source=hashnode&utm_medium=feed)

One \`ICacheService\` contract, two swappable backends — an in-memory LRU cache (BitFaster) and a disk-backed cache that survives process restarts — switchable through configuration, safe-off by default.

6 min read · [powercsharp.hashnode.dev](https://powercsharp.hashnode.dev/the-cache-family?utm_source=hashnode&utm_medium=feed)

[Sep 2](https://hashnode.com/posts/the-cache-family/6a98823e9be5334180c32743)

### [The Features Framework](https://powercsharp.hashnode.dev/the-features-framework?utm_source=hashnode&utm_medium=feed)

A feature flag library answers one question: is this feature enabled? It doesn't answer the question that actually matters in a real application: what happens to dependency injection when the feature is \*not\* enabled? That gap is where \`PowerCSharp.Features\` came from.

5 min read · [powercsharp.hashnode.dev](https://powercsharp.hashnode.dev/the-features-framework?utm_source=hashnode&utm_medium=feed)

[Aug 21](https://hashnode.com/posts/the-features-framework/6a87a0d81cd0e7f557095beb)

### [Foundation: Core, Extensions, Utilities, Helpers, Compatibility](https://powercsharp.hashnode.dev/foundation-core-extensions-utilities-helpers-compatibility?utm_source=hashnode&utm_medium=feed)

Twenty Years of the Same Five Bugs

7 min read · [powercsharp.hashnode.dev](https://powercsharp.hashnode.dev/foundation-core-extensions-utilities-helpers-compatibility?utm_source=hashnode&utm_medium=feed)

[Aug 18](https://hashnode.com/posts/foundation-core-extensions-utilities-helpers-compatibility/6a847a702accd035b96b92b1)

### [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.

7 min read · [powercsharp.hashnode.dev](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)

[Jul 14](https://hashnode.com/posts/why-i-built-a-feature-module-engine-and-why-feature-flag-libraries-weren-t-enough/6a557ceac653493c12c139f1)

### [100+ Extension Methods: When Breadth Is a Design Decision, Not a Mistake](https://powercsharp.hashnode.dev/100-extension-methods-when-breadth-is-a-design-decision-not-a-mistake?utm_source=hashnode&utm_medium=feed)

The danger of extension method libraries is not the methods — it's the lack of discipline. Here is how I designed 100+ methods that still have a coherent API surface.

5 min read · [powercsharp.hashnode.dev](https://powercsharp.hashnode.dev/100-extension-methods-when-breadth-is-a-design-decision-not-a-mistake?utm_source=hashnode&utm_medium=feed)

[Jul 3](https://hashnode.com/posts/100-extension-methods-when-breadth-is-a-design-decision-not-a-mistake/6a47d0b68f40d8f19021b3a3)