Backend website architecture

I always like to work on projects that achieve multiple goals. Since I want to focus on backend and cloud development for the next few months, I decided to create a real-world application that I'll actually use. This led me to build a comprehensive plumbing website using the following technologies:

• React with Next.js
• TypeScript
• Tailwind CSS
• AWS (Amazon Web Services)
• Go (Golang)

Having already created a straightforward plumbing website, I wanted version 2 to focus on automating as much of the process as possible, from booking to job completion.

Having already created a straightforward plumbing website, I wanted version 2 to focus on automating as much of the process as possible, from booking to job completion.

I’ve created an MVP (Minimum Viable Product) architecture diagram, but I have many more ideas to implement. My focus is on getting the core functionality up and running, then iteratively adding new features in an agile manner.

How the MVP is Designed

• Form Submission: The user submits a form, triggering a Lambda function that processes the data and stores it in a database.
• Calendar Integration (Challenge): The trickier part involves syncing available booking times with my phone's calendar. The idea is that events added to my Google Calendar will trigger a Lambda function to update the database, blocking off those times for bookings.

Additional Features

• Frontend Postcode Checker: A postcode radius checker on the frontend will determine if a user's location is within the service area. This will be implemented using a JSON-based hash map for fast (O(1)) lookups, ensuring a smooth user experience.
• Dynamic Booking Calendar: After passing the postcode check, users will see a calendar displaying available booking times fetched from the backend. This gives me granular control over the days and times offered for each service.

Mobile Calendar Integration

The more complex aspect is integrating this functionality with my mobile calendar. Adding an event to my Google Calendar should automatically update the database, blocking off those times for bookings.

The Road Ahead

I have many more features in mind, but I prefer to start with an MVP, tackling smaller tasks and gradually adding complexity once the core application is functional.

If anybody has implemented anything similar with google calender would be interesting to hear.