mybatis/mybatis-3

MyBatis SQL mapper framework for Java

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 17 minutes ago
Added to GitGenius on September 2nd, 2026
Created on February 14th, 2013
Open Issues & Pull Requests: 212 (+0)
GitHub issues: Enabled
Number of forks: 12,860
Total Stargazers: 20,444 (+0)
Total Subscribers: 1,131 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 41
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 963 days
Stale 30+ days: 34
Stale 90+ days: 31

Recent activity

Opened in 7 days: 3
Closed in 7 days: 1
Comments in 7 days: 3
Events in 7 days: 10

Top labels

  • waiting for feedback (31)
  • bug (26)
  • 🔩 constructor (13)
  • duplicate (8)
  • enhancement (8)
  • wontfix (8)
  • 🔩 interceptor (7)
  • 🔩 typehandler (6)

Detailed Description

MyBatis is a SQL mapper framework for Java that simplifies database interaction by mapping SQL queries to Java methods through configuration and annotations.

MyBatis addresses the impedance mismatch between object-oriented Java code and relational databases by providing a lightweight alternative to full object-relational mapping. Rather than generating SQL automatically, it lets developers write SQL directly while MyBatis handles the mapping between query results and Java objects. This approach gives developers explicit control over SQL performance and structure while eliminating boilerplate code for result set processing and parameter binding.

MyBatis suits projects where developers want to work with SQL directly rather than abstract it away, particularly when query optimization and control matter. It works well for applications ranging from simple CRUD operations to complex queries with custom logic. Teams should choose MyBatis when they prefer explicit SQL over generated queries, when they need fine-grained control over database interactions, or when they want a lighter-weight alternative to full ORM frameworks.

The project maintains steady development activity with regular commits addressing bug fixes and feature enhancements. Pull requests receive consistent review and integration into the codebase. Issue tracking shows ongoing engagement with user-reported problems and feature requests, with maintainers providing responses and guidance. The project sustains documentation updates alongside code changes, keeping guidance aligned with implementation.