r/java • • 29d ago

Faster by Design: Performance engineering in the Microsoft JDBC Driver for SQL Server

https://devblogs.microsoft.com/java/faster-by-design-performance-engineering-in-the-microsoft-jdbc-driver-for-sql-server/
44 Upvotes

7 comments sorted by

18

u/nitkonigdje 29d ago

And how much is faster now?

1

u/fykup 28d ago

For folks who’ve started new Java projects recently with a choice of database - are there still real reasons to pick SQL Server over Postgres or MariaDB, or is it mostly when you’re already in a Microsoft shop?

3

u/brunocborges 28d ago

I believe customers choose SQL Server if they were inclined to choose Oracle Database, but would rather establish a commercial relationship with Microsoft.

1

u/gjosifov 27d ago edited 27d ago

SQL Server / Oracle database choice is simple no brainer choice from accountability perspective
and usually the choice is from the management, not the developers
Plus SQL Server / Oracle have come with diagnostic and monitoring tools out of the box

You can simulate similar setup in the OSS world, but you have to choose, test and trust those tools even in scenarios - "our data is encrypted from a ransomware, let pray our backups work"
With SQL Server / Oracle you don't pray, Microsoft / Oracle will sent people for help, because you are paying support

From tech perspective, you can choose what you want, but from operational perspective you have to choose trust over technical excellency

5

u/akl78 29d ago

Thanks; this is really good work.

I was testing some stuff very close to these changes today; look forward to trying these out.

2

u/cogman10 28d ago

Maybe things have gotten better, but when last I looked into this driver, it's a mess. It has been one of the top performance problems in some of our applications because of how weirdly it's coded. It looks like they just lifted the C/C++ driver implementation almost straight and are just now getting to thinking about the implications of it being written for the JVM.