# Quick start

> Make your first map, connect it, give it some traffic and test it on Black Friday, in about five minutes.

This page takes you from an empty map to one you’ve tested on Black Friday. If you’d rather look around first, open a [template](https://docs.flozu.app/guides/templates.md) instead.

## Make a map

1. Open Flozu. You land on **home**: one box with your latest maps and the ways to start one.

2. Select **New map**. A blank map opens in the editor, with the parts library on the left and the inspector on the right.

   > **Tip**
   >
   > On an empty map, **Open an example** draws a shop’s checkout for you to look around.

3. Give the map a name. With nothing selected, the inspector shows the map itself: type its name under **About**.

## Add parts

1. Press `P` with the pointer over the canvas. A **Person** appears where the pointer is. Every kind of part has a key like this, shown beside it in the library.

2. Drag **Client app** from the library onto the canvas, to the right of the person.

3. Press `S` to add a **Service**, then `D` to add a **Database** to its right.

4. Double-click a part’s name to rename it. Call the service “Orders API” and the database “Orders DB”.

## Connect them

1. Drag from the port on the right edge of the person to the client app. Near another part’s port, the line snaps to it inside a soft orange ring, so you don’t have to hit the port exactly.

2. Connect the client app to Orders API, and Orders API to Orders DB.

3. From Orders API, drag a line out and let go on empty canvas. Flozu asks what comes next and suggests parts that usually follow a service. Pick **Queue**, and it’s added already connected.

![Dropping a line on empty canvas opens a small search, here narrowed to Cache by typing.](https://docs.flozu.app/_astro/quick-add-light.CjYtG6cl_1JhTVg.webp)

_Let go of a line on empty canvas, or double-click it, to add a part._

## Give it traffic

A map comes alive once it knows its numbers.

1. Select the line from the client app to Orders API. In the inspector’s **Traffic** tab, set its rate to 200 requests a second.

2. Select Orders API. In its **Traffic** tab, set its capacity to 400 a second: what it can process.

3. Press play on the island at the foot of the canvas if the map is paused. Dots now move along each line, closer together where there’s more traffic.

Why those numbers? 200 a second into a part that can take 400 means it’s half busy on a normal day: room to spare. The rate is always the busiest moment of a normal day, so a scenario can scale it up from there. You don’t need every number to start. The rates where traffic comes in and the capacity of the part you’re worried about are enough.

## Test it on Black Friday

1. Open the mode menu on the island at the foot of the canvas and choose **Scenario**.

2. In the scenario panel, pick **Black Friday**. Flozu plays a whole day with a rush at midnight and four times today’s traffic after it.

3. Read **What happens**. Orders API is outlined in red: just after midnight, nearly 1,500 requests a second arrive, and it can take 400. Under **Fix it**, Flozu says to give it about 2,100 a second, five times what it has, or run 6 copies.

4. Select **Apply** to make that fix, and the red outline goes. One undo takes it back.

![Black Friday running on the checkout map: the scenario panel lists two parts that need more room, the email worker is outlined in red, and a timeline runs along the bottom.](https://docs.flozu.app/_astro/scenario-light.D50hHthp_2r0uL7.webp)

## Next steps

- [Will it survive Black Friday?](https://docs.flozu.app/walkthroughs/black-friday.md) does the same on a fuller shop, where the part that breaks first isn’t the one you’d guess.
- [Take the tour](https://docs.flozu.app/start/tour.md) to learn what each part of the editor does.
- [Sort your maps into projects](https://docs.flozu.app/guides/your-maps.md) as you make more.
- [Present the map](https://docs.flozu.app/guides/presenting-and-sharing.md) to someone, or send them a link.