✳flâneur — a map of the web's best reading

Why You Should NOT Implement Layered Architectures – Java, SQL and jOOQ.

blog.jooq.org · 658 words · saved by 1 readers

Best Practices and Lessons Learned from Writing Awesome Java and SQL Code. Get some hands-on insight on what's behind developing jOOQ. Abstraction layers in software are what architecture astronauts tell you to do. Instead, however, half of all applications out there would be so easy, fun, and most importantly: productive to implement if you just got rid of all those layers. Frankly, what do you really need? You need these two: Because that’s the two things that you inevitably have in most systems. Users, and data. Here’s Kyle Boon’s opinion on possible choices that you may have Really enjoying #ratpack and #jooq. — Kyle Boon (@kyleboon) September 2, 2014 Very nice choice, Kyle. Ratpack and jOOQ. You could choose any other APIs, of course. You could even choose to write JDBC directly in JSP. Why not. As long as you don’t go pile up 13 layers of abstraction: That’s all bollocks, you’re saying? We need layers to abstract away the underlying implementation so we can change it? OK, let’s g

Abstraction layers in software are what architecture astronauts tell you to do. Instead, however, half of all applications out there would be so easy, fun, and most importantly: productive to implement if you just got rid of all those layers. Frankly, what do you really need? You need these two: Some data access Some UI Because that’s the two things that you inevitably have in most systems. Users, and data. Here’s Kyle Boon’s opinion on possible choices that you may have Really enjoying #ratpack and #jooq . - Kyle Boon (@kyleboon) September 2, 2014 Very nice choice, Kyle. Rat

Explore this link on the map →

related reading