do what you want.
try not to go crazy.
'database' is a misunderstood and misapplied term. as an application server, this is not needed. it also tries to have machines 'just handle' all the bits, pieces, and nuances of work. which is generally not a good plan, without first outlining the data, archive, storage, distribution, release-diff-merge procedures, signing, and history-edge control. by the time you are done with all of these tasks, then and only then can a database be added on top of it, as a bonus-feature and replaceable-interop between other applications.
to the laymen, it helps to think in terms of not so much databases (which descends into inaction, failure to comprehend, sloth, crazy, and abandonment without chance of recovery). instead, think in terms of email. company domains, project domains, system domains, etc, with mailbox users, task-subject users, archive/log/sysmsg users, etc. doing this as if you would be 'doing an email server' also attains distribution, transaction, human inspection, and auditing, etc. it will also permit recovery and retasking, isolation and destruction/preservation of data separate from code, etc.
making these systems is easy. handing the concepts, presence, problem-space, provision, production, delivery, limitations, and roadmaps to the point of not just correction, but crucially to completion as well, without confabulation - this is the harder part. using 'database' meme magic to 'just handle' the part that matters the most is shitskin thinking; you are asked to keep it from bleeding into your patterns.
applications come at the end. data first, structure second, and release (publication) dist/sych/merge generally follows structure [use established file system tools][or established email system tools under individual eml or mbox; avoid exchange lotus shitskin-capitulated etc]. operations on data are not permitted to delete or modify, only post transforms and derivations - which are kept separate ; data rank/score/trust will be established by adoption-acceptance into distribution trees, and this too will be kept in it's own separate structure. code is yet another structure, kept separate from all as well. search is an application, it comes at the end, fuck you, don't argue. database is an application, it comes at the end, fuck you, don't argue. your primary task is data, then structure, then release distribution/sync/merge, then history / log / transforms / production / production storage / etc.
good luck to you. time ticks away. do it right, and the work require to maintain is solved before expansion, preventing capitulation and abandonment. fail to do this pre-work, maintenance will kill you. and you will not have enough time, energy, and willpower/spirit left in you at each interval tick to recognize manipulation, shitskin frame entropy invasion, and subversion.