Mssql-changefeed Alternatives

Similar projects and alternatives to mssql-changefeed

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better mssql-changefeed alternative or higher similarity.

mssql-changefeed reviews and mentions

Posts with mentions or reviews of mssql-changefeed. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-14.
  • How to Listen to Database Changes Using Postgres Triggers in Elixir
    10 projects | news.ycombinator.com | 14 Jun 2023
    We made mssql-changefeed for this purpose:

    https://github.com/vippsas/mssql-changefeed

    V1 requires to run a sweeper procedure in the background, but an upcoming v2 version does without the sweep loop. Unfortunately too fresh for readme to be updated, but relevant lines in tests to show it off:

    https://github.com/vippsas/mssql-changefeed/blob/v1-lazy/go/...

    https://github.com/vippsas/mssql-changefeed/blob/v1-lazy/go/...

    https://github.com/vippsas/mssql-changefeed/blob/v1-lazy/go/...

    Library itself:

    https://github.com/vippsas/mssql-changefeed/blob/v1-lazy/mig...

  • Push-Based Outbox Pattern with Postgres Logical Replication
    6 projects | news.ycombinator.com | 28 Oct 2022
    Not OP, but there is an approach here of using a dedicated loop worker to assign post-commit ID sequence. I.e. using the outbox pattern once, simply to assign a post-commit ID.

    https://github.com/vippsas/mssql-changefeed/blob/main/MOTIVA...

    I wish DBs had this more built in, it seems a critical feature of a DB these days and the commit log already have very similar sequence numbers internally...

  • The Next Generation of Materialize
    9 projects | news.ycombinator.com | 3 Oct 2022
    We do something similar, but in 2), instead of using the outbox pattern, we make use (in several different settings) of integers that are guaranteed to increment in commit order, then each consumer can track where their cursor is on the feed of changes. This requires some more coordination but it means that publishers of changes don't need one outbox per consumer or similar.

    Then you can have "processes" that query for new data in an input table, and update aggregates/derived tables from that simply by "select * ... where ChangeSequenceNumber > @MaxSequenceNumberFromPreviousExecution"...

    The idea here implemented for Microsoft SQL for the OLTP case:

    https://github.com/vippsas/mssql-changefeed

  • A note from our sponsor - InfluxDB
    www.influxdata.com | 4 May 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic mssql-changefeed repo stats
4
14
6.6
5 months ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com