[go: up one dir, main page]

0% found this document useful (0 votes)
247 views3 pages

How To Prepare For Code Clash - Mini Hackathon

code clash prograaming docs

Uploaded by

bhuvan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
247 views3 pages

How To Prepare For Code Clash - Mini Hackathon

code clash prograaming docs

Uploaded by

bhuvan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

How to prepare for Code Clash - Mini Hackathon

We are excited to host you on Aug 31st for our 3-hour hackathon. To help you
prepare and perform your best, we have compiled some essential resources
on software architecture design.

The hackathon will be a group exercise where you will collaborate with 5 other
participants to design the architecture of an app (specific details will be
provided during the event).

Please review the following resources in order:

Application Architecture Design:

● Web Application Architecture


● Introduction to Software Architecture Patterns
Database Design:

● Database Design Basics


● Introduction to Database Modeling

API Design:

● Learn API Design


● API Design Best Practices

Diagramming Tools:

● Wireframe.cc
● Draw.io

Hackathon Process:

● The problem statement, including required functionalities, will be


shared in a document format.
● As it is an online event, you will be divided into breakout rooms of six
participants each on Zoom.
● Each breakout room will have a moderator to address any questions.
● You will work on solving the problem within your breakout rooms.
● At the end of the 2 hours, you will submit your work by sharing the links
to the documents created during the session.
● Submissions will be reviewed, and winners will be announced.
Problem Solving and Submission Process:

1. Ask questions to clarify the problem statement.


2. Design the application wireframe using Wireframe.cc, focusing on a
mobile application.
3. Create and document the database, including entities and
relationships, using Draw.io.
4. Design and document the necessary APIs (URL, HTTP method, request,
response) for each app screen in a Google Doc or a local text editor.
5. Decide on a monolithic or microservices architecture.
6. Document the services, their interactions, and overall network topology
in a high-level architecture diagram using Draw.io.
7. Compile all document links into a Google Doc and share it with the
moderators.
8. Bonus points will be awarded for tech stack suggestions for various
system components, including reasons for your choices.

You might also like