Draft: Layered Model of Singer #30
Open
Conversation
This file contains 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
visch
reviewed
Feb 22, 2022
| - Focus on the std-out portions of using Singer (serialization format, message types, required keys for messages, etc.) | ||
|
|
||
| #### Layer 2: Standards | ||
| The pieces that systems using Singer can rely on such as catalogs and discovery mode. These pieces required to implement to be considered as up to modern standards for Singer. Not implementing these is not an incompatibility, but all Singer actors should strive to implement the standards. The standards are more focused upon Singer actors themselves themselves (e.g., taps, targets), as opposed to the over-the-wire protocol at the heart of Singer. Some tooling that rely on these standards may not function if an actor does not implement it. |
visch
reviewed
Feb 22, 2022
| Principles: | ||
| - Specific to a particular vertical or market space | ||
| - Specific to a single ops approach for deployment or other closer-to-the-metal conecerns | ||
| - Not generalizable without either losing value in the source product |
There was a problem hiding this comment.
This sentence I'm a little lost on but I get the general idea. Maybe
Not generalizable without losing value in the Tooling/Orchestration/UX/Infrastructure
Or just
Not generalizable
🤷 , need to work on my writing more anyways so you probably have a better idea (overall this writeup is great and easy to understand)
There was a problem hiding this comment.
Ah, yup heh. I think I wanted to keep some space for closed source and/or proprietary pieces to be at least categorized here, but The intro probably explains that well enough. I like just "Not generalizable".
Co-authored-by: Taylor A. Murphy <taylor@meltano.com>
Co-authored-by: Taylor A. Murphy <taylor@meltano.com>
|
@dmosorast - Nit here: do you mind adding .md file suffix for markdown formatting? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the official proposal for the Working Group's adoption of the Layered Model of Singer proposal as represented in Issue #19 per the proposed SIP approval process.