JDBC is the standardized Java API for accessing relational databases. It provides connection management, SQL execution and result set handling for Java applications. JDBC supports driver models, is platform-independent and is commonly combined with connection pooling and ORM frameworks for OLTP and batch workloads.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
JDBC is the standardized Java interface for connecting to relational databases.
JDBC emerged in the 1990s from the need to connect Java applications independently of a database vendor. Sun Microsystems shaped the API; drivers translated its standard calls into each database's protocol.
The application opens a Connection, creates a PreparedStatement, and binds parameters. A JDBC driver executes SQL, returns ResultSets, and controls transactions while the application closes resources.
It mediates between the JDBC API and a database.
It encapsulates SQL and bound parameters.
It groups changes with commit or rollback.
JDBC provides a direct, portable database layer. Connection pooling, parameterization, transaction boundaries, and resource cleanup determine safety and operations.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.