Architecture discussion meeting¶
Through the meeting we mainly discussed the base architecture we'll build the web app on.
Main point discussed¶
Web application architecture¶
We agreed on an initial architecture with the following pattern.
For starters the components will be as follows: * DB:Transferring from MongoDB hosted on Mlab to PostgreSQL(Except for messaging) * Auth Server: Firebase authentication * Backend APIs: Django/NodeJS can be changed(Check the next point)
As an initial test we'll handle the authentication through firebase and hold a UID for each user in our DB to hold the type of the user (Employer of Freelancer).
Django Learning phase¶
To be on the same page when working on the backend I'll be giving DJango framework a study phase of 2 days to get familiar with it, if I get to wrap my head around it in that phase We'll be using it instead of NodeJS to ensure a better reviewed codebase, if not we'll continue with NodeJS with a similar framework.
Employers/Freelancers communication decision¶
This will be a decision up to the client, but we came up with 2 options for communication between the employers and freelancers: * Email Relay * Microservice realtime chat
Email Relay¶
This option will be completely implemented from scratch where the Employer/Freelancer will send mails to our own inbox and the email will get relayed to the designated target without exposing either.
Microservice chat¶
This option will use a complete third party library/SaaS to implement the realtime messaging with its own (mostly MongoDB) database.
We agreed that the first option is better in terms of clean implementation and clean formal communication between employer and freelancers unless the client wants a realtime messaging service between the two which is a decision to be handled.