<aside> ❓ See Technical Research Guide for more info on using this page
</aside>
<aside> 🚧 Add notes to this page about your product technical research. What you learn and your notes and considerations about them.
</aside>
<aside> 🚧 Here include UML's, live feature lists, or any other visuals that explain the current architecture only. Any models or visuals from previous versions should be placed into another document and linked below in the previous version it was in.
</aside>
<aside> 🚧 What platform(s) is your product going to be on? Where do you think most users will use your app? (native app, mobile web, desktop, etc...) Brainstorm your ideas here. Document in the 🏗 Architecture pag
</aside>
<aside> 🚧 How will you architect your product to accommodate your users' preferred platform?(Progressive Web App, Native Mobile App, etc... If your project is going to have more than 1 platform, list them all here)
</aside>
Our typical user will be using this application from a desktop environment.
Potential in future releases for mobile optimized web application or Android/iOS apps.
<aside> 🚧 Back end brainstorming and research notes here
</aside>
What are you using for your database? (SQLite3, PostgreSQL, MongoDB, etc…)
Production database will be PostgreSQL - familiarity and functionality
What framework/language are you using? (many teams use NodeJS/express/knex)
NodeJS/Express/Knex will be our backend framework - familiarity and functionality
How do you plan on interacting with your APIs? (REST API, GraphQL, etc...)
REST API
What alternatives did you explore?
GraphQL
Why did you decide on this combination? (what are the advantages?)
This is a framework that the team has worked with before and knows will, at current, accomplish our goals and objectives effectively.