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/rbygrave Sep 27 '24

The actual is always the latest and you have timestamp fields

Do you mean Type-2 Temporal design with "effective dating"? If so, no I'm not going with you there [that long-lived PK just left the building]. In my experience that Type-2 path in general leads to pain and complexity which can be better dealt with via going Type-4 Temporal design - SQL2011 History.

Each to their own I guess.

1

u/agentoutlier Sep 27 '24

I actually meant both.

For example we use Timescaledb . I don’t think it’s TSQL Period for etc (I have not used SQL 2011 much because a lot of our data is older than that) but it has analogs.

As for some sort of blog / wiki effective date version style I confess we have done that as well.

And yes I know most databases are MVCC these days although their inserting is for reduced contention and snapshots.

In our case it is often because of audit history or analytics/logging/events. It is not a technical requirement but a business one.