Golang Backend with Dynamic Connections to Multiple Database Brands (Oracle & PostgreSQL)

Is it reasonable to develop a web application in Golang that supports both Oracle and PostgreSQL databases, dynamically switching connections based on request parameters? The application is built with Golang as the backend and has an embedded Angular frontend (using embed.FS).

For example, when the application starts, the user opens the main page and sees a list of saved database connections. They can select one or multiple connections and click ‘Connect.’ Once connected, clicking on a specific database opens its main GUI page, where the Angular frontend interacts with the backend via API calls, retrieving and displaying relevant data from the selected database.

Key Questions:

1. 
   What are the potential advantages and challenges of such an architecture (serving multiple database types from a single backend), particularly in terms of performance, maintainability, scalability, and security?
   
   
2. 
   Are there any real-world applications or best practices that follow a similar approach of supporting multiple databases dynamically while serving a frontend from an embedded file system?
   
   
3. 
   What potential performance issues might arise, and how can they be mitigated?
   

I guess it’s possible to use dynamic connections with different brands of databases within Golang and Angular, but I want to be sure it’s a good approach to start with. This architecture seems more complex to implement, so I want to confirm whether it is a reasonable and correct approach before proceeding.

Continue reading...