Why do we use a DataSource instead of a DriverManager?

by

Better scalability and maintenance

For DriverManager you need to know all the details (host, port, username, password, driver class) to connect to DB and to get connections. Externalizing those in a properties file doesn’t change anything about the fact that you need to know them.

Using a DataSource you only need to know the JNDI name. The AppServer cares about the details and is not configured by the client application’s vendor, but by an admin where the application is hosted.

Scalability:

Suppose you need to create connections yourself, how would you deal with changing load, sometime you have 10 users sometime you have 1000, you can’t just get a connection whenever you need one and later ‘release’ it so the Database server does not get out of connections, which leads you to connection pooling. DriverManager does not provide it, DataSource does.

If you are going to program a connection pool yourself then you have to use DriverManager, otherwise go with DataSource.

More Related Contents:

  1. How to get the insert ID in JDBC?
  2. To prevent a memory leak, the JDBC Driver has been forcibly unregistered
  3. Is java.sql.Timestamp timezone specific?
  4. java.util.Date vs java.sql.Date
  5. MySQLSyntaxErrorException near “?” when trying to execute PreparedStatement
  6. Java ResultSet how to check if there are any results
  7. Retrieve column names from java.sql.ResultSet
  8. JDBC connection failed, error: TCP/IP connection to host failed
  9. How can I get the SQL of a PreparedStatement?
  10. Can we connect remote MySQL database in Android using JDBC? [closed]
  11. Is java.sql.Connection thread safe?
  12. JDBC MySql connection pooling practices to avoid exhausted connection pool
  13. Can I connect to SQL Server using Windows Authentication from Java EE webapp?
  14. How does Java’s PreparedStatement work?
  15. Create a jTDS connection string
  16. How to get all table names from a database?
  17. Should I use java.util.Date or switch to java.time.LocalDate
  18. org.postgresql.util.PSQLException: FATAL: sorry, too many clients already
  19. JPA SQL Server No Dialect mapping for JDBC type: -9
  20. Queries returning multiple result sets
  21. java error (No suitable driver found)
  22. Cannot use a LIKE query in a JDBC PreparedStatement?
  23. How can I abort a running JDBC transaction?
  24. When my app loses connection, how should I recover it?
  25. How to Correctly Close Resources
  26. How to get row count using ResultSet in Java?
  27. java sql date time
  28. Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
  29. MyBatis executing multiple sql statements in one go, is that possible?
  30. A persistent connection with JDBC to MySQL

Leave a Comment