Related Projects

store - RxJS powered state management for Angular applications, inspired by Redux

  •    TypeScript

These core principles enable building components that can use the OnPush change detection strategy giving you intelligent, performant change detection throughout your application. Please read contributing guidelines here.

ngrx-actions - ⚡️ Actions and Reducer Utilities for NGRX

  •    TypeScript

Actions/reducer utility for NGRX. It provides a handful of functions to make NGRX/Redux more Angular-tastic. Inspired by redux-act and redux-actions for Redux.

akita - 🚀 State Management Tailored-Made for JS Applications

  •    TypeScript

Whether it be Angular, React, Vue, Web Components or plain old vanilla JS, Akita can do the heavy lifting and serve as a useful tool for maintaining clean, boilerplate-free, and scalable applications. Akita is a state management pattern, built on top of RxJS, which takes the idea of multiple data stores from Flux and the immutable updates from Redux, along with the concept of streaming data, to create the Observable Data Stores model.

redux-beacon - Analytics integration for Redux and ngrx/store

  •    TypeScript

If you're using Redux or ngrx/store to manage your app's state, you can use Redux Beacon to tap into your dispatched actions and map them to events that are consumable by an analytics service (e.g. Google Analytics). With Redux Beacon your entire global state life-cycle becomes trackable. Redux Beacon is lightweight. The core Redux Beacon module is tiny (~ 1KB), and each target, extension, and util, is either around the same size or smaller.

example-app - Example app showcasing the ngrx platform

  •    TypeScript

Example application utilizing @ngrx libraries, showcasing common patterns and best practices. Take a look at the live app. This app is a book collection manager. Using the Google Books API, the user can search for books and add them to their collection. This application utilizes @ngrx/db to persist the collection across sessions; @ngrx/store to manage the state of the app and to cache requests made to the Google Books API; @angular/router to manage navigation between routes; @ngrx/effects to isolate side effects.


store-devtools - Developer Tools for @ngrx/store

  •    TypeScript

Devtools for @ngrx/store. Please read contributing guidelines here.

angular-ngrx-data - Angular with ngRx and experimental ngrx-data helper

  •    TypeScript

You may never write an action, reducer, selector, effect, or HTTP dataservice again. NgRx helps Angular applications manage shared state in a "reactive" style, following the redux pattern.

yatrum - Yatrum - Share and Discover Travel Stories, Itineraries, Travel Guides built with ♥️ using Angular 4

  •    TypeScript

Yatrum built with ❤️ using Angular2, ngrx store, observables and reactive forms. We have also created and open sourced AngularSpree: Plug and play frontend application for SPREE E-Commerce API built with ❤️ using Angular2, Redux, Observables & ImmutableJs.

event-store - PHP 7.1 EventStore Implementation

  •    PHP

PHP 7.1 EventStore Implementation. Prooph Event Store is capable of persisting event messages that are organized in streams. Prooph\EventStore\EventStore itself is a facade for different persistence adapters (see the list below) and adds event-driven hook points for Prooph\EventStore\Plugin\Plugins which make the Event Store highly customizable.

eventstore - CQRS event store using PostgreSQL for persistence

  •    Elixir

CQRS event store implemented in Elixir. Uses PostgreSQL as the underlying storage engine. Requires Elixir v1.5 and PostgreSQL v9.5 or newer.

eventsourced - A library for building reliable, scalable and distributed event-sourced applications in Scala

  •    Javascript

In other words, Eventsourced implements a write-ahead log (WAL) that is used to keep track of messages an actor receives and to recover its state by replaying logged messages. Appending messages to a log instead of persisting actor state directly allows for actor state persistence at very high transaction rates and supports efficient replication. In contrast to other WAL-based systems, Eventsourced usually keeps the whole message history in the log and makes usage of state snapshots optional. Logged messages represent intended changes to an actor's state. Logging changes instead of updating current state is one of the core concept of event sourcing. Eventsourced can be used to implement event sourcing concepts but it is not limited to that. More details about Eventsourced and its relation to event sourcing can be found at How does Eventsourced persist actor state and how is this related to event sourcing.

laravel-event-projector - Event sourcing for Artisans 📽

  •    PHP

Event sourcing is to data what Git is to code 1. Most applications have their current state stored in a database. By storing only the current state a lot of information is lost. You don't know how the application got in this state. Event sourcing tries to solve that problem by saving all events that happen in your app. The state of your application is built by listening to those events.

EventStore - The open-source, functional database with Complex Event Processing in JavaScript.

  •    CSharp

The open-source, functional database with Complex Event Processing in JavaScript.This is the repository for the open source version of Event Store, which includes the clustering implementation for high availability.

redux-react-local - local component state via redux

  •    Javascript

Add the supplied reducer to a key local on your redux store. However, because 'views' don't have global references / identities ala Backbone etc, communicating between these components can get cumbersome 2; we then resort to building some form of messaging system external to these components - callbacks, pubsub channels, flux stores, observable event chains, etc. The smart ones use context to expose these systems to a particular render tree, avoiding 'global' state, but still getting a similar model.

platform - Reactive libraries for Angular

  •    TypeScript

Become a sponsor and get your logo on our README on Github with a link to your site. Please read contributing guidelines here.

PumpkinDB - Event Sourcing Database Engine

  •    Rust

PumpkinDB is a event sourcing database engine that doesn't overwrite data. It features include Immutable key/value storage, ACID transactions, Binary keys and values (allows any encoding to be used: JSON, XML, Protobuf, Cap'n Proto, etc.), An embedded programming language (PumpkinScript), A range of event indexing and querying primitives.

wolkenkit - wolkenkit is an open-source CQRS and event-sourcing framework for JavaScript and Node

  •    Javascript

wolkenkit is an open-source CQRS and event-sourcing framework for JavaScript and Node.js that perfectly matches DDD. wolkenkit is a CQRS and event-sourcing framework for JavaScript and Node.js. wolkenkit uses an event-driven model based on DDD to setup an API for your business in no time. This way, wolkenkit bridges the language gap between your domain and technology.

ReactStateMuseum - A whirlwind tour of React state management systems by example

  •    Javascript

Every app is meant to be small, simple, and the same as each other. The only difference should be the state management decisions of each. The repeated React and ReactNative app is a Packing List, with the name based on the state technology.