71 packages tagged with “pub/sub”
A lightweight enterprise Function as a service (FaaS) framework to write function based serverless and micro-service applications in hybrid multi-datacentre, on-premise and Azure environments, offering modern patterns such as CQRS and event-sourcing. Offering a superior combination of serverless, micro-service and traditional deployments both in the cloud and on-premise to suit any business. Deployments can be inter-conntected with each other sharing data and resourcing or independant and issolated while providing a consistent framework and guideline for both development, deployment, DevOps and administration. CQRS.NET has been designed with modularity in mind... see the number of technology packages below you can chose from. Modularity applies to both development concerns like storage as well as operational modularity such as serverless or micro-service deployment, PaaS, VMs or container packaging. Every package and design choice made should be interchangeable with custom code if needed.
Use Azure ServiceBus as a message, event or command bus in CQRS.NET
Use Ninject as your IoC container of choice with Greg Young's Event Store for CQRS.NET
A visual designer for the lightweight CQRS.net framework. Using this package you can generate much of the boiler plate code involved in implementing a scalable, enterprise grade CQRS project ready for deployment on-premise or on Azure.
Use Greg Young's event store as the Event Store in CQRS.NET
Deprecated. Use the Cqrs.Ninject package instead.
Use Ninject as your IoC container of choice when using Microsoft Azure ServiceBus for CQRS.NET as your event bus
Use Ninject as your IoC container of choice when using Microsoft Azure ServiceBus for CQRS.NET as your command bus
The built-in, Sql Store in the CQRS.NET cannot process non-primitive properties on the entity classes in read stores and data stores. If your entity classes require more comp[lexity than just basic, flat primitive property structures, this package will allow you to use Microsoft SqlServer as an read store and data store in CQRS.NET allowing you to build custom converters to provide mappings from your entities to you SQL table schema structures.
These packages include the resources needed to write Remote Data Adapters and Remote Metadata Adapters for Lightstreamer Server with .NET. Each Lightstreamer session requires the presence of an Adapter Set, which is made up of one Metadata Adapter and one or multiple Data Adapters. Multiple Adapter Sets can be plugged onto Lightstreamer Server. Please refer to the provided "General Concepts.pdf" document for further details about the role of the Adapters in Lightstreamer, and in particular to this documentation https://lightstreamer.com/docs/ls-server/latest/Adapter%20Remoting%20Infrastructure.pdf for Remote Adapters deploying. The full API references are available from https://lightstreamer.com/sdks/ls-dotnetstandard-adapter/1.15.2/api/index.html
Use Ninject as your IoC container of choice to use WCF with CQRS.NET as ServiceHosts
Use Akka.NET actors in CQRS.NET
Use Ninject as your IoC container of choice with Akka.Net for CQRS.NET
Use Azure EventHubs as a message, event or command bus in CQRS.NET
Use Ninject as your IoC container of choice with Microsoft WCF for CQRS.NET
The Lightstreamer .Net Standard Client SDK allows to subscribe to real-time data pushed by a Lightstreamer server and to send any message to the server. The library offers automatic recovery from connection failures, automatic selection of the best available transport, and full decoupling of subscription and connection operations.
Use Ninject as your IoC container of choice when using Microsoft Azure Event hubs for CQRS.NET as your event bus
Use Azure Webjobs with CQRS.NET
Use Ninject as your IoC container of choice when using Microsoft Azure Event hubs for CQRS.NET as your command bus
Use Ninject as your IoC container of choice with Microsoft WebJobs for CQRS.NET
Use DI with CQRS.NET
Package Description
A simple, lightweight event messenger that uses a ConditionalWeakTable internally.
Use MS DI as your IoC container of choice when using Microsoft Azure ServiceBus for CQRS.NET as your event bus
Use Azure Functions with CQRS.NET
Use MS DI as your IoC container of choice when using Microsoft Azure ServiceBus for CQRS.NET as your command bus