Null is biggest flaw of Java, saying some developers. Null causes NPEs causes crashing software. IMHO this is the same vibe as C vs Rust and I totally disagree. Crashing software is caused by developers and not by the programming language.
The easiest and best way to prevent NPEs is … proper exception handling. It is as simple as it sounds.
Bye the way, NPEs are often a side effect of OOP. All Objects are unsafe until you checked them. But checks are unsafe so go with exception handling.
For most software companies resilience means that the replication factor is 2 or higher.
Well that's far from good. You resilience is still bad as with two instances of your weak micro service.
One way to increase the internal resilience of your service is to decouple external service calls. This includes Data Base operations, Kafka, HTTP. For HTTP calls it is very common and most developer understand that this HTTP calls can go wrong but Data Base calls, yes all external services are running over a network, firewall, load balancer, switches, ... So it's a good idea to make all external call more resilient:
