docs(profile): describe stream-layers tier as a solid peer (figure + text + in-flight PRs)#10
Open
estebanzimanyi wants to merge 4 commits into
Open
Conversation
estebanzimanyi
force-pushed
the
docs/stream-readiness-findings
branch
4 times, most recently
from
c4e9bfa to
dbb22e5
Compare
estebanzimanyi
changed the title
… longer dashed State the present-state facts about the stream-layers tier: - The same edge-to-cloud model runs on the streaming side, each tool in its canonical role (MobilityNebula edge / MobilityKafka transport / MobilityFlink cloud). - The published reference architecture is the MobilityNebula EDBT 2026 paper; the SNCB railway data is the application demonstration. - The parity contract matches the SQL-layer one — the same BerlinMOD reference queries across all three platforms in three streaming forms (continuous / windowed / snapshot), anchored to MobilityDB-BerlinMOD on the snapshot form. - Bindings split is JMEOS for the JVM platforms (Flink, Kafka); MobilityNebula calls MEOS directly through its C ABI. - The streaming-form scaffolds are tracked in three open PRs against the planned-tier repositories — MobilityFlink#3, MobilityKafka#1 and MobilityNebula#15 — each implementing the BerlinMOD-Q × 3-form cells in the runtime's native operator surface. Figure update: the Stream-layers box is now a solid pastel-sky peer (fill #e0f2fe, stroke #7dd3fc) matching the SQL/HTTP/Bindings boxes in shape, with a connector arrow to the MEOS core. The Stream-layers legend entry switches from a dashed swatch to the solid sky swatch. The 'PLANNED (roadmap)' framing is removed from the figure desc and section comments throughout.
estebanzimanyi
force-pushed
the
docs/stream-readiness-findings
branch
from
dbb22e5 to
63cea0b
Compare
…, MobilityKafka#2)
…21/27 + 6 partial
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describes the present-state facts about the planned stream-layers tier in the profile README:
The figure stays dashed and ghosted — the band only becomes solid when the cross-platform streaming parity is real, in line with the rest of the profile (MobilitySpark is depicted as a solid peer SQL box because it is real).
This is a text-only change to
profile/README.md; no figure or table-of-repositories edits.