ManuHub.Memora.Client 1.0.1

Memora.Client

Memora.Client is a .NET library for interacting with a running Memora server. It provides a high-level API wrapper over the Memora protocol so you can use strongly-typed commands, handle responses cleanly, and integrate Memora into your applications with minimal boilerplate.

It complements the Memora CLI and Memora Server by giving developers a programmatic client for caching, key/value operations, and data structure commands.

⭐ Why Memora package?

Memora was created to solve a practical development issue: On Microsoft Windows, setting up a Redis-compatible environment often requires Docker, WSL, or external services. Many .NET developers prefer a lightweight native solution that runs directly on Windows.

Memora provides a simple alternative by shipping a native executable server and a .NET client library designed for development and lightweight deployments.

Key Idea

Memora runs as a local executable:

 memora-server.exe

So developers only need to:

1. Download the server

   Windows | Linux

2. Install / Run the server
3. Use the Client or CLI (memora-cli) - inside the bundle / zip

No Docker, WSL, or external infrastructure is required.

Ideal Use Cases

• Local development caching
• Integration testing
• Prototyping
• Small production workloads
• Offline development environments

Memora is not intended to replace large-scale Redis deployments, but to provide a simple, self-contained Redis-style environment for Windows-focused development.

Table of Contents

• Overview
• Installation
• Connecting to Memora
• Basic Commands
• List Operations
• Hash Operations
• Database Commands
• Error Handling
• ASP.NET Core Example
• CLI Usage
• Best Practices

Overview

Memora is designed for fast in-memory caching with a simple API:

• Key/Value storage
• List and hash operations
• TTL (time-to-live) for keys
• FlushDB / FlushAll commands
• Compatible with .NET async/await patterns

Components:

Installation

Install the client via NuGet:

dotnet add package ManuHub.Memora.Client --version 1.0.0

Or add as a project reference:

<ProjectReference Include="ManuHub.Memora.Client" Version="1.0.0" />

Connecting to Memora

Via Dependency Injection (ASP.NET Core)

using Memora.Client;

builder.Services.AddSingleton<IMemoraClient>(sp =>
    new MemoraClient(host: "127.0.0.1", port: 6380));

Direct Instantiation

using var client = new MemoraClient("127.0.0.1", 6380);

Basic Commands

List Operations

Hash Operations

Database Commands

Error Handling

All commands throw MemoraException on server errors:

try
{
    await client.SetAsync("key", "value");
}
catch (MemoraException ex)
{
    Console.WriteLine($"Memora error: {ex.Message}");
}

ASP.NET Core Example

[ApiController]
[Route("[controller]")]
public class CacheController : ControllerBase
{
    private readonly IMemoraClient _cache;

    public CacheController(IMemoraClient cache) => _cache = cache;

    [HttpGet("{key}")]
    public async Task<IActionResult> Get(string key)
    {
        var value = await _cache.GetAsync(key);
        return value is null ? NotFound() : Ok(value);
    }

    [HttpPost("{key}/{value}")]
    public async Task<IActionResult> Set(string key, string value)
    {
        bool success = await _cache.SetAsync(key, value);
        return success ? Ok() : StatusCode(500);
    }
}

CLI Usage

If using Memora.Cli:

memora-cli> set name Alice
memora-cli> get name
memora-cli> lpush users Alice Bob
memora-cli> hset user:1 name Alice age 25
memora-cli> hgetall user:1

Best Practices

1. Use singleton client per application.
2. Always use async methods.
3. Catch MemoraException for errors.
4. Use TTL for expiring keys.
5. Avoid blocking calls on TCP client — use await.

📜 License

MIT License – see LICENSE