Skip to content

Build a Help Desk sample on Polecat + Wolverine #9

Description

@jeremydmiller

Build a Help Desk sample application on Polecat + Wolverine, as the SQL Server counterpart to the Marten + Wolverine version.

Why

A Help Desk application is a good showcase for event sourcing — a genuinely stateful entity with a rich lifecycle, projections that people can recognise, and natural concurrency concerns. Having the same application implemented on both Marten (PostgreSQL) and Polecat (SQL Server) makes the store-level differences legible without changing the domain, which is far more instructive than two unrelated samples.

What it should cover

Mirror the Marten + Wolverine version as closely as the two stores allow:

  • the same event sourced Incident aggregate and lifecycle
  • the same projection set — single stream for details, multi stream with a custom grouper for the per-customer summary
  • inline and async projections side by side
  • optimistic concurrency through the HTTP layer
  • Wolverine for command handling and messaging
  • Alba based integration tests

Where the two genuinely diverge, that divergence is the interesting part and worth calling out in the README rather than papering over.

Context

Marten's own in-tree Helpdesk sample was retired in marten#5069, and Marten's docs now point here for end to end samples.

Pairs with the Marten + Wolverine version of the same application.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions