glossary
glossary copied to clipboard
Add new term: 'Event Streaming'
Issue #346
Deploy Preview for cncfglossary ready!
| Name | Link |
|---|---|
| Latest commit | 75f168c65f5af82d7332b23d55d73f42433ddd17 |
| Latest deploy log | https://app.netlify.com/sites/cncfglossary/deploys/632c2aef7487be00080db956 |
| Deploy Preview | https://deploy-preview-1065--cncfglossary.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Sorry for the delay. I went ahead and implemented the changes.
Never noticed the feature to signoff and commit in GitHub before. Pretty nifty. The text looks accurate. If anyone has any comments, let me know!
@jasonsmithio I am afraid to say that the content IMHO is not accurate enough yet. I made some suggestions but basically my impression is that you described a lot more what would fit to the term Event Driven/Eventing/Message driven architecture. The focus of Event Streaming is not on decoupling. Using a Message Queue decouples an architecture as well, but what is unique about Event Streaming (in contrast to Event messaging).
I am super happy to hear other opinions here :) @JasonMorgan @seokho-son @jihoon-seo
I agree with the opinion from @iamNoah1 .
There are several terms related with event streaming. These terms are more fundamental concepts, and I think event streaming is a special instance (implementation) of these concepts.
- Event-driven architecture
- Pub/Sub model (for message, event, or ...)
- Microservice
- ...
I think event streaming can be categorized into an event-driven architecture.
Also, the structure of event streaming is based on Pub/Sub model (or pattern). I think we don't have to introduce microservices in this definition.
A system based on Publish/Subscription model can be implemented to handle either event or message.
And, event streaming is a kind of implementation of a Publish/Subscription model for sequences of events (not for just an event).
Compare to a event-driven architecture (which is a general concept related with event-based decoupling), event streaming is focused on providing multiple categorized sequences of events ordered by time based on pub/sub model so that subscribers (consumers, microservices, ...) can utilize or process the ordered set of events.
@jasonsmithio, let me know when the technical feedback has been woven in, and we are ready for the editing round.
@jasonsmithio, let me know when the technical feedback has been woven in, and we are ready for the editing round.
Should be good to go. I added some technical feedback and approved a lot of the suggested edits.
Not seeing any updates. Could it be that you didn't commit yet, @jasonsmithio?
Not seeing any updates. Could it be that you didn't commit yet, @jasonsmithio?
I accepted edits in the UI. Maybe I should pull it down and reupload?
Not seeing any updates. Could it be that you didn't commit yet, @jasonsmithio?
I accepted edits in the UI. Maybe I should pull it down and reupload?
@jasonsmithio I guess the suggestions were applied. Still the article is not accurate enough. I mean you realized yourself that the focus should be on streaming and not on event driven per se. Please try to rework the respective passages and keep the provided feedback in mind.
Not seeing any updates. Could it be that you didn't commit yet, @jasonsmithio?
I accepted edits in the UI. Maybe I should pull it down and reupload?
@jasonsmithio I guess the suggestions were applied. Still the article is not accurate enough. I mean you realized yourself that the focus should be on streaming and not on event driven per se. Please try to rework the respective passages and keep the provided feedback in mind.
I made some changes
@jasonsmithio I don't know what exactly you did since the last change but now there are a lot of commits that should be here. Maybe rebased against the wrong branch? Please try to fix that :) Thanks
Howdy,
Will try, any quick tips?
@jasonsmithio I don't know what exactly you did since the last change but now there are a lot of commits that should be here. Maybe rebased against the wrong branch? Please try to fix that :) Thanks
Howdy,
Will try, any quick tips?
I would try to revert the last action. I don't know what you did exactly. As last resort save the changes you did and hard reset to the latest remote commit from your branch. Then reapply.
I believe I fixed the rebasing
Made the change but spellcheck doesn't like the term TCP
Regarding the spellcheck, you just have to add the word to the wordlist: https://github.com/cncf/glossary/blob/main/wordlist.txt
Not sure where we are at. Please let us know when it's ready for review — thank you!
Howdy,
I did a push a few days ago with some language changes.