...can there be more?
One possible response is yes- to leverage a Preview Publishing Target. In this scenario you would duplicate your web
database, connection string and definition. Rename to preview
(for example).
Connection Strings
<add name="preview" connectionString="user id=sitecore;password=sitecore;Data Source=(local);Database=Sitecore_Preview" />
Definition
<?xml version="1.0"?>
<sitecore>
<databases>
<!-- preview -->
<database id="preview" singleInstance="true" type="Sitecore.Data.DefaultDatabase, Sitecore.Kernel">
<param desc="name">$(id)</param>
<icon>Images/database_web.png</icon>
<securityEnabled>true</securityEnabled>
<dataProviders hint="list:AddDataProvider">
<dataProvider ref="dataProviders/main" param1="$(id)">
<disableGroup>publishing</disableGroup>
<prefetch hint="raw:AddPrefetch">
<sc.include file="/App_Config/Prefetch/Common.config" />
<sc.include file="/App_Config/Prefetch/Webdb.config" />
</prefetch>
</dataProvider>
</dataProviders>
<proxiesEnabled>false</proxiesEnabled>
<proxyDataProvider ref="proxyDataProviders/main" param1="$(id)" />
<archives hint="raw:AddArchive">
<archive name="archive" />
<archive name="recyclebin" />
</archives>
<cacheSizes hint="setting">
<data>100MB</data>
<items>50MB</items>
<paths>2500KB</paths>
<itempaths>50MB</itempaths>
<standardValues>2500KB</standardValues>
</cacheSizes>
</database>
</databases>
</sitecore>
Workflow Considerations
With two web databases, you can leverage the Preview Publishing Target setting.
Publishing Target

Workflow State

This will promote items in this workflow state immediately to your preview target.
There are additional considerations with this configuration such as a separate CM and CD instances and indexing that fall outside the scope of your specific question. But, short answer, yes you can have additional databases.