feathers-reactive - Reactive API extensions for Feathers services

  •        7

Reactive API extensions for Feathers services

https://github.com/feathersjs/feathers-reactive

Tags
Implementation
License
Platform

   




Related Projects

authentication - Feathers local, token, and OAuth authentication over REST and Websockets using JSON Web Tokens (JWT) with PassportJS


Add Authentication to your FeathersJS app. @feathersjs/authentication adds shared PassportJS authentication for Feathers HTTP REST and WebSocket transports using JSON Web Tokens.

docs - The FeathersJS documentation, powered by GitBook


Feathers is a batteries included but entirely optional minimal web application framework. At its core, Feathers is a set of tools and an architecture pattern that make it easy to create scalable REST APIs and real-time applications. With Feathers, you can literally build prototypes in minutes and production-ready apps in days.

feathers - User interface components for Starling Framework and Adobe AIR


Warning: This is a pre-release version of Feathers UI. It may contain bugs or unfinished features. It is not recommended for production apps because it is considered potentially unstable. Use at your own risk. To download a stable build, visit the Feathers website. Say hello to Feathers UI, a library of light-weight, skinnable, and extensible UI controls for mobile and desktop. The components run on Starling Framework and Adobe AIR — offering blazing fast GPU powered graphics to create a smooth and responsive experience. Build completely standalone, native applications on iOS, Android, Windows, and macOS, or target Adobe Flash Player in desktop browsers. Created by Josh Tynjala from Bowler Hat LLC, Feathers UI is free and open source.


awesome-feathersjs - A list of awesome things related to FeathersJS


feathers-accounts - Token-Based User Account System for FeathersJS (configure).

feathers-examples - The Feathers examples have moved!


The Feathers examples have moved!

chyrp - The ultra-lightweight ultra-flexible blogging engine with a fetish for birds and misspellings


Chyrp is a blogging engine designed to be lightweight while retaining functionality. It is driven by PHP and MySQL (or SQLite), and has a great standard theme and robust module engine. You can personalize and modify it any way you want. All of your content is powered by a unique Feathers system that allows Chyrp to be whatever you want it to be. You can post anything and everything, or just stick to the default Text feather and run a regular blog. Chyrp destroys the fine line between a blog and a tumblelog.

GeoBB 1.0


GeoBB is FIRST Georgian discussion board written in PHP, MySQL, CSS and JavaScript. GeoBB is designed to be the fastest Discussions board and also includes site search engine. much more feathers you can see when visitng the Demonstration Page.

feathers - User interface components for Starling Framework


User interface components for Starling Framework

Reactive Extensions Plugin for Resharper


A Resharper plug-in to help use the Reactive Extension libraries. This has been developed for Resharper version 7.1 and supports the following version of the .N

alpakka - Alpakka is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Akka


Systems don't come alone. In the modern world of microservices and cloud deployment, new components must interact with legacy systems, making integration an important key to success. Reactive Streams give us a technology-independent tool to let these heterogeneous systems communicate without overwhelming each other. The Alpakka project is an open source initiative to implement stream-aware, reactive, integration pipelines for Java and Scala. It is built on top of Akka Streams, and has been designed from the ground up to understand streaming natively and provide a DSL for reactive and stream-oriented programming, with built-in support for backpressure. Akka Streams is a Reactive Streams and JDK 9+ java.util.concurrent.Flow-compliant implementation and therefore fully interoperable with other implementations.

alpakka-kafka - Alpakka Kafka connector - Alpakka is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Akka


Systems don't come alone. In the modern world of microservices and cloud deployment, new components must interact with legacy systems, making integration an important key to success. Reactive Streams give us a technology-independent tool to let these heterogeneous systems communicate without overwhelming each other. The Alpakka project is an open source initiative to implement stream-aware, reactive, integration pipelines for Java and Scala. It is built on top of Akka Streams, and has been designed from the ground up to understand streaming natively and provide a DSL for reactive and stream-oriented programming, with built-in support for backpressure. Akka Streams is a Reactive Streams and JDK 9+ java.util.concurrent.Flow-compliant implementation and therefore fully interoperable with other implementations.

ReactiveUI - An advanced, composable, functional reactive model-view-viewmodel framework for all


ReactiveUI is a composable, cross-platform model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming which is a paradigm that allows you to abstract mutable state away from your user interfaces and express the idea around a feature in one readable place and improve the testability of your application.That's reactive programming: changes propagate throughout a system automatically. Welcome to the peanut butter and jelly of programming paradigms. For further information please watch the this video from the Xamarin Evolve conference - Why You Should Be Building Better Mobile Apps with Reactive Programming by Michael Stonis.

RxRuby - Reactive Extensions for Ruby


Reactive Programming is a hot topic as of late, especially with such things as the Reactive Manifesto. Applications' needs have changed over time, from simple polling for data to a full reactive system where data is pushed at you. Each time, we're adding more complexity, data, and asynchronous behavior to our applications. How do we manage it all? How do we scale it? By moving towards "Reactive Architectures" which are event-driven, resilient, and responsive. With the Reactive Extensions, you have all the tools you need to help build these systems.The Reactive Extensions for Ruby (RxRuby) is a set of libraries for composing asynchronous and event-based programs using observable sequences and fluent query operators that many of you already know in Ruby. Using RxRuby, developers represent asynchronous data streams with Observables, query asynchronous data streams using our many operators, and parameterize the concurrency in the asynchronous data streams using Schedulers. Simply put, RxRuby = Observables + Operators + Schedulers.

spring-reactive-sample - Spring 5 Reactive playground


Reactive or Reactive Streams is a hot topic in these days, you can see it in blog entries, presentations, or some online course. Reactive Streams is an initiative to provide a standard for asynchronous stream processing with non-blocking back pressure.This encompasses efforts aimed at runtime environments (JVM and JavaScript) as well as network protocols.

freactive - High-performance, pure Clojurescript, declarative DOM library


pronounced "f-reactive" for functional reactive - name subject to change. This library should be considered experimental - it has not been widely tested. To try this quickly, you can install the austin repl plugin, run austin-exec, open a browser with the URL provided by austin and execute the code below. This code is also compatible with lein-figwheel - this is possibly the best approach for live Clojurescript development available now.

rxvision - visualizer debugger for reactive streams


Maintenance status: low. I'm not currently using this or RxJS, but I'm happy to review & merge pull requests if you want to make improvements. Completion status: Prototype. I got something working that worked well for demos, but wasn't really sufficient for large app-sized use cases. It also hasn't been updated to the latest versions of RxJS.