Kevin's Easy-to-Understand Spring Reactive Web Applications: Reactor Part 2
Reactor, one of the core technologies of Spring WebFlux-based reactive applications, and Reactor Operator, which can be said to be the most important part of Reactor, if you want to make it yours, take the `Kevin's Easy-to-Understand Spring Reactive WebApplications: Reactor Part 2` lecture.
355 learners
Level Basic
Course period Unlimited
･
Edited
📢 Announcement: OpenClaw.AI Basics Part 2.5 Lecture Now Open
📢 OpenClaw.AI Basic Part 2.5 Course Opening Announcement
Hello, I'm Kevin, the instructor for the OpenClaw.AI Master Class basic course.
I am finally posting an announcement as [Basic Part 2.5] Fundamentals of Multi-Agent Team Design and Role Separation has been released on Inflearn. :)
This Part 2.5 further expands the "AI Assistant in my PC" created in Parts 1 and 2,
This is a lecture focused on growing a single Telegram bot into a small AI team with divided roles.
👉[Go to OpenClaw.AI Basics Part 2.5 Lecture]
What we will build together in Part 2.5
- Using Telegram Forum Groups + Topic-based Routing
We will configure a multi-agent environment that operates two agents, content-planner and content-editor, with a single bot.
- To the /workspace/content/planning / /workspace/content/drafts folders
We will actually create a content workflow where planning deliverables and draft/edited versions are separated.
- Through the scenario of "generating ideas and outlines in the planner room → refining the writing in the editor room," we will complete a realistic multi-agent collaboration routine based on manual copy-pasting.
Especially recommended for these people
- Those who have followed OpenClaw Parts 1 and 2 but are still making a single agent do everything
- Those who want to develop a Telegram bot not just as a "single chatbot," but as an AI team divided into a Planner and a Writer/Editor
- Solo creators, newsletter/blog operators, and YouTubers who want to organize their workflow by delegating content planning, drafting, and refining tasks to role-specific agents.
- Developers, planners, and PMs who are interested in multi-agents but want to start light in their current OpenClaw + Telegram environment instead of using a massive framework
Part 2.5 Core Curriculum at a Glance
- Section 1: For both existing and new students
Part 2.5 Joining Route A (5-minute environment check) / B (Minimum setup onboarding) Guide + Super simple review of OpenClaw UI
- Section 2: Single-agent vs. Multi-agent concepts,
Understanding the structure of how multiple agents are deployed within openclaw.json, and checking the current configuration with openclaw agents list
- Section 3:
- Define content-planner / content-editor agents
- Separate workspaces for /content/planning and /content/drafts
- Telegram forum group & planner-planning / editor-editing topic creation
- Find Group ID / Topic ID → Complete agent routing by topic
- Section 4:
- planner ↔ editor semi-manual collaboration practice (based on human copy-paste)
- Preview of the 4-agent automated collaboration pipeline (Leader/Planner/Editor/QA) to be covered in Part 3
Checklist before taking the course
- It is best if you have the WSL2 + Docker + OpenClaw + Telegram Bot environment used in Parts 1 and 2 ready.
- Even if you haven't taken Parts 1 and 2, I have structured it so that you can set up the minimum environment required for the multi-agent practice by following the “Environment Check Route A / Minimum Setup Onboarding Route B” included in Part 2.5.
- You will need a Gemini API key issued by Google AI Studio.
If you have any questions or get stuck while taking Part 2.5, please feel free to leave them on the Q&A board at any time.
Based on your feedback, we will continue to strengthen the practice examples and troubleshooting guides.
I hope this Part 2.5 serves as an opportunity to expand your OpenClaw environment from "one smart assistant" into a "small AI team with divided roles."
Thank you.