HandyHub - Your Go-To Tradesman Directory

Bislon A Zulu — Wed, 18 Sep 2024 19:00:15 +0000

HandyHub: Connecting Clients with Reliable Tradesmen

Project Purpose

HandyHub is designed to bridge the gap between clients and skilled tradesmen in their area. Our goal is to streamline the process of finding and hiring tradesmen, making it easier for clients to access essential services like plumbing, electrical work, and repairs through a user-friendly platform.

Team Members, Roles, and Timeline

The HandyHub project is part of the ALX SE program’s final project, and the development team consists of:

Bislon Zulu (Myself): Responsible for backend development, including database design, API creation, and overall project architecture.
Project Timeline: Development is ongoing, with the Minimum Viable Product (MVP) currently complete and under review.

Who Is HandyHub For?

HandyHub serves two primary audiences:

Clients: Homeowners, businesses, or anyone in need of tradesmen services such as electricians, plumbers, or contractors.
Tradesmen: Skilled workers looking to expand their client base by listing their services and being discovered by potential clients.

My Personal Focus

As the sole engineer, my main focus has been on building the backend infrastructure for HandyHub. This includes ensuring smooth API integration and managing the database. The project is designed to provide a mobile-friendly experience, using technologies like Flask and PostgreSQL to power its core functionality.

HandyHub helps clients easily find tradesmen based on location and specialization, much like how apps like Uber connect riders with drivers.

When I started working on HandyHub, it wasn’t just another project to tick off my list; it was a personal mission. As I walked through my neighborhood, I often saw outdated flyers and makeshift signs advertising services. It struck me that there had to be a better way to connect people with the services they need. Many skilled tradesmen were limited to a small radius for advertising their services, while clients struggled to find reliable professionals. HandyHub was created to address these issues by offering a modern, efficient way to connect people with the services they require.

Project Summary

HandyHub successfully simplifies the process of finding and connecting with skilled tradesmen. The platform allows service providers to reach a broader audience and offers users an easy way to find reliable professionals. By combining technology with community needs, HandyHub provides both a directory and a rating system to ensure trust between clients and tradesmen.

Result of the Project

The final result is a web application where users can search for tradesmen by location and specialization. Tradesmen can create profiles showcasing their skills, certifications, and contact details. This modern approach eliminates the need for outdated advertising methods like flyers.

Technologies Used

Frontend: We chose HTML5, CSS3, and JavaScript to build a mobile-first, responsive interface. This stack was selected for its flexibility and the opportunity to deepen our understanding of core JavaScript principles and responsive design techniques without additional frameworks.
Backend: Flask and Python were selected for their lightweight nature, which facilitates the development of REST APIs that meet our project’s needs. Flask’s minimalistic approach allowed us to maintain control over the application’s structure.
Database: PostgreSQL was chosen for its robust relational data management and strong community support. It efficiently handles structured data, such as tradesman profiles and client reviews, ensuring data integrity.

The Most Difficult Technical Challenge

The most challenging aspect of this project was working within the Windows Subsystem for Linux (WSL). Although WSL was chosen to maintain a Linux-based workflow consistent with other ALX tasks, it presented a steep learning curve. Configuring and integrating tools and services within WSL proved difficult, especially with issues related to PostgreSQL and network settings. Ultimately, I decided to switch to development directly in Windows to expedite the process and meet deadlines. This experience, though challenging, contributed significantly to my growth as a developer.

Conclusion

Working on HandyHub has been a rewarding journey, blending technology with community service. I’m proud of how the project has evolved from an initial idea to a functional platform that connects tradesmen with clients. Despite challenges, especially with WSL, the project has been a valuable learning experience.

I’m a passionate software engineer dedicated to creating solutions that positively impact the community. You can explore the HandyHub project on GitHub. For further connections, feel free to reach out to me on LinkedIn.

Postmortem: HandyHub Service Outage

Bislon A Zulu — Tue, 03 Sep 2024 22:40:11 +0000

Issue Summary
Duration: August 25, 2024, 14:00 - 16:30 GMT+2
Impact: HandyHub’s search and browse functionality was down, affecting 60% of users. Users experienced slow response times and were unable to search for tradesmen.
Root Cause: A misconfigured API Gateway routing rule caused requests to loop indefinitely, leading to high server load and eventual service downtime.

Timeline
14:00 - Issue detected via monitoring alert indicating high server load.
14:05 - Initial investigation by on-call engineer; assumption was a DDoS attack.
14:15 - Misleading path: Network team investigated potential external threats.
14:30 - Customer complaints confirmed the issue was affecting search functionality.
14:45 - Escalated to backend engineering team.
15:00 - Identified misconfigured API Gateway routing rule.
15:15 - Applied temporary fix by disabling the problematic rule.
15:45 - Full resolution by correcting the routing configuration.
16:30 - Services fully restored and monitored for stability.
Root Cause and Resolution
Root Cause: The API Gateway had a misconfigured routing rule that caused requests to loop back to the gateway instead of being routed to the appropriate backend service. This misconfiguration led to an exponential increase in server load, causing the search and browse functionality to become unresponsive.

Resolution: The issue was resolved by first disabling the problematic routing rule to stop the looping requests. Then, the routing configuration was corrected to ensure that requests were properly directed to the backend services. A thorough review of all routing rules was conducted to prevent similar issues in the future.

Corrective and Preventative Measures
Improvements:

Implement stricter validation and testing of API Gateway configurations before deployment.
Enhance monitoring to detect unusual traffic patterns indicative of routing issues.
Conduct regular audits of routing rules and configurations.
Tasks:

Patch API Gateway: Update the API Gateway to the latest version to include any bug fixes and improvements.
Add Monitoring: Implement detailed monitoring on API Gateway traffic to detect anomalies.
Automate Testing: Develop automated tests for API Gateway configurations to catch misconfigurations early.
Review and Document: Conduct a comprehensive review of current routing rules and document them thoroughly.
Training: Provide training for engineers on best practices for configuring and managing API Gateways.
By addressing these measures, we aim to improve the reliability and stability of HandyHub’s services, ensuring a better user experience and reducing the likelihood of similar outages in the future.

Fun Fact: During the outage, our team discovered that the coffee machine was also down. Coincidence? We think not! ☕🚨

Remember, always keep your API Gateway and your coffee machine in top shape! 😉

DEV Community: Bislon A Zulu