Eine Implementierung eines hybriden logischen Uhrwerks in Dart, basierend auf dem Paper "Logische physikalische Uhren und konsistente Schnappschüsse in global verteilten Datenbanken".
Aus öffentlichen Paketdaten erstellte Orientierung.
HLC_Dart ist eine Dart-Implementierung eines hybriden logischen Uhr (HLC), die dazu entwickelt wurde, kausal konsistente Zeitstempel in verteilten Systemen bereitzustellen. Inspiriert durch den Artikel über logische physikalische Uhren kombiniert es die Vorteile von logischer und physischer Zeit, um starke Konsistenz in weltweit verteilten Datenbanken sicherzustellen. HLC_Dart ermöglicht eine präzise Ereignisreihenfolge unter Beibehaltung der Synchronisation mit der realen Weltzeit und ist daher ideal für CRDTs und verteilte Ledger. Das Paket unterstützt mehrere Plattformen wie Android, iOS, Web, macOS, Windows und Linux.
Anwendungsfälle
Verteilte Datenbank-Zeitstempelung
CRDT-Konfliktlösung
Globale Ereignisreihenfolge in Microservices
Konsistente Snapshots in replizierten Systemen
Echtzeit-Kollaborationsanwendungen
Hauptmerkmale
Hybride logisch-physikalische Zeitabstimmung
Kausale Konsistenz über Knoten hinweg
Niedrige-Latenz-Zeitstempel-Erzeugung
Plattformübergreifende Unterstützung
Integration mit CRDTs
Geeignet für
Entwickler, die verteilte Systeme entwickeln
Teams, die CRDTs für Datenkonsistenz verwenden
Anwendungen, die eine globale Ereignisreihenfolge erfordern
Backend-Dienste in Multi-Region-Deployment
Hinweise
Erfordert sorgfältige Behandlung von Uhrdrift
Nicht geeignet für Anforderungen an hochpräzise Zeitmessung
Abhängig von genauen Systemzeitquellen
Kann im Edge-Fall Netzwerk-Koordination erfordern
Am besten in Umgebungen mit stabiler Netzwerkverbindung einsetzen
Original-README
Originaler README-Schnappschuss aus dem verknüpften Quell-Repository. Aktuelle Inhalte finden Sie im Repository.
A roadmap is available in the project page. The roadmap provides a high-level overview of the project's goals and the current status of the project.
Workspace structure
This repository is a workspace that contains multiple packages and apps.
Consistency is granted by the melos tool.
Melos
Melos (pub.dev)
is a CLI tool for Dart/Flutter monorepos. It links the local packages together,
so every package can depend on the others without publishing them first, and it
runs the same command over all of them (format, analyze, test, publish, ...).
Every shared command lives in melos.yaml and runs with
melos run <script>:
Script
What it does
format
formats the code (80 characters per line)
analyze
runs the analyzer with warnings and infos as errors
test / test_flutter / test_chrome
runs the Dart, Flutter and web tests
benchmark
runs the benchmarks of every package with a benchmarks/ folder
devtools_build
builds the DevTools extension
docs_bs / docs_build
bootstraps and builds the documentation site
update_references
propagates package/app references into the READMEs
Setup
The Flutter SDK is pinned with fvm, and the documentation
site is a Docusaurus project, so Node.js (with
npm) is required too.
fvm install # installs the pinned Flutter SDK
fvm dart pub get # resolves the workspace tools (melos included)
fvm dart run melos bootstrap # links the packages and prepares the examples
fvm dart run melos run docs_bs # optional: installs the documentation site (needs Node.js)
Note
Melos is a dev_dependency of the root pubspec.yaml, so
running it as fvm dart run melos ... is the safest option: you use the melos
version pinned by this repository, with the Flutter/Dart SDK pinned by fvm.
A globally activated melos (dart pub global activate melos) works as well,
but it may be a different version than the one the workspace expects, and the
difference usually shows up at the worst possible moment 🙃.
A command is provided to try to publish all packages:
fvm dart run melos publish --dry-run
This ensures that every package is formatted, analyzed, tested and built.
Organization
The repository structure is organized as follows:
workspace/├──melos.yaml# melos configuration file├──packages/# contains every package of the workspace│├──core/# the CRDT engine and its bindings││├──crdt_lf/│││├──lib/│││├──example/│││└──flutter_example/││└──.../│├──adapters/││└──persistence/# storage backends for crdt_lf││├──crdt_lf_drift/││├──crdt_lf_hive/││└──crdt_lf_sqlite/│└──_internal/# private, unpublished packages│├──benchmark_infrastructure/│└──shared_examples_infrastructure/├──apps/# contains the applications built on top of the packages│└──greyhound_markdown/│├──client/│└──server/├──docs/# the documentation site (Docusaurus, Node.js project)├──scripts/# dart scripts used by the melos commands└──assets/# contains the assets used in the documentation└──.../
VS Code
If you work with VS Code, the repository already contains a
.vscode folder with:
the recommended extensions (Dart, Flutter, Melos, Mermaid);
the settings (fvm SDK path, project dictionary for the spell checker);
the launch configurations for the apps and the examples;
the snippets used in the READMEs and the changelogs.
Accepting the recommended extensions gives you the smoothest experience on this
workspace.
Contributing
Contributions are welcome: bug fixes, new features, documentation, performance
work, or anything else — a fixed typo counts too 💚.
The whole flow (roadmap, issues, pull requests, AI-assisted work) is described
in CONTRIBUTING.md. Please read it before opening an issue
or a pull request.