The appilcation's frontend is built on next.js and deployed via Netlify, communicating with an Apache web server, WSGI, and Flask API deployed on an Amazon Linux 2 instance. The API retrieves data directly from the internet and from an AWS MSSQL RDS instance, where data is also stored. An endpoint is available here, and the frontend and backend repositories are public on GitHub. Below are a number of diagrams drawn before any of the application materialized. Their description of the app architecture is still mostly valid.
The backend repository uses Git, GitHub, AWS CodePipeline, and AWS CodeDeploy for CI/CD deployment to an Amazon Linux 2 instance. Similarly, the frontend uses Git and GitHub for direct CI/CD integration with Netlify.
I regret that this website—in particular, this application—is not very responsive (4/13/2023), but I feel it demonstrates fullstack competency and is enough to post. If you see anything broken or poorly-done, I probably know about it, so challenge me to correct it! And, yes, this is wildly overengineered for my purposes, but it was a great learning experience.
Click on the search bar and type in an NBA player's name. Limitations to the search algorithm have the following consequences:
All player pictures, statistics, and data are property of www.basketball-reference.com. This demonstration is intentionally limited to better align with the guidelines issued by Sports Reference. Measures taken to limit this site's footprint on Sports Reference's are described on the explanation page. Data, images, statistics, etc. from Sports Reference are blurred.