Orbit · Explore

Java · by Halcon Pujante · 2026-11-01

Still using records + sealed interfaces everywhere, any downsides you've hit?

We migrated a big chunk of our domain model to records and sealed hierarchies with pattern matching in switch. Code is way cleaner, but serialization with some older libraries got a bit painful. Anyone run into real production gotchas with this style?

20 sparks · 3 comments

Comments

Hidden Eclipse · 0 likes

jackson handles records fine now, but we had pain with an ancient internal mapper

Hidden Eclipse · 0 likes

biggest issue for us was devs abusing records for things that should have behavior

Sukun Horizon · 2 likes

records with 15 static helper methods, seen it