Skip to content

Latest commit

 

History

History
56 lines (39 loc) · 3.22 KB

README.md

File metadata and controls

56 lines (39 loc) · 3.22 KB

Chapter 1 :: (The rise of) Platforms on Top of Kubernetes


🌍 Available in: English | 中文 (Chinese) | Português (Portuguese) | Español | 日本語 (Japanese) | French

Note: Brought to you by the fantastic cloud-native community's 🌟 contributors!


Pre-requisites for the tutorials

You'll need the tools below to follow the step-by-step tutorials linked in the book:

These are technologies and versions used when testing the tutorials.

Warning

If you want to use other technologies, like Podman instead of Docker, it is possible by turning on rootful container execution with this command

podman machine set --rootful

Conference Application Scenario

The application that we will modify and use throughout the book's chapters represents a simple "walking skeleton", meaning that it is complex enough to allow us to test assumptions, tools, and frameworks. Still, it is not the final product that our customers will use.

The "Conference Application" walking skeleton implements a straightforward use case, allowing potential speakers to submit proposals that the conference organizers will evaluate. See below the app's home page:

home

Check below how the application is commonly used:

  1. C4P: Potential speakers can submit a new proposal by going to the application's Call for Proposals (C4P) section. proposals
  2. Review & Approval: Once a proposal is submitted, the conference organizers can review (approve or reject) them by using the Backoffice section of the application. backoffice
  3. Announcement: If accepted by the organizers, the proposal is automatically published on the conference Agenda page. agenda
  4. Speaker's Notification: In the Backoffice, a speaker can check the Notifications tab. There, potential speakers can find all the notifications (emails) sent them. A speaker will see both approval and rejection emails in this tab. notifications

An event-driven application

Every action in the application results in new events being emitted. For instance, events are emitted:

  • when a new proposal is submitted;
  • when the proposal is accepted or rejected;
  • when notifications are sent.

These events are sent and then captured by a frontend application. Luckily, you, the reader, can see these details in the app by accessing Events tab in the Backoffice section.

events

Sum up and Contribute

Do you want to improve this tutorial? Create an issue, message me on Twitter, or send a Pull Request.