[{"_1":2,"_165":-5,"_166":-5},"loaderData",{"_3":4,"_13":14,"_20":21,"_141":142},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":11,"_17":11,"_18":19},"username","isBillingDecouplingSeatCount","isSearchBoxExperimentEnabled","isAskGordonEnabled",true,"routes/_layout.r.$namespace.$reponame",{"_22":23,"_24":-5,"_25":11,"_26":11,"_27":28,"_29":30,"_31":-5,"_32":11,"_33":34,"_93":-5,"_94":95,"_134":-5,"_135":11,"_136":11,"_137":11,"_138":-5,"_139":140},"canonicalUrl","https://hub.docker.com/r/ehildt/acap/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","ehildt","reponame","acap","cloudBuildSource","isAutobuildsAvailable","repo",{"_35":36,"_48":49,"_51":52,"_53":54,"_55":11,"_56":57,"_58":59,"_60":61,"_38":30,"_27":28,"_63":64,"_65":50,"_66":67,"_68":69,"_70":71,"_72":-5,"_73":67,"_74":75,"_76":11,"_77":28,"_78":79,"_84":11,"_85":86,"_90":28,"_91":92},"categories",[37,42,45],{"_38":39,"_40":41},"name","Message queues","slug","message-queues",{"_38":43,"_40":44},"Content management system","content-management-system",{"_38":46,"_40":47},"Databases & storage","databases-and-storage","content_types",[50],"image","date_registered","2023-09-27T15:21:53.044871Z","description","A simple and convenient way to distribute and provide content to your apps ;)","is_private","last_updated","2024-05-23T17:53:18.24094Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[62],"application/vnd.docker.container.image.v1+json","pull_count",670,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","

\nAdaptive Content Aggregation Proxy (ACAP)\n

\n\n

\n\n`The ideal time to grow a business was yesterday, but the next best time to invest in one is now.`\n\nACAP is a cutting-edge system designed to revolutionize content distribution and engagement. With its dynamic and adaptable features, it ensures that your clients and services receive the right content at the right time. ACAP responds in real-time to changing needs and preferences, guaranteeing a seamless and personalized experience. Its automated processes make content distribution effortless, allowing you to focus on what matters most. Moreover, ACAP empowers you to enhance user engagement by delivering timely, relevant, and diverse content through its platform or channels. This means increased customer satisfaction and loyalty, leading to business growth. Say goodbye to static and cumbersome content management and hello to ACAP's game-changing capabilities.\n\n

\n\n

Expand to read where it delivers!

\n
\n\n${\\color{gold}Dynamic \\space and \\space Adaptable \\space Content \\space Distribution}$ \nACAP ensures that other services receive the right content at the right time by dynamically adapting to their changing needs and preferences. This enhances content distribution for other services, providing them with a flexible and adaptable solution.\n\n${\\color{gold}Real-time \\space Responsiveness}$ \nACAP responds in real-time to the evolving needs and preferences of other services, ensuring a seamless and personalized experience. Its real-time responsiveness guarantees enhanced user engagement and satisfaction, as content is delivered promptly to meet their demands.\n\n${\\color{gold}Effortless \\space Content \\space Distribution}$ \nACAP automates content distribution processes, relieving other services from the burden of manual distribution tasks. With ACAP handling the efficient distribution of content, other services can focus on their core functionality, minimizing effort and maximizing productivity.\n\n${\\color{gold}Enhanced \\space User \\space Engagement}$ \nACAP empowers other services to deliver timely, relevant, and diverse content, enhancing user engagement. By leveraging ACAP's platform and channels, other services can optimize their content delivery strategies, resulting in increased user interaction and satisfaction.\n\n${\\color{gold}Increased \\space Customer \\space Satisfaction \\space and \\space Loyalty}$ \nBy delivering personalized and relevant content, ACAP helps other services improve customer satisfaction and foster loyalty. This, in turn, can lead to business growth and customer retention, driving long-term success for those services.\n\n

\n
\n

\n\n![Name](https://img.shields.io/badge/open_source-ACAP-gold)\n![License](https://img.shields.io/github/license/ehildt/acap?style=flat&color=brown)\n![DockerPulls](https://img.shields.io/docker/pulls/ehildt/acap?color=darkgreen&label=docker%20pulls&logo=docker) \n![Branch](https://img.shields.io/badge/branch-main-blue?style=flat&logo=git&logoColor=white)\n![Version](https://img.shields.io/github/package-json/v/ehildt/acap?style=flat&color=orange)\n![Node](https://img.shields.io/badge/node-LTS-purple?style=flat&logo=node.js&logoColor=white)\n![BuildStatus](https://img.shields.io/badge/build-passing-darkgreen?style=flat&logo=github&logoColor=white) \n![codecov](https://codecov.io/gh/ehildt/acap/graph/badge.svg?token=MCL18OCNV7)\n![Changeset](https://img.shields.io/badge/Changeset-SemVer-green)\n

\n\n

\n\npowered by\n\n![NestJs](https://img.shields.io/badge/nestjs-E0234E?style=for-the-badge&logo=nestjs&logoColor=white)\n![Fastify](https://img.shields.io/badge/fastify-202020?style=for-the-badge&logo=fastify&logoColor=white)\n![Redis](https://img.shields.io/badge/redis-%23DD0031.svg?&style=for-the-badge&logo=redis&logoColor=white)\n![BullMQ](https://img.shields.io/badge/bullmq-%233C5280?style=for-the-badge&logo=redis&logoColor=white)\n![PubSub](https://img.shields.io/badge/pubsub-aC5cce?style=for-the-badge&logo=redis&logoColor=white) \n![MQTT](https://img.shields.io/badge/MQTT-660066?style=for-the-badge&logo=mqtt&logoColor=white)\n![MongoDB](https://img.shields.io/badge/MongoDB-47A248?style=for-the-badge&logo=mongodb&logoColor=white)\n![Docker](https://img.shields.io/badge/Docker-2496ED?style=for-the-badge&logo=docker&logoColor=white)\n![Swagger](https://img.shields.io/badge/Swagger-85EA2D?style=for-the-badge&logo=Swagger&logoColor=black)\n![TypeScript](https://img.shields.io/badge/TypeScript-007ACC?style=for-the-badge&logo=typescript&logoColor=white) \n![ESLint](https://img.shields.io/badge/ESLint-4B32C3?style=for-the-badge&logo=eslint&logoColor=white)\n![Prettier](https://img.shields.io/badge/Prettier-F7B93E?style=for-the-badge&logo=prettier&logoColor=white)\n![Jest](https://img.shields.io/badge/Jest-C21325?style=for-the-badge&logo=jest&logoColor=white)\n![Git](https://img.shields.io/badge/Git-F05032?style=for-the-badge&logo=git&logoColor=white)\n![Minio](https://img.shields.io/badge/-MinIO-C72E49?style=for-the-badge&logo=minio&logoColor=white)\n\n

\n\n
\n\n

\nTable of Contents\n

\n\n[Getting Started](#getting-started) \n[Serialization and Persistence](#serialization-and-persistance) \n[Example Use Cases](#example-use-cases) \n[Whats in the box?](#whats-in-the-box) \n[Content Validation](#content-validation) \n[Content Encryption](#content-encryption) \n[Caching](#caching) \n[Redis Publish Subscribe](#redis-publish-subscribe) \n[MQTT](#mqtt) \n[Kafka](#kafka) \n[RabbitMQ](#rabbitmq) \n[BullMQ](#bullmq) \n[Outbreak API](#outbreak-api)\n\n

\n
\n\n## Getting Started\n\n
\n\n> VSCODE: Before we start, please do yourself a favor and open the **.code-workspace** file in the project root with vscode.\nTrust me, it will make your life much simpler. Now back to topic.\n\nGetting ACAP up and running is pretty straight forward.\n\n

Docker

\n\nRun the following commands to install the required dependencies:\n\n1. `npm i -g pnpm && pnpm install`.\n2. `sudo apt install python3 python3-pip`\n3. `pip install jinja2`\n\nGenerate the docker-compose.yml:\n\n1. `pnpm run -r genpose`.\n2. `docker-compose.yml`\n\nGenpose will generate the docker-compose.yml based on the set environment variables.\n\n- USE_REDIS_PUBSUB=false\n- USE_BULLMQ=false\n- USE_MQTT=false\n- USE_KAFKA=false\n- USE_RABBITMQ=false\n\nPlease note that without USE_RABBITMQ=true, no other services will be activated. This is because the backend relies on RabbitMQ to emit events to the message bridge, which then distributes them to the brokers.\n\n> For Kafka you would need to set **USE_RABBITMQ=true** and **USE_KAFKA=true**\n\nBy default the message bridge as well as all brokers are disabled.\n\n

CLI

\n\nWe recommend utilizing [pnpm](https://pnpm.io/), as it streamlines the execution of tests, linting processes, and script initialization, resulting in improved efficiency and ease of use.\n\n- Install pnpm `npm i -g pnpm`.\n- Install the dependencies `pnpm install`.\n- Run `pnpm run -r start:dev`\n\n> Make sure all the required services aka databases etc are up and running. \n> If you ran docker previously, then you most likely will get an error compiling the dist folders.\n> Simply `sudo rm -rf` those folders in every workspace.\n\nYou can run storybook explicitly or execute tests in parallel:\n\n- Storybook `pnpm run --filter frontend storybook`\n- Run tests parallel in all workspaces `pnpm run -r test`.\n\n

Config

\n\n**ACAP** simplifies the initialization process by providing a convenient ready-to-use setup. It leverages a `config.yml` file, reducing dependence on system environment variables, while still allowing flexibility to set them when required.\n\nWhen utilizing ACAP in Docker or Kubernetes (K8S), configuring the service is effortless. By binding the `/app/config.yml` to a volume, you can easily adjust the service settings. The `config.yml` file contains default presets, which, when combined with Docker Compose, enable a speedy setup for local development. This approach facilitates a seamless spin-up process for your projects.\n\n
\n\n

Expand to see the sample config.yml file

\n
\n

\n\n```yml\nappConfig:\n port: 3001\n address: 0.0.0.0\n printEnv: true\n startSwagger: true\n nodeEnv: \"local\"\n bodyLimit: \"104857600\"\n crypto:\n secret: CryptoShield2024\n realm:\n ttl: 300\n resolveEnv: true\n namespacePostfix: ACAP\n gzipThreshold: 20\n brokers:\n useBullMQ: true\n\nmongoConfig:\n uri: mongodb://mongo:27017\n ssl: false\n tlsAllowInvalidCertificates: false\n dbName: ACAP\n user: mongo\n pass: mongo\n\nminioConfig:\n endPoint: \"minio\"\n port: 9000\n useSSL: false\n accessKey: \"minio\"\n secretKey: \"minio2024\"\n bucket: \"acap\"\n\nredisConfig:\n host: keydb\n port: 6379\n ttl: 600\n max: 100\n db: 0\n password: redis\n username: default\n\nbullMQConfig:\n connection:\n port: 6379\n host: keydb\n password: redis\n username: default\n```\n\n

\n\n
\n\n

Expand to see the sample docker compose file

\n
\n

\n\n```yml\nservices:\n frontend:\n container_name: frontend\n build:\n context: ./apps/frontend\n target: local\n depends_on:\n - backend\n volumes:\n - ./apps/frontend:/app\n - ./node_modules:/node_modules\n environment:\n - ./apps/frontend/.env.development\n ports:\n - \"5173:5173\"\n networks:\n - acap-network\n\n backend:\n container_name: backend\n build:\n context: ./apps/backend\n target: local\n volumes:\n - ./apps/backend:/app\n - ./node_modules:/node_modules\n depends_on:\n - mongo\n - minio\n - keydb\n - msbridge\n env_file:\n - ./apps/backend/env/.env\n ports:\n - 3001:3001\n networks:\n - acap-network\n\n msbridge:\n container_name: msbridge\n build:\n context: ./apps/ms-bridge\n target: local\n volumes:\n - ./apps/ms-bridge:/app\n - ./node_modules:/node_modules\n depends_on:\n - keydb\n - kafka\n - mosquitto\n - rabbitmq\n env_file:\n - ./apps/ms-bridge/env/.env\n environment:\n - KAFKAJS_NO_PARTITIONER_WARNING=1\n ports:\n - 3002:3002\n networks:\n - acap-network\n\n keydb:\n image: eqalpha/keydb\n container_name: keydb\n ports:\n - 6379:6379\n volumes:\n - keydb_data:/data\n - ./apps/ms-bridge/keydb.conf:/usr/local/etc/keydb/keydb.conf\n command: keydb-server /usr/local/etc/keydb/keydb.conf\n networks:\n - acap-network\n restart: unless-stopped\n\n mongo:\n command: mongod --quiet --wiredTigerCacheSizeGB 1.5 --logpath /dev/null\n image: mongo\n container_name: mongo\n environment:\n - MONGO_INITDB_ROOT_USERNAME=mongo\n - MONGO_INITDB_ROOT_PASSWORD=mongo\n - MONGO_INITDB_DATABASE=ACAP\n volumes:\n - mongo_data:/data/db\n ports:\n - 27017:27017\n networks:\n - acap-network\n restart: unless-stopped\n\n minio:\n image: \"bitnami/minio\"\n container_name: minio\n ports:\n - \"9000:9000\"\n - \"9002:9001\" # Management UI port (optional)\n environment:\n - MINIO_ROOT_USER=minio\n - MINIO_ROOT_PASSWORD=minio2024\n - MINIO_SKIP_CLIENT=yes\n - MINIO_DEFAULT_BUCKETS=acap\n volumes:\n - minio_data:/bitnami/minio/data\n networks:\n - acap-network\n restart: unless-stopped\n\n mosquitto:\n image: eclipse-mosquitto\n container_name: mosquitto\n ports:\n - 1883:1883\n - 9001:9001\n volumes:\n - mosquitto_data:/mosquitto/data\n - ./mosquitto.conf:/mosquitto/config/mosquitto.conf\n - mosquitto_log:/mosquitto/log\n networks:\n - acap-network\n restart: unless-stopped\n\n kafka:\n image: 'bitnami/kafka'\n container_name: kafka\n ports:\n - '9092:9092'\n - '9093:9093'\n volumes:\n - kafka_data:/bitnami/kafka\n environment:\n - KAFKA_CFG_NODE_ID=1\n - KAFKA_CFG_PROCESS_ROLES=broker,controller\n - KAFKA_CFG_CONTROLLER_QUORUM_VOTERS=1@kafka:9093\n - KAFKA_CFG_LISTENERS=PLAINTEXT://:9092,CONTROLLER://:9093\n - KAFKA_CFG_ADVERTISED_LISTENERS=PLAINTEXT://kafka:9092\n - KAFKA_CFG_CONTROLLER_LISTENER_NAMES=CONTROLLER\n - KAFKA_CFG_AUTO_CREATE_TOPICS_ENABLE=true\n - KAFKA_CFG_OFFSETS_TOPIC_REPLICATION_FACTOR=1\n - KAFKA_CFG_TRANSACTION_STATE_LOG_REPLICATION_FACTOR=1\n - KAFKA_CFG_TRANSACTION_STATE_LOG_MIN_ISR=1\n - KAFKA_CFG_LOG_DIRS=/bitnami/kafka/data\n - ALLOW_PLAINTEXT_LISTENER=yes\n networks:\n - acap-network\n restart: unless-stopped\n\n kafdrop:\n image: obsidiandynamics/kafdrop\n container_name: kafdrop\n ports:\n - '9003:9000'\n environment:\n KAFKA_BROKERCONNECT: 'kafka:9092'\n JVM_OPTS: '-Xms32M -Xmx64M'\n depends_on:\n - kafka\n networks:\n - acap-network\n\n rabbitmq:\n image: rabbitmq\n container_name: rabbitmq\n ports:\n - \"5672:5672\"\n - \"15672:15672\"\n volumes:\n - rabbitmq_data:/bitnami/rabbitmq\n - ./apps/ms-bridge/rabbitmq.conf:/etc/rabbitmq/rabbitmq.conf\n networks:\n - acap-network\n restart: unless-stopped\n\nvolumes:\n mongo_data:\n minio_data:\n keydb_data:\n kafka_data:\n rabbitmq_data:\n mosquitto_data:\n mosquitto_config:\n mosquitto_log:\n\nnetworks:\n acap-network:\n driver: bridge\n```\n\n

\n\n
\n\nAs mentioned earlier, you can still utilize system environment variables either in conjunction with the config.yml file. System environment variables, if set, take precedence over the values specified in the config.yml file. Here are the system environment variables that are available for utilization.\n\n

Expand to see the sample .env file

\n
\n

\n\n```sh\nPORT=3001\nADDRESS='0.0.0.0'\nNODE_ENV='local'\nREALM_TTL=300\nREALM_NAMESPACE_POSTFIX='ACAP'\nREALM_GZIP_THRESHOLD=20\nPRINT_ENV=true\nSTART_SWAGGER=true\nREALM_RESOLVE_ENV=true\nUSE_REDIS_PUBSUB=true\nUSE_BULLMQ=true\nUSE_MQTT=true\nSYMMETRIC_KEY='a4e8b65e2c3e167942bcf48abf6e9d71'\nBODY_LIMIT=104857600\n\nREDIS_PUBSUB_PORT=6379\nREDIS_PUBSUB_USER='default'\nREDIS_PUBSUB_PASS='redis'\nREDIS_PUBSUB_HOST='redis'\n\nBULLMQ_REDIS_PORT=6379\nBULLMQ_REDIS_USER='default'\nBULLMQ_REDIS_PASS='redis'\nBULLMQ_REDIS_HOST='redis'\n\nMQTT_KEEPALIVE=5000\nMQTT_CONNECTION_TIMEOUT=5000\nMQTT_RECONNECT_PERIOD=1000\nMQTT_RESUBSCRIBE=true\nMQTT_BROKER_URL='mqtt://localhost'\nMQTT_PROTOCOL='mqtt'\nMQTT_HOSTNAME='localhost'\nMQTT_PORT=1883\nMQTT_USERNAME='mqtt'\nMQTT_PASSWORD='mqtt'\n\nMONGO_USER='mongo'\nMONGO_PASS='mongo'\nMONGO_DB_NAME='ACAP'\nMONGO_URI='mongodb://mongo:27017'\nMONGO_SSL=false\nMONGO_TLS_ALLOW_INVALID_CERTIFICATES=true\n\nREDIS_USER='default'\nREDIS_PASS='redis'\nREDIS_HOST='redis'\nREDIS_PORT=6379\nREDIS_TTL=600\nREDIS_MAX_RESPONSES=100\nREDIS_DB_INDEX=0\n\nMINIO_ENDPOINT='minio'\nMINIO_ACCESS_KEY='minio'\nMINIO_SECRET_KEY='minio'\nMINIO_PORT=9000\nMINIO_USE_SSL=false\nMINIO_BUCKET='acap'\n```\n\n

\n\n
\n\nWith this, you have everything you need to make the ACAP your own and harness its full potential to power your applications and drive business growth.\n\n
\n\n## Serialization and Persistance\n\nStructured data, like JSON and YAML, is housed in mongoDB for persistence. Meanwhile, unstructured data such as images and files is stored in minio, with their metadata structured and stored in mongoDB for efficient retrieval. Structured is cached by redis, while unstructured is cached and managed by minio.\n\n
\n\n## Example Use Cases\n\nOne example use case for ACAP could be serving base64-encoded images to web clients. This setup allows for dynamic switching of content on the fly, similar to how it is commonly done in a content management system (CMS). Of course, this capability is not limited solely to images.\n\nAnother use case could involve inter-service communication, enabling a centralized configuration as a single source of truth. This can be achieved by leveraging technologies such as **bullMQ**, **MQTT** and **RedisPubSub** which facilitate real-time provision and distribution of these configurations.\n\nThere are instances where utilizing ACAP as a proxy can be advantageous. By creating content that references external sources holding the required datasets, you can leverage the capabilities of ACAP without the need for directly handling large datasets. This approach greatly enhances the efficiency of data retrieval and management.\n\nIn certain scenarios, there may be a need to describe and validate content. ACAP accomplishes this by utilizing JSON schema with the help of **avj**. In IDEs like **Visual Studio Code** and similar environments, you have the ability to link the **$schema** , which enables highlighting and validation. Alternatively, you can fetch the schema on the client side and perform data validation in real time during runtime.\n\n## Whats in the box?\n\nPostman, Insomnia and Swagger OpenApi were yesterday! ACAP delivers a sleek, modern, and intuitive user interface, designed to effortlessly manage and organize your content (**WIP**). With crisp content management and immediate processing, your experience is seamless and efficient. ACAP simplifies the process for developers to enable or disable optional features like Redis Publish Subscribe, MQTT, and BullMQ as per their requirements.\n\n### Content Validation\n\nWhen creating and managing content, you can freely choose between a strict or lenient approach to describe its structure. Validation of your content involves checking if a JSON schema matches the content. ACAP knows which content belongs to which schema by simply referencing the realm identifier. In simpler terms, if you create content with a realm value of **MY_REALM** and a schema that also has a realm value of **MY_REALM**, your content will be validated against that schema. The content itself is not bound to any particular structure or value. It even has the capability to fetch system variables when enabled, as long as the content identifier matches the specified system variable key. By default, this feature is disabled to ensure security. For a more comprehensive understanding of content and schema declarations, please refer to the [Wiki](https://github.com/ehildt/ACAP/wiki/ACAP).\n\n`This powerful feature provides industry-leading flexibility in managing content structure, empowering companies to customize and validate their content with ease and efficiency. Experience unparalleled control and adaptability in content management, unlocking new possibilities for your business's success.`\n\n### Content Encryption\n\nIn ACAP, we prioritize your freedom of choice, including your security preferences. By default, ACAP conducts content upserts without encryption, suitable for most scenarios. However, recognizing the paramount importance of data security, we empower you to strengthen defenses by encrypting content before it's stored.\n\nWithin ACAP, we leverage the globally recognized Advanced Encryption Standard (AES). You have access to multiple block cipher modes: AES-256-CBC, AES-192-CBC, and AES-128-CBC, with respective key lengths of 32, 24, and 16 bytes.\n\nIn essence, these AES-CBC modes form a robust security foundation. Your choice depends on specific security and performance needs. Opt for AES-256-CBC for peak security, accepting a slight performance trade-off. Or choose AES-128-CBC, delivering strong security without performance compromise. For a balanced blend, consider AES-192-CBC.\n\nWith ACAP, it's your data, your choice, fortified by our robust security options. Elevate your data protection standards while retaining the flexibility to apply encryption as you see fit. Your security, your way, with ACAP's formidable security toolkit.\n\n
\n\n

Expand to get more insight into AES

\n
\n\n${\\color{pink}AES-256-CBC}$\n\nSecurity: AES-256-CBC uses a 256-bit key, which provides a very high level of security. As of 2021, it is considered highly secure and resistant to brute force attacks. The key length is so long that it would require an astronomical amount of computational power and time to break the encryption by trying all possible keys. Drawbacks: The main drawback of AES-256-CBC is its computational overhead. Encrypting and decrypting data with a longer key can be slower compared to AES-128-CBC or AES-192-CBC. This difference may not be noticeable for small amounts of data but could become significant for large datasets or high-throughput applications.\n\n${\\color{pink}AES-192-CBC}$\n\nSecurity: AES-192-CBC uses a 192-bit key, which is also considered very secure. It strikes a balance between the strong security of AES-256-CBC and the computational efficiency of AES-128-CBC. Drawbacks: Like AES-256-CBC, the main drawback is the computational overhead, although it's generally slightly faster than AES-256-CBC. It may be a good choice when you need strong security but want slightly better performance than AES-256-CBC.\n\n${\\color{pink}AES-128-CBC}$\n\nSecurity: AES-128-CBC uses a 128-bit key, which is still considered secure but is theoretically more susceptible to brute force attacks compared to AES-192-CBC and AES-256-CBC. However, in practice, it offers a high level of security for most applications. Drawbacks: The primary advantage of AES-128-CBC is its speed and lower computational overhead. It's generally faster than AES-192-CBC and AES-256-CBC. The drawback is that, in rare cases of highly motivated attackers with immense computational resources, it might be less secure compared to the longer key lengths.\n\n

\n
\n\n### KeyDB\n\nUnder the hood, ACAP utilizes [KeyDB](https://docs.keydb.dev/), a drop-in alternative for [Redis](https://redis.io/). ACAP builds on top of KeyDB and efficiently updates the cache whenever content is modified or fetched. Notably, only structured data is cached in memory. Unstructured data and all optimization are handled by MinIO. However, the metadata of unstructured files is stored and cached in memory as a reference and persisted in MongoDB.\n\n> KeyDB, ValKey, and Dragonfly are just a few drop-in alternatives to Redis. Feel free to use any compatible in-memory cache service you prefer.\n\n`KeyDB is a high performance open source database used at Snap, and a powerful drop-in alternative to Redis. While many databases keep the best features locked in their paid offerings, KeyDB remains fully open source. This best enables Snap & the community to collaborate and benefit together in the projects development.`\n\n### Publish Subscribe\n\nACAP supports [PubSub](https://redis.io/docs/interact/pubsub/). When this feature is enabled, ACAP automatically publishes content using the realm as the channel, which can be subscribed to by other clients and services. The **fire-and-forget** strategy for **Redis Publish Subscribe** ensures non-blocking transmission, allowing for a seamless content distribution without any interruptions.\n\n### MQTT\n\n[MQTT](https://mqtt.org/) plays a crucial role in enhancing ACAP by addressing key communication challenges in the IoT ecosystem. With MQTT, ACAP benefits from the following features:\n\n- **Lightweight and Efficient:** MQTT's lightweight nature ensures minimal bandwidth usage and a small footprint, allowing ACAP to optimize resource utilization while maintaining efficient communication between devices.\n\n- **Reliable Message Delivery:** ACAP leverages MQTT's message queuing capabilities, enabling devices to reliably publish messages to specific topics. This ensures that important data is delivered without loss or duplication, guaranteeing the integrity of the information exchanged.\n- **Scalability:** MQTT's scalable nature allows ACAP to accommodate a growing number of devices within the IoT ecosystem. As your service expands, MQTT ensures seamless and efficient communication, enabling ACAP to handle a large volume of messages without sacrificing performance.\n- **Real-time Data Exchange:** MQTT's ability to handle unreliable networks makes it an ideal choice for ACAP. It ensures that real-time data exchange between devices occurs smoothly, even in challenging network conditions, enhancing the overall reliability and responsiveness of your service. By utilizing MQTT, ACAP leverages the power of this open-standard protocol to overcome communication hurdles, optimize resource usage, ensure reliable message delivery, and provide a scalable solution for real-time data exchange in IoT deployments.\n\n### Kafka\n\nBefore emitting data to Kafka, make sure you create the **ACAP_BRCS** topic. This is where ACAPs MSBridge will emit it's data.\n\nto be continue..\n\n### RabbitMQ\n\nto be continue..\n\n### BullMQ\n\n[BullMQ](https://docs.bullmq.io/), a powerful job and message queue library, brings several benefits to ACAP, enhancing its capabilities and performance. Here's how BullMQ benefits ACAP:\n\n- **Job Management:** BullMQ enables ACAP to efficiently manage and prioritize jo","has_starred","hub_user","immutable_tags_settings",{"_80":11,"_81":82},"enabled","rules",[83],".*","is_automated","permissions",{"_87":19,"_88":11,"_89":11},"read","write","admin","user","storage_size",2788224905,"orgData","recentTags",[96],{"_97":50,"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_56":123,"_124":99,"_125":28,"_126":62,"_38":127,"_128":129,"_130":114,"_131":123,"_132":71,"_133":19},"content_type","creator",23284020,"digest","sha256:f0035bca213c09cb2de5901be22d94e6bbc2e404d71945eaa97879683cb09782","full_size",122055161,"id",530532898,"images",[108],{"_109":110,"_100":101,"_111":112,"_113":114,"_115":116,"_117":118,"_119":112,"_120":-5,"_121":103,"_68":71,"_122":-5},"architecture","amd64","features","","last_pulled","2026-07-15T05:29:15.132357182Z","last_pushed","2024-05-23T17:53:18Z","os","linux","os_features","os_version","size","variant","2024-05-23T17:53:17.113879Z","last_updater","last_updater_username","media_type","latest","repository",22059488,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_33":143,"_153":154,"_139":163,"_164":11},{"_35":144,"_48":148,"_51":52,"_53":54,"_55":11,"_56":57,"_58":59,"_60":149,"_38":30,"_27":28,"_63":64,"_65":50,"_66":67,"_68":69,"_70":71,"_72":-5,"_73":67,"_74":75,"_76":11,"_77":28,"_78":150,"_84":11,"_85":152,"_90":28,"_91":92},[145,146,147],{"_38":39,"_40":41},{"_38":43,"_40":44},{"_38":46,"_40":47},[50],[62],{"_80":11,"_81":151},[83],{"_87":19,"_88":11,"_89":11},"tags",{"_155":69,"_156":-5,"_157":-5,"_158":159},"count","next","previous","results",[160],{"_97":50,"_98":99,"_100":101,"_102":103,"_104":105,"_106":161,"_56":123,"_124":99,"_125":28,"_126":62,"_38":127,"_128":129,"_130":114,"_131":123,"_132":71,"_133":19},[162],{"_109":110,"_100":101,"_111":112,"_113":114,"_115":116,"_117":118,"_119":112,"_120":-5,"_121":103,"_68":71,"_122":-5},[],"canDeleteTags","actionData","errors"]

ehildt/acap

Tags for ehildt/acap