amazon web services - JEE Container (Glassfish) and HikariCP - JNDI vs managing my own instance -


is considered bad/acceptable/good/best practice manage own instance of hikaricp connection pool, goal don't have configure jndi resources within glassfish?

some background:

my deployment environment aws's elastic beanstalk, running glassfish within docker container. have working solution generating jndi resources whe deploying in environment, makes deployment quite fragile. see following question details: how configure glassfish instance running on aws/elasticbeanstalk/docker?.

i'm quite keen rid of deployment hassles, don't know connection pooling, , hikaricp in particular. cruising bruising in direction? super simple implementation might create static variable contains connection pool.


Comments

Popular posts from this blog

php - Invalid Cofiguration - yii\base\InvalidConfigException - Yii2 -

How to show in django cms breadcrumbs full path? -

ruby on rails - npm error: tunneling socket could not be established, cause=connect ETIMEDOUT -