martinsahlen

Alvin CTO here! I think the most useful takeaway for data teams is that spending time to optimize queries and reduce waste is not useless, but probably the timing is better around commitment and contract renegotiation, since you have an up-to-date and fresh perspective on the true consumption and compute need. Then you avoid the situation where the previous spring cleaning was ages ago, and no-one really knows if the current spend is representative or bloated.

I totally agree, I'm also playing around with Play (no pun intended). But as stated in the post - for microservices that are used by other services, I think akka-http makes total sense - especially since it integrates nicely with akka that we are using for tasks / jobs in our platform.