Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
cressie176 authored Jan 26, 2024
1 parent afcc697 commit 966fd61
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,8 @@

The easiest way to explain Filby is that it's like source control for reference data.

- In systems like git, you have a commit log, comprising a sequence of commits. Each commit is uniquely identified by a commit hash, and typically bundles related source code changes (but doesn't have to).
- With Filby, you have a change log, comprising a sequence of change sets. Each change set is uniquely identified by an id, and typically bundles related reference data updates (but again, doesn't have to).<br/>
- In systems like git, you have a commit log, comprising a sequence of commits. Each commit is uniquely identified by a commit hash, and typically bundles related source code changes. <br/><br/>
- With Filby, you have a change log, comprising a sequence of change sets. Each change set is uniquely identified by an id, and typically bundles related reference data updates

Like checking out a commit, your applications can use the Filby API to retrieve a desired set of reference data for a given change set id. They can also inspect the changelog to find which change set was in effect at a given point in time, and be notified when the reference data they are interested in changes.

Expand Down

0 comments on commit 966fd61

Please sign in to comment.