在Web项目中组织库是否是不好的做法？ [关闭]

I started to create a project with the following format for a go project:

github.com
    coolproject
        datasources
        coolapp

Within datasources this can be a database or a file, and it seems like there is enough of them that they warrant another dir for organization.

Under datasources I was thinking of organizing as follows:

datasources
    databases
        pgsql.go
        mysql.go
    configfiles
        yaml.go
        json.go

The names of the dirs and files have been generalized a little bit for simplicity.

However, it appears most projects encourage a flat structure where datasources wouldn't exist, and databases and configfiles would be at the same directory level as coolapp.

Question is - is an additional level of organization for common libs considered bad practice?

I am most interested in what is considered idiomatic and accepted by the community.