squrl

Whole-System State Management

Overview

What if we could describe our business domain as a set of functions that both Server and Client could share? What if instead of worrying about CRUD actions on data, we worried about the secret sauce that makes our application unique? What if we could point our whole application at a description of resources and let it figure out how to do everything else? Enter squrl: Think of it as meteor meets graphql meets lenses.

Pieces

• Parser

  • Responsible for abstracting the decoding of messages sent across the wire

• Socket

  • Responsible for abstracting both Client and Server WebSocket communication using Parser

• State

  • Responsible for reacting to actions sent across the wire that keeps the Data in sync across devies

• Utils

  • General utilities and helpers that are used internally