Breaknorm
Sign inStart free

Product

SignalsPeopleCompaniesLocal businessesMCP and API

Plays

Post engagersTeam build-outChampion movedHiring surgeNewly fundedLookalikesAll plays

Data

Coverage by countryHiring dataJob changesEmail verificationCompanies by toolWho is hiringMarket mapsOutboundCompany profilesCompare
PricingDatasetsDocsSign in
Compare · backend frameworks

Django VS Spring Data JPA

As of 30 October 2026, Spring Data JPA is named by 121 companies and Django by 2,060; Django skews to companies under 200 people (66% vs 48%), Spring Data JPA to companies over 1,000 (31% vs 16%).

As of 30 October 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.

The website-and-DNS footprint is not comparable between a marketing suite and a CRM: Django's script and mail records show on hundreds of thousands of small sites, Spring Data JPA rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.

Django: 2–200 employees
66%
Spring Data JPA: 2–200 employees
48%
Django: 1,000+ employees
16%
Spring Data JPA: 1,000+ employees
31%
Postings per company, 90 days
2.1 · 2.9
Website or DNS footprint
0 · 0
2,060companies name Django
121companies name Spring Data JPA
0name both
4,240 · 347postings in 90 days, Django · Spring Data JPA
02Side by side

Who chooses which

Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.

By company size
SegmentDjangoshareSpring Data JPAshareLeans
Self-employed362%22%even
2-10 employees26213%1412%even
11-50 employees63931%2218%Django
51-200 employees45322%2218%Django
201-500 employees22311%1412%even
501-1000 employees1156%97%even
1001-5000 employees1547%1714%Spring Data JPA
5001-10000 employees502%54%even
10,001+ employees1286%1613%Spring Data JPA
By industry
SegmentDjangoshareSpring Data JPAshareLeans
Technology & software1,28162%7461%even
Business & finance services32816%2218%Spring Data JPA
Manufacturing & industry1226%32%Django
Consumer services & leisure804%76%even
Media & content623%32%even
Public, community & associations492%22%even
Utilities & infrastructure382%11%even
Commerce & trade301%––outside top 12
Property & construction231%––outside top 12
Health care151%32%even
Automotive111%11%even
Hospitality & travel100%11%even
Transport, logistics & rental––32%outside top 12
Agriculture & forestry––11%outside top 12
By country
SegmentDjangoshareSpring Data JPAshareLeans
United States1,19858%5848%Django
India1758%2017%Spring Data JPA
United Kingdom1286%54%Django
Germany904%43%even
France613%43%even
Canada372%22%even
Netherlands362%––outside top 12
Poland291%––outside top 12
Australia261%––outside top 12
Italy241%––outside top 12
Singapore201%43%Spring Data JPA
Switzerland181%32%even
Spain––54%outside top 12
Brazil––32%outside top 12
Portugal––22%outside top 12
Austria––11%outside top 12
Postings by team (share of each tool's postings)
SegmentDjangoshareSpring Data JPAshareLeans
Software engineering4,83875%39087%Spring Data JPA
Data & AI62810%133%Django
IT operations & business systems1943%82%even
Engineering (non-software)781%20%even
Product, program & project management371%10%even
Unclassified371%31%even
Marketing & communications240%––outside top 12
Education & training180%20%even
Customer service & success170%10%even
Design & UX130%––outside top 12
Public safety and protective services120%––outside top 12
Sales110%10%even
General management & consulting––20%outside top 12
Cite this

Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.

Spring Data JPA is named by 121 companies in job postings and Django by 2,060; 0 name both. (Breaknorm, 30 October 2026, https://breaknorm.co/compare/django-vs-spring-data-jpa)
How we know

Read from the source, not self-reported

Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →

  • Job postingsRead hourly from career sites. A tool counts when the employer's own text names it as the team's system; both tools can count for one company.
  • Website and DNSScripts and embeds on the company's pages, plus SPF, DKIM, MX and CNAME records of its domain that point at the vendor.
  • SegmentsCountry, size and industry from the company profile built from its website.
  • Not a reviewNo ratings, prices or feature claims. For those, read the vendors.
FAQ

Django vs Spring Data JPA: questions

Which is more used, Django or Spring Data JPA?

By companies naming it in their own job postings, Django (2,060) over Spring Data JPA (121). By website-and-DNS footprint, Spring Data JPA (0 vs 0), because its scripts and mail records sit on many small company sites.

Who chooses Django?

66% of Django companies have 2 to 200 employees, against 48% for Spring Data JPA. 16% of Django companies have over 1,000 employees, against 31% for Spring Data JPA.

Do companies run both?

0 companies name both in their postings, usually Django in marketing and Spring Data JPA in sales, or during a migration.

Where do these numbers come from?

From the employer's own text in job postings read hourly from career sites, and from scripts found on company websites in our crawl. No vendor data, no surveys.

Companies and people

Get either list your way

The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.

Every company on either tool,
with the person who owns it

Filter on Django or Spring Data JPA. Start free, no card.

  1. 01Sign up, no card
  2. 02Connect Claude, ChatGPT or an API key
  3. 03Ask for your market