Isn't this tiered support a necessity when operating at scale? How can you help thousands of customers where faqs and getting starteds don't cut it? You need a filtering mechanism (L1) to help users directly without overloading the product team with a standard reply rtfm.
But then the main contributor, Lightbend company, decided to change the license from Apache 2, to BSL.. Now Apache Pekko is the fork that should continue the implementation :)
Nice write-up, and good to see that maven also evolves. The use of the daemon is really significant for the build time. Is there any clue what would take 90 seconds everytime you execute the maven process? Is it the creating of the build graph and its dependencies? What would happen when I change my dependencies or module structure, does the daemon still stay on 30 seconds?
Scala happily accepts null as it is the bottom type for AnyRef and needed for jvm compatibility. Kotlin has a compiler check that enforces it, Scala does not.
This might be your first instinct, but a new contractor would have to gain the knowledge KPN did on preventing these outages, there is no guarantee any other company would have better uptime.
Reminds me of the quote or story that someone rather hired an ops engineer that accidentally dropped a database than someone who didn't. As the first one would go at more length preventing to do it again.