Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Planning: BridgeInTech App Flow #10

Closed
mtreacy002 opened this issue May 11, 2020 · 10 comments
Closed

Planning: BridgeInTech App Flow #10

mtreacy002 opened this issue May 11, 2020 · 10 comments
Labels
Program: GSOC Related to work completed during the Google Summer of Code Program.

Comments

@mtreacy002
Copy link
Member

App flow as per proposal:
Link to online document

Opt. 3. MS+BIT schemas in MS DB+REST

BridgeInTech - App Flow MS+BIT schemas in MS DB+REST.png

@mtreacy002 mtreacy002 added the Program: GSOC Related to work completed during the Google Summer of Code Program. label May 11, 2020
@mtreacy002
Copy link
Member Author

mtreacy002 commented May 12, 2020

Hi team (@isabelcosta, @ramitsawhney27, @foongminwong).

I've made some adjustments to the App Flow based on @ramitsawhney27 suggestion.

Option 1:
This adjustment is made under assumption that the application would have 2 databases MS+BIT with one REST API.

Below is the screenshot of new flow. (link to file)

Screen Shot 2020-05-12 at 12 37 56 pm

@mtreacy002 mtreacy002 added this to the Project Overview milestone May 12, 2020
@mtreacy002
Copy link
Member Author

mtreacy002 commented May 12, 2020

Option 2:
For this option, the assumption is the BridgeInTech application will use MS DB + API with BIT DB + API.

Screen Shot 2020-05-12 at 4 39 40 pm

To think about:

  • Is it possible for one API to talk to 2 different DB? If so, how can we achieve this (routing?)? If not, should we use 2 APIs instead?
  • What about performance impact of using them (either 2 DBs + 1 API or 2 DBs + 2 APIs)?
  • Which one will have the least of N +1 problem (not creating loop full of requests)?

@mtreacy002
Copy link
Member Author

mtreacy002 commented May 13, 2020

Update: Option 4.
Hi @isabelcosta, @ramitsawhney27, and @foongminwong. I've adjusted option 2 App Flow as per discussion on Team Weekly Meeting, May 13th. I appreciate If you all can confirm that this is our direction. You can post a comment or react with ✅ .
In the mean time I'm going to work on the ERD issue#12 so we can finalize database design 😉 .

Screen Shot 2020-05-14 at 7 49 03 am

Link to file, also available on BridgeInTech Google drive folder: BridgeInTech_MTreacy002_Presentation.drawio

@mtreacy002
Copy link
Member Author

mtreacy002 commented May 16, 2020

Update Option 5
Hi @anitab-org/bridgeintech-maintainers. Here's another option with BIT API facing frontend and BIT backend will call MS API to get MS related data.

Screen Shot 2020-05-16 at 10 02 46 pm

@ramitsawhney27
Copy link

@mtreacy002 - As discussed, can you please update the two schemas to be shown under the same database? The rest looks good!

@mtreacy002
Copy link
Member Author

mtreacy002 commented May 17, 2020

Update on Option 5.
@ramitsawhney27 , is this ok?

Screenshot (1)

@isabelcosta
Copy link
Member

@mtreacy002 a nice to have would be mention of the APIs scope, so which is for MS and for BIT

@mtreacy002
Copy link
Member Author

mtreacy002 commented May 20, 2020

Update:
Hi @anitab-org/bridgeintech-maintainers, here's the update on option 5, now with API names as discussed in the BIT Team weekly meeting May 20th AEST.

Screen Shot 2020-05-21 at 6 21 12 am

link to file

@mtreacy002 mtreacy002 mentioned this issue May 25, 2020
10 tasks
@mtreacy002
Copy link
Member Author

Update:

As per our discussion on BIT Weekly Meeting, Wednesday, May 27th, the following will apply during GSoC periods:

  • On initial stage and during early development of GSoC, the App Flow on initial option 5 as posted here will be the one to be used

Screen Shot 2020-05-16 at 10 02 46 pm

  • At the final stage of GSoC, hopefully we can achieve the final version of option 5 as posted here

Screen Shot 2020-05-21 at 6 21 12 am

meenakshi-dhanani pushed a commit that referenced this issue Jun 2, 2020
* Add the README file

* made changes to README

* added suggested changes

* docs: Move lines #8 and #10

* moved README outside .github

* remove extra README file
mtreacy002 pushed a commit to mtreacy002/bridge-in-tech-backend that referenced this issue Jun 6, 2020
* Add the README file

* made changes to README

* added suggested changes

* docs: Move lines anitab-org#8 and anitab-org#10

* moved README outside .github

* remove extra README file

Fix pylint score

update requirements.txt for pylint

modified per review request and added travis tests
mtreacy002 pushed a commit to mtreacy002/bridge-in-tech-backend that referenced this issue Jun 6, 2020
* Add the README file

* made changes to README

* added suggested changes

* docs: Move lines anitab-org#8 and anitab-org#10

* moved README outside .github

* remove extra README file

Fix pylint score

update requirements.txt for pylint

modified per review request and added travis tests

move travis
mtreacy002 pushed a commit to mtreacy002/bridge-in-tech-backend that referenced this issue Jun 6, 2020
* Add the README file

* made changes to README

* added suggested changes

* docs: Move lines anitab-org#8 and anitab-org#10

* moved README outside .github

* remove extra README file

Fix pylint score

update requirements.txt for pylint

modified per review request and added travis tests

move travis

test if travis build gets triggered
mtreacy002 added a commit to mtreacy002/bridge-in-tech-backend that referenced this issue Jun 7, 2020
* Add the README file

* made changes to README

* added suggested changes

* docs: Move lines anitab-org#8 and anitab-org#10

* moved README outside .github

* remove extra README file
mtreacy002 added a commit to mtreacy002/bridge-in-tech-backend that referenced this issue Jun 7, 2020
* Add the README file

* made changes to README

* added suggested changes

* docs: Move lines anitab-org#8 and anitab-org#10

* moved README outside .github

* remove extra README file
meenakshi-dhanani pushed a commit that referenced this issue Jun 9, 2020
* Add the README file

* made changes to README

* added suggested changes

* docs: Move lines #8 and #10

* moved README outside .github

* remove extra README file
@mtreacy002
Copy link
Member Author

mtreacy002 commented Aug 30, 2020

Update @anitab-org/bridgeintech-maintainers , Closing this as the app architecture has matched the final stage targetted here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Program: GSOC Related to work completed during the Google Summer of Code Program.
Projects
None yet
Development

No branches or pull requests

3 participants