Welcome

Have you ever looked at some code and wondered what on earth were they thinking?

Why did you code it in that way?

Why not use library x? Why not use pattern y?

I think I've found a fix for that...

Over the next 8-12 weeks we're going to build an "Event Ticket Platform". This app let's organizers create events and sell tickets, event goers buy those tickets and the system handles the whole ticket QR code scanning at the event.

This is usually where I'd show you clips of the fanciest bits the finished app, but here's the thing -- the app's not built yet.

We've got a project brief, you can grab that PDF from Discord too, but that's it -- but fear not, that's what we want!

This build is going to be a bit more raw than my previous builds, as I'll be taking you through the build, as I build it.

No safety net, we're all in.

Without the benefit of foresight, We'll likely have to rework some stuff as we go, but as a result you'll get to see my real, as-it-happens, build thought process -- the good, the bad and the ugly.

Build Plan

Here's the plan for this build. It's likely to change as we learn more about the domain, but here's today's understanding:

1. System Design - Analyze the domain, user personas, UI Design and domain modelling That's this video.
2. Design REST API and the application's architecture
3. Project Setup, including Security
4. Domain Implementation
5. Event Creation & Management
6. Ticket Sale & Purchase
7. Ticket Validation
8. Sales Reporting

Prerequisites

That's the plan, we'll see how we get on, so let's cover the prereqs for this build.

This is going to be in the intermediate build territory, and as we're on a time limit we'll need to focus on the build and can't make too many diversions cover theory in-depth.

As a result, you should already be comfortable with:

• Java
• Spring Boot
• Spring Security

Have a basic understanding of:

• OAuth2 and OpenID connect
• React + npm

Source Code

This build will be focused on the Spring Boot backend and I'll be uploading the source code to Discord.

As an app isn't complete without a UI, I will also be building a React frontend for this build and uploading the source code to Discord too, so you can download it.

I'll not include how to code the react app in this series, but if you're interested in that, I'll be posting some details to the community on how to access it soon.

Getting Support

If you have questions or get stuck at any point during this build, there's a whole community of Developers, and dedicated help channels in Discord.

Right, with that covered, let's jump into system design.