Why Your Developers Need jOOQ
Upcoming SlideShare
Loading in...5
×
 

Why Your Developers Need jOOQ

on

  • 370 views

So, your developers are all crazy about this bleeding edge database technology called jOOQ. But it costs money and you don't want to spend any on yet another geeky tool? We understand, so we have ...

So, your developers are all crazy about this bleeding edge database technology called jOOQ. But it costs money and you don't want to spend any on yet another geeky tool? We understand, so we have created this presentation to help you understand another aspect of why your developers need jOOQ: They will be much more productive, which in turn lowers your development costs drastically.

See for yourself!

Statistics

Views

Total Views
370
Views on SlideShare
368
Embed Views
2

Actions

Likes
0
Downloads
1
Comments
0

1 Embed 2

http://www.slideee.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Why Your Developers Need jOOQ Why Your Developers Need jOOQ Presentation Transcript

  • Get Back in Control of your SQL Why your developers need jOOQ. SQL and Java could work together so much better if we only let them. Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0
  • What is jOOQ? JDBC vs. jOOQ JPA vs. jOOQ ROI offered by jOOQ jOOQ is SQL written in Java - SQL is from 1974: Mature and robust - Java is from 1995: Mature and robust - Up to date, it is hard to write SQL in Java («hard» means inefficient, error-prone. developers focus on infrastructure instead of business-logic) Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0
  • What is jOOQ? JDBC vs. jOOQ JPA vs. jOOQ ROI offered by jOOQ SQL and Java – in theory Java one jack SQL one plug In this metaphor, electricity is the data (SQL) that flows into your appliance / application (Java) Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0
  • What is jOOQ? JDBC vs. jOOQ JPA vs. jOOQ ROI offered by jOOQ SQL and Java – in practice – a bad fit Java SQL one jack lots of plugs Images from: http://en.wikipedia.org/wiki/AC_power_plugs_and_sockets. License: public domain Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0
  • What is jOOQ? JDBC vs. jOOQ JPA vs. jOOQ ROI offered by jOOQ What JDBC means for your developers With JDBC, your developers have to do a lot of manual, error-prone (dangerous) and inefficient work Images from Flickr. Cables by: Matthew Straubmuller, Greg Grossmeier. License: CC BY SA 2.0. Electric Engineers shown with permission by Marco Sarli, all rights reserved. Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0
  • What is jOOQ? JDBC vs. jOOQ JPA vs. jOOQ ROI offered by jOOQ How JDBC compares with jOOQ JDBC jOOQ Time consuming Time saving Manual work Automated work (code generation) Error prone (no Java typesafety) Error safe (Java typesafety) Errors detected at run time (production) Errors detected at compile time (development) Errors cost XX,XXX.XX € or more Errors cost XXX.XX € or less Databases are all different jOOQ handles database differences Very basic SQL Highly extensible SQL With JDBC, your developers will build something like jOOQ themselves instead of writing business-logic Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0
  • What is jOOQ? JDBC vs. jOOQ JPA vs. jOOQ ROI offered by jOOQ What JPA means for your developers With JPA, your developers use a huge framework with lots of complexity that can get hard to manage Images from Wikimedia. License: public domain. High voltage power lines by Simon Koopmann. License: CC-BY SA 3.0 Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0
  • What is jOOQ? JDBC vs. jOOQ JPA vs. jOOQ ROI offered by jOOQ How JPA compares with jOOQ JPA jOOQ Time consuming Time saving Complex Simple Performance is difficult Performance is easy Writing SQL is hard Writing SQL is easy You need a DBA *and* a JPA expert You only need a DBA JPA defines your whole architecture jOOQ works with any architecture JPA costs much in development efforts jOOQ costs little in development efforts and little in licensing With JPA, your developers will spend a lot of time tuning JPA and a lot of time circumventing JPA Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0
  • What is jOOQ? JDBC vs. jOOQ JPA vs. jOOQ ROI offered by jOOQ What jOOQ means for your developers Java jOOQ SQL one jack one adaptor all plugs With jOOQ, Java plugs into SQL intuitively, letting your developers focus on business-logic again. Images from Wikimedia. License: public domain. Travel converter by Cephira. License: CC-BY SA 3.0 Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0
  • What is jOOQ? JDBC vs. jOOQ JPA vs. jOOQ ROI offered by jOOQ Your ROI with jOOQ REDUCE YOUR OVERALL PRODUCT COSTS Money spent on jOOQ licenses Money spent on development Without jOOQ Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0 With jOOQ
  • Why use jOOQ - Your developers save time - Your developers increase quality - Your customers get better software - And: You save money Copyright (c) 2009-2013 by Data Geekery GmbH. Slides licensed under CC BY SA 3.0