PartyTime: Building a Secure and Simple Event Hosting API

Hey there! 👋

Let’s dive into PartyTime, a project I built to create a secure, simple backend for an anonymous event hosting platform.

Why I Built PartyTime 🤔

• ASP.NET and PostgreSQL were my tech choices for this project.
• The focus was on backend development, as I’ve worked a lot on frontend in the past.
• I wanted to explore security and backend concepts in more depth.

Security: Keeping Things Safe 🔐

Security is key! Here's how I kept PartyTime secure:

• HTTPS for encrypted communication.
• Passwords are hashed using SHA-256 and salted to protect against common attacks.
• I used JWT (JSON Web Tokens) for authentication and authorization.

Simple Architecture for Flexibility 🏗️

• Monolithic architecture for simplicity. The system has two main parts: Users and Events.
• Keeps things manageable and easy to scale.

API Routes & Features 🚀

PartyTime’s API is built for simplicity:

• Users can create, log in, and delete their own account.
• Admins can manage users.
• Events can be created, updated, and deleted by authorized users.

Why Backend Development? 💡

I chose to focus on backend security over frontend features. This allowed me to dive into new areas like JWTs and secure database management.

Even though it’s not perfect, I’m proud of how PartyTime turned out. It’s a solid backend that can grow over time.

Final Thoughts 💭

Building PartyTime wasn’t just about code—it was about creating something secure and reliable. This project helped me level up my skills in backend development and API security.

I’m excited to continue building and learning. 🚀