DEV Community

Divya
Divya

Posted on

πŸš€ Building for Impact: Our Journey at Guidewire DevTrails Codestorm Hackathon

Hackathons are often about speed. But the Guidewire DevTrails University Hackathon – Codestorm pushed us to focus on something deeper β€” building solutions that actually make sense in a real-world insurance environment.

Instead of just coding for the sake of submission, we focused on practicality, scalability, and clarity.

πŸ’‘ Problem-First Thinking

Most hackathon teams jump straight into tech. We didn’t.

We started by asking:

What real problem are we solving?
Who is the end user?
Can this solution actually scale?

This shifted our mindset from β€œbuild something cool” β†’ β€œbuild something useful.”

πŸ—οΈ System Architecture

We designed the system using a layered architecture approach to keep things modular, scalable, and easy to maintain.

πŸ”Ή High-Level Architecture
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Client (User) β”‚
β”‚ Web UI / Input Forms β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Presentation Layer β”‚
β”‚ (HTML / JSP / UI) β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Controller Layer β”‚
β”‚ (Servlets / Handlers) β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Business Logic Layer β”‚
β”‚ (Validation / Rules) β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Data Access Layer β”‚
β”‚ (DB Utils / Queries) β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Database β”‚
β”‚ (Logs / User Data) β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
πŸ” Architecture Breakdown

  1. Presentation Layer

Handles user interaction
Collects inputs like file name and password
Displays system responses

  1. Controller Layer

Acts as the bridge between UI and backend
Processes incoming requests
Routes them to appropriate logic

  1. Business Logic Layer

Core of the system
Validates authentication
Applies rules for secure access
Decides whether to allow or deny operations

  1. Data Access Layer

Manages communication with the database
Handles queries for logs and authentication data
Ensures separation between logic and storage

  1. Database Layer

Stores log files and access records
Maintains security audit trails
βš™οΈ Key Design Decisions
Layered separation β†’ easier debugging and scaling
Authentication-first design β†’ security as priority
Modular components β†’ reusable and maintainable code
Clear data flow β†’ predictable system behavior
πŸ› οΈ Implementation Highlights
Structured Java-based backend
Clean separation of concerns
Secure validation for file access
Logging mechanism for tracking attempts

πŸ”— GitHub Repository:
https://github.com/deiepak/Guidewire_Devtrails_University_Hackathon_Codestorm

🀝 Team Execution

We didn’t waste time overplanning.

Divided work early
Focused on execution
Fixed issues fast instead of overthinking

That’s what made the difference.

Top comments (1)

Collapse
 
ayush_kumar_420ae5395a8af profile image
Ayush Kumar

Creative concept, smooth implementation, impactful outcome