Cronus Documentation
  • Introduction
  • Getting Started
    • Quick Start
      • Setup
      • Persist First Event
      • Explore Projections
  • Cronus Framework
    • Concepts
      • Domain Driven Design
      • Event Sourcing
      • Command Query Responsibility Segregation
    • Domain Modeling
      • Bounded Context
      • Multitenancy
      • Aggregate
      • Entity
      • Value Object
      • IDs
      • Published Language
      • Messages
        • Commands
        • Events
        • Public Events
        • Signals
      • Handlers
        • Application Services
        • Sagas
        • Projections
        • Ports
        • Triggers
        • Gateways
    • Event Store
      • EventStore Player
      • Migrations
        • Copy EventStore
    • Workflows
    • Indices
    • Jobs
    • Cluster
    • Messaging
      • Serialization
    • Configuration
    • Unit testing
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Getting Started

Quick Start

To help you get started quickly on the Cronus we will build an application that will satisfy all future business requirements.

Business requirements

  • We need a new task management system.

  • We need data to be consistent.

  • We need to be able to reassign tasks inside the user group.

  • We need an accurate progress report for every user.

  • Groups progress report needs to be secured such that only group members can access it.

  • We need a notification to the group members when a user finishes his task.

  • We need a screen to view the historical changes in user activity.

  • When users close their accounts we need to ask them why (optional survey).

  • We need to generate a monthly report that indicates why lost users closed their accounts.

PreviousIntroductionNextSetup

Last updated 2 years ago

Was this helpful?