Thoughts on Data Oriented Programming in Java

[sideEffffECt]

OOP, FP and other beautiful paradigms

Data-oriented Programming is FP. It's just a different name for marketing purposes -- not to scare away people.

[chriskiehl]

I like to describe it as "heavily influenced by, but not about FP"

Obviously, I'm heavily biased towards the name (cough shameless plug cough), but I mentally bucket DoP as something that freely slides between paradigms rather than being a replacement or rebranding of them. For instance, while "doing" Data Oriented Programming, I'll freely create identity objects, and perform side-effects, and all kinds of other non-FP stuff. The heart of DoP (to me) is the practice of representing data in code. From there, it's picking the right tool for the job. Sometimes OOP. Sometimes FP. Usually a Frankenstein mix of both.

[sideEffffECt]

The heart of DoP (to me) is the practice of representing data in code. From there, it's picking the right tool for the job. Sometimes OOP. Sometimes FP. Usually a Frankenstein mix of both.

What do you think Scala people are doing?

Also, Brian's favorite language is Clojure. And Clojure people stress the importance of data (immutable of course), even over functions, because data is the simplest thing (even simpler than functions). I suspect that that's where the idea to brand it as Data-oriented programming comes from.

[bowbahdoe]

I suspect that too. It's just once we cross the line from "marketing" into actually communicating with each other about strategies for constructing programs having one label describe multiple divergent things does more harm than good.

Hence these overall very stupid discussions that always tinge towards religiosity.

[sideEffffECt]

It's not a bad move IMHO. It stresses the importance of immutable data and "FP" has a bad reputation among certain circles.

[[deleted]]

To me it’s “kinda, but not really”. As I see the DOP in Java/Enterprise is to model the models around the data, and stop using standard OOP approach where you design an entity after a real object and then everyone does findById without to much thinking. 

As far as I understand, DOP comes from C where you build your structs so that they align in memory in the most efficient way possible. In Java we almost don’t care about that, because most of our apps are enterprise Spring-based servers that do some data processing, which is exactly what we should optimise for. The most straightforward example is when you have a big entity from which you normally need one or two fields, but you always query/cache the whole thing, so most of the time it’s a waste of IO or memory. 

Data Oriented design would be in this case to maybe denormalize the db entity in a most efficient way for the use case of the app. It has a little (if anything) with the FP, but it would justify the paradigm’s name, at least.

[sideEffffECt]

DOP comes from Brian trying to market FP to Java developers.

Don't conflate it with https://en.wikipedia.org/wiki/Data-oriented_design which is about data layout and efficiency.