Congrats Theresa! This too shall pass. Failure = More Success. You have learned and grown so much practical experience and sharing wisdom with others as an inspiration. Imagine if it just worked and you had no issues… until one day with 100s or 1000s of users it “crashed”… then what?! Congrats. Way to persevere and follow your dreams to help so many. Continue to do so.. proactively. Your app + database are now being tested for scalability, availability, performance and reliability. Backup/Recovery & redundancy are equally important should issues occur. Change management & control are important especially with changing AI platform & app hosting environment. For example, is your app+ database dependent on specific AI model and features? What if AI model changes or replaced, does it impact your system? What if pricing and use changes? How do you adapt live with your app? What happens if app loses connection to database connection for one of many issues? Databases get “fat” over time and use and have limitations in terms of sessions, connections, threads, performance as well as indexing requirements, reclaiming memory, etc. What happens if database is updated to new revision, version or release? Databases have limitations in data types and sizes, how data is stored, compressed, indexed, etc. what happens when growth and size gets large, impact to performance, integration of additional tables, views, or redundant databases. Are you tracking bugs and defects and tracking resolution progress & history? Will this be used to share with partners who may be involved in supporting app development & maintenance? Will customers of app be able to submit issues or problems via the app or some dashboard, and integrate into this environment (eg slack)? Are you planning on having an app+database status web page as part of supporting clients and keeping track of issues, including dependencies? This may help reduce DMs, emails and reviews … and reduce duplication of communication/efforts.