Escape from the Planet of the Collections by Stuart Marks, Maurice Naftalin

Record classes should be used carefully with collections since they cannot guarantee true immutability if containing mutable components like collections

When working with collections, follow these key principles:

• Only mutate collections that you own
• Make defensive copies when accepting collections from outside
• Use unmodifiable wrappers to prevent modification
• Keep collections encapsulated within classes

The Java Collections Framework has limitations around int-based sizes and indices, making it challenging to work with collections containing more than 2^31 elements

HashSets and TreeSets with different equivalence relations don’t mix well and can lead to unexpected behaviors around equality and duplicates

Avoid using inheritance to modify collection behavior - prefer delegation and encapsulation instead

Project Valhalla will help address some collections issues through:

• Value types that can be flattened into arrays
• Better support for primitive collections
• Reduced memory overhead per object

For large datasets:

• Consider alternatives to LinkedList due to high per-node overhead
• Be aware of memory/performance tradeoffs with different collection types
• HashMap’s internal table size is limited by array size restrictions

Using composite keys and proper encapsulation is better than contorting object designs around collection limitations

The Collections Framework was designed with mutability in mind - immutability has to be handled through wrappers and defensive programming

Consider performance characteristics when choosing collection types - linear search in lists vs constant time operations in hash-based collections