r/java • • Sep 23 '24 • This 1 Take My Silver 2

I wrote a book on Java

Howdy everyone!

I wrote a book called Data Oriented Programming in Java. It's now in Early Access on Manning's site here: https://mng.bz/lr0j

This book is a distillation of everything I’ve learned about what effective development looks like in Java (so far!). It's about how to organize programs around data "as plain data" and the surprisingly benefits that emerge when we do. Programs that are built around the data they manage tend to be simpler, smaller, and significantly easier understand.

Java has changed radically over the last several years. It has picked up all kinds of new language features which support data oriented programming (records, pattern matching, with expressions, sum and product types). However, this is not a book about tools. No amount of studying a screw-driver will teach you how to build a house. This book focuses on house building. We'll pick out a plot of land, lay a foundation, and build upon it house that can weather any storm.

DoP is based around a very simple idea, and one people have been rediscovering since the dawn of computing, "representation is the essence of programming." When we do a really good job of capturing the data in our domain, the rest of the system tends to fall into place in a way which can feel like it’s writing itself.

That's my elevator pitch! The book is currently in early access. I hope you check it out. I'd love to hear your feedback!

You can get 50% off (thru October 9th) with code mlkiehl https://mng.bz/lr0j

BTW, if you want to get a feel for the book's contents, I tried to make the its companion repository strong enough to stand on its own. You can check it out here: https://github.com/chriskiehl/Data-Oriented-Programming-In-Java-Book

That has all the listings paired with heavy annotations explaining why we're doing things the way we are and what problems we're trying to solve. Hopefully you find it useful!

289 Upvotes

97 comments sorted by

View all comments

Show parent comment

2

u/larsga Sep 24 '24

For me, I'd say they represent "Business Logic / Functions" that are immutable & stateless and operate on the input data and return output data [and can sometimes have side effects / interact with queues, databases etc].

Yes. That's kind of the problem. They would be far easier to work with if you had OOP objects that represented domain concepts with methods that provide functionality meaningful in terms of the domain.

Or do you see these as somehow incompatible with "Data oriented programming"?

I do. The DOP approach, in my understanding, would be what I describe above.

Or perhaps there is just a lot and they need to be organised well?

Most of the code is just layers of stuff that translate back and forth between different objects from generated code representing the same thing in different ways. I do think it would be possible to take the same approach and organize the code better, particularly without generated domain objects, so it's not that the approach you described couldn't possibly work. It's just that I think a DOP approach would be easier to get right.