You can provide a multi-component with the database at the same service with the same performance and scalability
What is our primary use case?
The database for the accounting systems is our primary use case for this solution. Business software is 80% of my use case in the accounting software. It's a good tool for planning. I work with financial data and the data mining aspect is very important, as I need to access the data easily. The data is the most important thing. Sometimes the software developers forget this part because they just want to save the data on the database, but they don't know how to manipulate the data. The performance of the solution is dependant on how easily and quickly you can obtain access to the data.
Pros and Cons
"With the database, you can provide a multi-component at the same service with the same performance, scalability, or all those things."
"The database and applications can become very slow."
What other advice do I have?
If you want one tenant, you can use MySQL. If you want a multi-tenant, I think Postgres is better. SQL on PostgreSQL is linked to Oracle. Oracle and Postgres is the same thing, the same language. You will not have a big change for the software developers to migrate from Oracle to Postgres. I would rate PostgreSQL 8 out of 10.