<aside> 👀 First: let's review the requirements to follow the workshop

</aside>

To explain how you might approach Fluence at the hackathon, let me start with analogy.

How to build a (web) app

Imagine we want to build some kind of simple chat. It allows to add users, add messages, and query that data. It also implements simple in-chat command like /duckduckgo what is homotopy

Write a backend with API

- add_user(User { name: string, id: string })
- get_users()    → [User]

- add_message(msg: string, auth: bool)
- get_messages() → [Message]

- query_url(url) → String or Error

Write frontend

• button: add user ⇒ API.add_user
• text field: send message ⇒ API.add_message
• list area: get_users + get_messages
• /duckduckgo ⇒ API.query_url(http://api.duckduckgo.com/...)

Why build that yourself? Reuse!

• You're not the first human to store list of users and messages
• Someone definitely had implemented that before
• These service may be even running somewhere idling!
• Wouldn't it be nice to reuse code or even running services (with state/user base)?
• Even so... How to compose different services from different vendors and keep it simple?

Let's reflect on that question for a moment. And while we do...