Software

INTEGU-java-best-practices-85-Avoid-serialization

Serialization

Avoid Java serialization if possible

Serialization was intended as a utility within the Java language, which allows objects to be converted into bytes (serialized), send to another endpoint, and reconstructed as an object again (deserialized). This is necessary since java objects only exists within the JVM and can therefore not be send directly.

INTEGU-java-best-practices-84-thread-schedulers

Concurrency

78. Use Synchronize When Handling Mutable Methods
When working with threads, synchronize on mutable methods becomes a valuable resource. This is because of two reasons:

Synchronize ensure the method can only be accessed by one thread at a time. Any thread attempting to execute the method while it is already in use, will be put on hold until the method is available again.
Because the threads are set to wait for each other, synchronize also guarantee that each thread will be able to see changes to the mutable method made by previous threads.
A mutable method could for example be a method providing an incremental serial number based on a field instance.

INTEGU-java-best-practices-85-Avoid-serialization

Exceptions

Exceptions only for exceptional scenarios

Exceptions are a way of causing the system to quickly alert the system of some unexpected scenario. However, some people might start using exceptions as a functionality of the system and start relying on the to convey acceptable scenarios.

INTEGU-java-best-practices-57-minimize-scope-58-for-each-over-for-loop

General Programming

Minimize scope of local variables.

Local variables should be contained within the smallest scope possible.

The most optimal solution is therefore to create the local variable the same place as it is used. Thereby increasing the readability of the code and minimizing the chance of misusing the variable.

INTEGU-java-best-practices-49-argument-validity-50-defensive-copies

Methods

Assert method arguments validity
Whenever an object is given in as a method argument, it should be asserted in terms of validity as the first thing.

This can be done with something as Objects.requireNonNull(arg), which will throw an exception if the argument is null.

Additionally, if you want to determine which arguments, should be allowed to be nullable, the @Nullable annotation can be used.

Scroll to Top