Planning: BridgeInTech App Architecture

[mtreacy002]

This issue is to discuss BridgeInTech App Architecture which needed to be finalised to get a solid idea of how to move forward with the project.

Below is the initial idea of app architecture as per proposal:

As per proposal:

Backend:
(Option3) The middle ground is to use the current MS REST API but with 2 Frontend: MS and BIT. In short 2FE + 1BE.

Pros:

• Reduce overhead compared to option 2 (to use the current MS as REST API and have separate Backend and Frontend specific to BIT (2FE + 2BE)).
• No need for MS Android FE to be changed to accommodate BIT UI
• Being MS FE exclusive to Mentor/Mentee, their interaction throughout the program can be focused on the task at hand.
• Minimise company interference on the specific details within the process of mentoring between mentor and mentee. Company involvement is limited to collaborating with mentor/mentee in designing tasks at the beginning prior to actual program starts. However, companies can still interact with the mentor and mentee through the IRC channel throughout the duration of the program.

Cons:

• Reducing company involvement on the tasks specific could be seen as unfavourable to some companies.

Frontend:

• Android: MVVM
• React: ??

[mtreacy002]

Update:
Hi @anitab-org/bridgeintech-maintainers. Just wanna give an update here based on our discussion in BIT weekly meeting Wednesday , May 27th AEST

Backend architecture:

• on initial GSoC period:
  • API:MS API + BIT API ** ~ aka 2 APIs**
  • Database: MS Heroku database (specific to BIT) and BIT database **~ aka 2 DBs**
• at the end of GSoC period:
  • API: MS API + BIT API as above
  • Database: MS schema and BIT schema in one single Database

Frontend architecture:

• React package: tba