<aside>
β See the Architecture Guide for more information
</aside>
Technical
<aside>
π§ After doing technical research, return here to fill out the technical frameworks, platforms and other architectural decisions you resolve.
</aside>
API Integrations
<aside>
π§ See the guide for more info on what to document here.
</aside>
- What Feature(s) is/are this API connected to?
- Onboarding
- Okta
- third party API to verify user is a Lambda Student (stretch) talk to ryan hamblin about this
- third party API to grab list of job titles (stretch)
- What will this API integration accomplish in the feature(s) to which itβs connected?
- handle Oauth token creation and deletion - authentication
- What alternatives did you consider?
- Due to Engineering Standards we chose Okta.
- Why did you decide on this solution? (what are the advantages?)
- Personalized User Experience: It provides ease of use for end-users to access applications, and is fully customizable.
- Adaptive Authentication: Protect user access with two-factor authentication for all SSO customers via Okta Verify OTP. Okta is an internal resource all Lambda School students have access to.
- What potential challenges can you foresee?
- Third party APIs can't be fully reliable. They could theoretically change endpoints or names for data, which we would then have to update on our end as well.
- Nobody on the team has experience setting up Okta, which introduces a learning curve.
Front-end
<aside>
π§ See the guide for more info on this section.
</aside>
-
What Framework are you using for your FE? (React, React Native, Angular, Vue, etc...)
-
What are other frameworks you would like to consider?
-
Why did you decide on this framework over the alternatives (what are the advantages?)
- React over native because build responsive web only, flexibility in building blocks, quick, efficient, large community support. React has virtual DOM where angular does not. Can easily implement React-Native at a later point in development.
- Single Page Application, JSX
-
What potential challenges can you foresee using this framework?
- State management
- Implementing new UI libraries
-
Where to deploy front end?