Don't use setters and getters in your models. Use public fields, add getters and setters if you have to. Serialize your POJOs using Jackson. All modern data fr

Don't use setters and getters in your models. Use public fields, add getters and setters if you have to. Serialize your POJOs using Jackson. All modern data frameworks can deal with public fields just as well as getter/setter combinations. (Unless you are publishing a public API. In that case, you can't easily convert a public field to a private field/getter/setter setup if needed, as the cat is out of the bag and clients have code against the public field.) Do I wish there were auto properties like C#? Oh yeah, I'd love that. But I do find modeling fairly easy. I also lament having to manually maintain equals/compare/hashCode/toString implementations. However, with IDE auto-generation of code (using IntelliJ) makes this merely noisy and annoying, and not a time sink or a constant source of dumb errors.