Browse free open source Lua Redis Clients and projects below. Use the toggles on the left to filter open source Lua Redis Clients by OS, license, language, programming language, and project status.

  • Our Free Plans just got better! | Auth0 Icon
    Our Free Plans just got better! | Auth0

    With up to 25k MAUs and unlimited Okta connections, our Free Plan lets you focus on what you do best—building great apps.

    You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
    Try free now
  • Cloud tools for web scraping and data extraction Icon
    Cloud tools for web scraping and data extraction

    Deploy pre-built tools that crawl websites, extract structured data, and feed your applications. Reliable web data without maintaining scrapers.

    Automate web data collection with cloud tools that handle anti-bot measures, browser rendering, and data transformation out of the box. Extract content from any website, push to vector databases for RAG workflows, or pipe directly into your apps via API. Schedule runs, set up webhooks, and connect to your existing stack. Free tier available, then scale as you need to.
    Explore 10,000+ tools
  • 1
    Carmine

    Carmine

    Redis client and message queue for Clojure

    A pure-Clojure Redis client & message queue. Redis is awesome and it's getting more awesome every day. It deserves a great Clojure client. Fully documented, API with full support for the latest Redis versions. Industrial strength connection pooling. Composable, first-class command functions. Flexible, high-performance binary-safe serialization using Nippy. Simple, high-performance message queue (v2+, Redis 2.6+). Simple, high-performance distributed lock (v2+, Redis 2.6+). Pluggable compression and encryption support (v2+). Includes Tundra, an API for replicating data to an additional datastore (v2+, Redis 2.6+). You'll usually want to define a single connection pool, and one connection spec for each of your Redis servers. Note that executing multiple Redis commands in a single wcar request uses efficient Redis pipelining under the hood, and returns a pipeline reply (vector) for easy destructuring, etc.
    Downloads: 1 This Week
    Last Update:
    See Project
  • Previous
  • You're on page 1
  • Next