Full-Stack Java

MasakJerr!

A full-stack recipe management application for managing recipes and user data with Java, JSP/Servlets, and MySQL.

Java JSP/Servlets MySQL

View Code

Project Type Full Stack

My Role Backend Engineer

Status Archived

Overview

MasakJerr! is a recipe management platform designed to help users organize, share, and discover culinary creations. It demonstrates full-stack development patterns through recipe CRUD (Create, Read, Update, Delete) workflows backed by MySQL.

Key Features

Recipe Management (CRUD)

Users can seamlessly create new recipes, upload instructions, update ingredients, and delete entries from their cookbook.

Data Persistence

Reliable and normalized data storage using relational mapping against a MySQL database.

User Profiles

Registration and login flows to keep user data isolated and private.

Java Web Backend

Uses Java Servlets for request processing and business logic, JSP pages for the web interface, and MySQL for persistent data storage.

System Architecture Pipeline

Full-stack MVC recipe persistence pipeline managing user authentication, CRUD operations, ingredient normalization, and relational storage.

Authenticated Recipe Persistence Pipeline

Java 17 JSP & Servlets MySQL 8.0 DAO Layer Tomcat

01 / Identity Tier

Registered Chef User account onboarding, personalized cookbook curation Web Browser · HTTPS

Credential Guard Session-based authentication & encrypted user credentials Stateful HTTPS Session

02 / Presentation

JSP Recipe Views Dynamic recipe builder, step-by-step cooking checklists JSTL Templates

Ingredient Form Matrix Multi-field ingredient row creation and form validation Multipart Form Handling

03 / App Controller

Servlet Logic Routing CRUD action dispatching, ownership checks & redirects HTTP Servlet API

DAO Layer & Pooling Data access objects with parameterized query mapping PreparedStatements

04 / Data Store

MySQL Relational DB Normalized recipes, ingredients, categories & tags 1:N Relational Mapping

Foreign Key Safeguards Referential constraints preventing orphaned recipe ingredients ACID Integrity Guard

Design Pattern Model-View-Controller (MVC) Strict separation of JSP presentation, servlet control, and data model

Data Security Scoped Ownership Private recipe isolation ensuring users only access their personal recipes

Schema Normalization Relational 3NF Integrity Normalized recipe-ingredient tables with automated cascading updates

Server Platform Apache Tomcat Deployment Enterprise servlet runtime with reliable connection pooling