gell-session

time based entity (lifcycle) modeling in an event based system

Objectives

• provide basis for commonly defined sessions in an event based system
  • for example, browser session in a web application
• model common session state via gell
• implement common events
  • session initiation
  • session ending
  • session invalidation
  • etc
• support timeline related features
• support metrics collection
• support session observation

Characterisics

• always tied to actor/user
• captures several timestamps
  • initiated/start
  • authenticated
  • end
  • expiration
• may also capture events
• closely resembles a sequence
• parent/child relationship

Outstanding

• must a session be associated with an actor in the system?
• should this package support scheduling features
  • or is this gell-schedule?

Deprecations

• storage mechanisms
  • transient, file system, dynamodb, etc
  • separate packages should do this
    • e.g. gell-fs
  • could eventually provide several persistence implementations
• search
• GraphQL bindings