[Task]: Evaluate inconsistency in Database configurations in Platform API and Gateway

[Thushani-Jayasekera]

Please select the area the issue is related to

Area/Gateway (Routing, API deployment in gateway etc.)

Please select the aspect the issue is related to

Aspect/UX (User experience, flows, usability, clarity)

Description

Platform API DB configs

[database]
driver = "sqlite3"   # "sqlite3" or "postgres"

# SQLite — ignored when driver = "postgres"
path = "/app/data/api_platform.db"

# PostgreSQL — uncomment and set driver = "postgres" above to use
# host     = "localhost"
# port     = 5432
# name     = "platform_api"
# user     = "platform_api"
# password = "change-me"
# ssl_mode = "disable"   # "disable" | "require" | "verify-ca" | "verify-full"

# Connection pool — tune for production workloads
# max_open_conns    = 25    # maximum open connections
# max_idle_conns    = 10    # maximum idle connections in the pool
# conn_max_lifetime = 300   # seconds before a connection is recycled

# Schema management
# execute_schema_ddl = true   # set to false if you manage migrations yourself

Gateway DB Configs

[controller.storage]
# Storage type: "sqlite", "postgres", or "memory"
type = "sqlite"

[controller.storage.sqlite]
path = "./data/gateway.db"

[controller.storage.postgres]
# Optional DSN. If set, host/port/database/user/password are ignored.
# dsn = "postgres://user:password@localhost:5432/gateway?sslmode=require"
host = "localhost"
port = 5432
database = "gateway"
user = "gateway"
password = ""
sslmode = "require" # disable, require, verify-ca, verify-full
connect_timeout = "5s"
max_open_conns = 25
max_idle_conns = 5
conn_max_lifetime = "30m"
conn_max_idle_time = "5m"
application_name = "gateway-controller"

Issue with defining database configs as in gateway is, when we introduce a new database type we will have to add a new config.