Posts

Showing posts from 2020

AspNetCore.IgniteServer: A .NET Core, Kubernetes ready, authentication, and SSL enabled Apache Ignite server implementation

AspNetCore.IgniteServer 2.19.0 (extracted from Tarzan and improved)      AspNetCore.IgniteServer is an implementation of Apache Ignite 2 embedded mode that references necessary assemblies to provide a server-side component for the ASP.NET Core platform. Kubernetes ready, authentication and SSL enabled with auto-discovery clustering capabilities. Usually, every node runs one or more instances of the server.      The repository also contains AspNetCore.Ignite , a thin client library for ASP.NET Core applications (see Client library below). What's new       Version 2.19.0 targets .NET 10. It is the first published image that starts (the JVM options of the 2.17.0 and 2.18.0 images included -server , which the embedded JVM rejects). The highlights: Settings from environment variables, validated at startup: every error is listed, and the server exits with code 1. Health and metrics on port 9464: /health/startup , /health/readiness , /health/...

Rebalancer for RabbitMQ, SQS, etc.

Image
Rebalancer 6.0 (forked from Jack Vanlightly  and improved)      Create Kafka style consumer groups in other technologies. Rebalancer was born of the need for consumer groups with RabbitMQ. But Rebalancer is completely technology-agnostic and will balance activity over any group of resources across a group of participating nodes. Use cases Create Kafka-like "consumer groups" with messaging technologies like RabbitMQ, SQS, etc. On RabbitMQ 3.8+ read RabbitMQ: ordered consumer groups with Rebalancer or with super streams first: single active consumer and super streams now cover much of this natively. Consume a group of resources such as file shares, FTPs, S3 buckets between the instances of a scaled-out application. Single Active-Consumer / Active-Backup. Create an application cluster that consumes a single resource in a highly available manner. The cluster leader (Coordinator) consumes the single resource, and the other nodes (Followers) remain idle in backup...

Poison message handling RabbitMQ

Image
     Poison message handling in RabbitMQ it is available as of RabbitMQ 3.8.0, by using the new type of queue:  Quorum Queues .      Quorum queue support handling of poison messages, that is, messages that cause a consumer to repeatedly requeue a delivery (possibly due to a consumer failure) such that the message is never consumed completely and positively acknowledged so that it can be marked for deletion by RabbitMQ.      Be aware, some features are not currently supported by quorum queues:      Quorum queues keep track of the number of unsuccessful delivery attempts and expose it in the "x-delivery-count" header that is included with any redelivered message.      It is possible to set a delivery limit for a queue using a policy argument, delivery-limit. When a message has been returned more times than the limit the message will be dropped or dead-lettered (if a DLX is configu...