jOOQ Newsletter November 14, 2013

subscribe to the newsletter here

jOOQ Blog License now CC-BY-SA

Next to providing you with the best Java / SQL integration on the market, we’re also passionate bloggers on the matter of Java, SQL and Open Source. We think that with our experience around jOOQ, we should be major influencers on those subjects in general.

Our blog at will have reached the 200k hits threshold by the end of the week and we’ll most certainly celebrate that. Our topics and insights are increasingly appreciated by a wider and wider audience outside of the jOOQ user base, also on our syndication partners DZone (where we’ve had around 800k readers so far), JCG(readers unknown) and Tech.Pro (100k reads so far). The recent success shows that our marketing efforts pay off. Here are some stats from the jOOQ blog:

Because our blog is reaching far beyond our user base, we have decided to license its content under the terms of the CC-BY-SA 3.0 license, a permissive license that reflects our Open Source spirit. You may thus freely use our content for commercial purposes, if you attribute authorship to us. Please contact us, if you’re not sure how to create appropriate attribution.

Dual Licensing. An Experience Report

A month ago, we started dual-licensing jOOQ. We are happy to see that our competitors follow our lead in offering commercial services around their software. This is a strong indicator for having done something right. Here’s a little review from Data Geekery about the recent events around our new licensing model.

We have to admit that switching over from a very permissive Open Source license to more restrictive dual-licensing wasn’t exactly a walk in the park. Getting legal aspects right wasn’t easy. How many Open Source products out there do you think are neglecting due diligence with respect to copyright? Our estimate: 95%.

Yet, removing commercial database support from the jOOQ Open Source Edition has had only little impact on the number of downloads, nonetheless. After a short break in August / September (no jOOQ 3.1 patch releases), jOOQ 3.2 is almost as strong as ever as can be seen in this chart originating from

This doesn’t even count the number of downloads from, or from SourceForge, before we removed the SourceForge download channel. The same effect can be seen on Stack Overflow and on GitHub, where jOOQ has had a significant increase of traction in the last 2-3 months!

Furthermore, with our recent discussions with the Apache GORA and Apache CloudStack guys, we’re positive that dual-licensing won’t keep jOOQ out of the professional Open Source world.

At the same time, sales talks around tailor-made agreements with medium and large customers are ongoing. We’re considering our work of the last 4 months a great success and we’re positive to be able to provide you with a much better jOOQ in the near future by creating professional Open Source software built on solid financial grounds, which everyone can greatly profit from.

Upcoming Events

As mentioned in the October newsletter, Lukas is going to be present at a number of events in the near future, talking about jOOQ and other database related stuff. ThejOOQ presentation at Topconf in beautiful Tallinn, Estonia has had around 35 attendants – well, it was hard to compete with the Google Glass presentation :-)

Upcoming events include

Stay informed about 2014 events on

SQL Zone – ORM (Un)Popularity

We’re personally thrilled by the fact that the ORM debate is far from over, even more than half a decade after the vietnam of computer science was first recognised. We firmly believe that ORMs are a very leaky abstraction, which is fine in “top-down” engineering approaches where the relational database is a second-class citizen.

But many companies don’t think that should be the case. Many companies want their data to be the first-class citizen, processed by more volatile entities, such as Java programs. It often just doesn’t make sense to have the data abide by the rules of the ORM. It is thus not surprising that Charles Humble from InfoQ has again detected increasing discomfort with ORMs at QCon and other conferences.

In our opinion, there’s a simple reason for this. SQL is constantly evolving, but JPA isn’t. Most importantly, JPA doesn’t do SQL as understood by the ISO / IEC standards. And it doesn’t look as though that’s going to change. Read our blog post on that subject.

SQL Zone – The History of NoSQL

A witty remark about what NoSQL really is has recently been made at the O’Reilly Strata Conference in London, where Mark Madsen, a popular researcher and analyst was walking around with a geeky T-Shirt depicting the History of NoSQL.

We sincerely hope that this awesome piece of humour will go viral. See for yourself:

Clearly, betting on the “SQL horse” isn’t such a bad bet after all.

6 thoughts on “jOOQ Newsletter November 14, 2013

  1. > We are happy to see that our competitors follow our lead.

    Well, not exactly. The Querydsl post you link to explicitly reassures their users that they are not following your lead on licensing: “We have no intention of changing the licensing model of Querydsl and will keep on using a pure open source license for the foreseeable future.” They are just offering commerical services.

    1. Yes, I meant that they follow our lead with respect to “taking action” towards monetizing innovation. It doesn’t matter that they’ve chosen a different model. I just found it newsworthy that they would react to our actions. I fixed the text to better reflect this.

      1. Querydsl has offered and provided commercial support for ages. The biggest reason for the blog post was that a lot of our users were interested in knowing about Querydsl’s future plans, jOOQ’s decision to dual license was probably a trigger for some of them.

        1. Interesting, thanks for the feedback. I haven’t seen any actual public feedback to our dual-licensing from Querydsl users, neither on the user group, nor on the referenced blog post, or in other blogs. I also hadn’t seen any public advertising about commercial support on the QueryDSL website in the past, e.g. transparent pricing models etc, similar to Flyway. I’m sure that’ll follow, right?

          1. We are not comfortable publishing details of private discussions.

            Regarding transparency of pricing models we are constantly evaluating what is the best fit. Currently our prices are not visible because they vary based on what the customer’s needs are, for instance supporting Cassandra is a totally different to supporting Datomic etc.

            1. We are not comfortable publishing details of private discussions.

              Luckily, you’re not an Apache Software Foundation project:

              If it didn’t happen on a mailing list, it didn’t happen.

              Taken from ;-) I’m just kidding. Of course, private discussions aren’t disclosed often. Yet, since the linked QueryDSL article is advertising transparency through a “purer” form of Open Source, I have found these facts quite interesting.

              for instance supporting Cassandra is a totally different to supporting Datomic etc.

              That’s up to you, of course. I have to say, though, that the training and support page wasn’t there the last time I checked, so that changes a couple of my claims. Looks interesting! I’m really curious, myself, which model will work out better. With jOOQ and QueryDSL being quite similar in some aspects, we have much to learn from each other.

Leave a Reply