Architectural Katas

What Is a Kata?

An architectural kata is a practice exercise in software design. You get a short brief for a system that does not exist yet, and you work out an architecture that could serve it.

Nobody writes code. The design stays on paper or a whiteboard, along with the reasons behind each choice.

What a Kata Asks of You

A brief says what a system must do, but it never says how to build it. Working that out is up to you, and it means you have to:

None of these has a correct answer, only trade-offs. Every choice makes something easier and something else harder.

Katas usually run in small groups, because a design nobody questions teaches you little. Someone at the table will ask why you made a choice, and the answer has to be a reason the others can follow. Often the question exposes an assumption you did not know you had made.

What a Brief Looks Like

A brief describes a situation, names its users, and lists numbered requirements. It also leaves things out on purpose, and the questions you ask about those gaps shape the design as much as the stated needs.

The Show Must Go On!

Description

A team of organizers runs a large annual technology conference, bringing together thousands of developers, technology professionals, and industry experts.

Each year features a new lineup of speakers, talks, and activities. The organizers need a platform to manage the conference, keep attendees informed, and support interactions between speakers and participants.

Early-bird ticket sales open in three months.

The platform must also maintain an archive of previous editions, allowing visitors to explore past schedules, speakers, and presentations.

Users

  • Thousands of attendees
  • Hundreds of speakers
  • Dozens of staff

Requirements

  1. Conference Management

    Organizers and speakers can manage talks, schedules, room assignments, and conference information.

  2. Attendee Engagement

    Attendees can explore the program, interact with talks, provide feedback, and receive important updates.

  3. Conference Archive

    Visitors can explore previous editions, including their programs, speakers, and presentations.

  4. Mobile Accessibility

    All capabilities must be usable on mobile devices, including during the conference.

  5. Reliability

    The platform must remain useful during periods of high demand and unreliable venue connectivity.

Three gaps stand out in this one. None of them looks important until you try to draw the design:

The brief will not settle any of them for you. Whether the platform sells tickets, for instance, decides whether payments are part of your design at all, and whether they have to work within three months.

The requirements it does state still leave you choices, and each one has a cost. Reliability asks the platform to stay useful when the venue’s connection is unreliable.

Picture attendees checking the schedule on their phones while the venue Wi-Fi struggles. Keeping a copy of the schedule on each phone means they can still read it, but every room change then has to reach all of those copies.

Why Practice Matters

Most engineers design a system from scratch only a handful of times in their career. With so few chances, there is little room to build the judgment a new design takes.

A kata lets you practice as often as you like, and none of it touches production. When an idea does not hold up, nobody gets paged and no customer notices. That leaves you free to try the option you would never risk on a real project.

Where Katas Come From

The word comes from the martial arts, where a kata is a set sequence of movements performed as an exercise. Each sequence simulates defense and counterattack against imaginary opponents.

Ted Neward applied the idea to software architecture. He created architectural katas because software architects need a chance to practice being architects, just as programmers practice programming.

The katas started as a workshop he presented. His site, architecturalkatas.com, now holds the rules, a large selection of briefs, and guidance on running a kata yourself.

Trying It Yourself

To try one yourself, work through this same brief with a small team, from the first read to a design you can present to others. Along the way, you’ll capture what you decide with decision records, release timelines, and diagrams.

Work through the brief