Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workshop topics #4

Open
Barbanio opened this issue Apr 30, 2021 · 14 comments
Open

Workshop topics #4

Barbanio opened this issue Apr 30, 2021 · 14 comments

Comments

@Barbanio
Copy link
Contributor

Hello! @smoya and I have opened this issue so that to know opinions about the workshops. We want to create these seminars to introduce AsyncAPI to potential users and improve the knowledge of people who already know the specification and want to improve it.

For this, we need the opinion of the community especially on these points:

  1. To which communities we can offer the workshops.
  2. Companys or groups that might be interested in this.
  3. Themes that would be interesting for these workshops.
  4. And anything else you can think of regarding the workshops.

Here is the summary document of the information we have collected so far on the workshops: https://docs.google.com/document/d/1qfDGhRI07vO6ZydYYRFRk6B9PyYr2oUU/edit#heading=h.gjdgxs

Feel free to post your interests :)

@Barbanio Barbanio transferred this issue from another repository Apr 30, 2021
@github-actions
Copy link

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.

Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@jpgough
Copy link

jpgough commented Apr 30, 2021

If I was looking to create a workshop on Async I think I would look at the following agenda (which reflects a little bit on what I'd like to learn):

Session 1 Taught - Hello Async

  • Introduction to event driven architecture essentials
  • Demonstrating event driven architecture using a WebSocket/simple example accessible in a range of languages e.g. these blog posts are really good
  • What are the problems that AsyncAPI is trying to solve? Demonstrate by how difficult it is to find out what the application does from a consumer perspective and how AsyncAPI helps to solve this
  • Introduce AsyncAPI

Lab 1 - Hello

  • Create an AsyncAPI using VSCode Tooling?
  • Generate code in language comfortable with to look at hello world

Session 2 Taught - Specification Deep Dive

  • Core components of the specification
  • Modelling Channels
  • Defining Servers and Security Concerns

Lab 2 - Dynamic Todo List

  • Set out the requirements for a Todo list application for a team of developers
  • Consumer can send in a todo item and other clients get the response
  • Possibly provide a UI that can hook into the local service to make this quite visual for workshop participants
  • Host a sample solution on cloud to show both the power of async and the power of specifications

Other topics I'd then try to curate into a final session (but this is where I'm still learning myself would be):

  • Tooling
  • Participating in the community
  • Supporting an additional protocol to WS used in Lab 1 & 2

@smoya
Copy link
Member

smoya commented May 4, 2021

@jpgough It looks pretty promising!

I'm wondering if the Todo List is a good exercise for showing how an event-driven app works. Would you mind sharing more details?
I've seen simple chat applications as the default example in many workshops or demos of event-driven apps, but I have no preference of course!

@jpgough
Copy link

jpgough commented May 5, 2021

@smoya that's a good question and I think we can play around with the lab session that really helps us get to the points we want to prove out. In terms of the todo application I was thinking of a scenario where:

  • There is a shared team todo list (maybe a bit like GitHub issues)
  • Creating an issue notifies other team members
  • Team members can comment on an issue (possibly react to an issue)
  • Team members can add comments on an issue

I will put together a more detailed proposal on the above soon, but let me know if you think this might work. It actually sounds quite like a chat application 😄 - but I guess there's a bit of a dynamic nature to the channels.

@fmvilas
Copy link
Member

fmvilas commented May 10, 2021

I just created a repo for us to collaborate on the workshops content: https://github.com/asyncapi/training.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

@smoya
Copy link
Member

smoya commented Jul 12, 2021

Shall we move this issue to https://github.com/asyncapi/training? cc @Barbanio @fmvilas

@Barbanio
Copy link
Contributor Author

I think it makes sense, right?

@fmvilas fmvilas transferred this issue from asyncapi/community Jul 12, 2021
@fmvilas
Copy link
Member

fmvilas commented Jul 12, 2021

Done :)

@Barbanio
Copy link
Contributor Author

Barbanio commented Dec 7, 2021

@all-contributors please add @Barbanio for eventOrganizing, ideas

@allcontributors
Copy link
Contributor

@Barbanio

I've put up a pull request to add @Barbanio! 🎉

@allcontributors
Copy link
Contributor

@Barbanio

I've put up a pull request to add @siham! 🎉

@Barbanio
Copy link
Contributor Author

@all-contributors please add @Sihamtahi for review

@allcontributors
Copy link
Contributor

@Barbanio

I've put up a pull request to add @Sihamtahi! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants