pqyzwbq

Maybe you can check:

  - https://github.com/turbot/steampipe (which will query the sources on demand): Use SQL to instantly query your cloud services (AWS, Azure, GCP and more). Open source CLI. No DB required.

  - https://github.com/cloudquery/cloudquery (which will retrieve data in batch, and save them into another database for query)

Already switched to fly.io. It is also great, and its VM will not "sleeping while inactive"

It is very hard to develop on premise product.

First you need to works with different Linux OS (ubuntu, redhat, etc.), and nowadays, product may contain a lot of microservice, then you need a kubernetes cluster, which is very hard to maintain. And then, you need to find a good storage (object/blob storage) for kubernetes.

Then, you may need to often troubleshooting server issues (like, disk full, slow disk issue, out of memory, kubernetes network broken). And you need to often check whether the data backup system works.

It is much easier to operate as SaaS, and you can pick your OS and your machine spec, and your programing stacks

Scala was fun when my company was small.

Later, we need to recruit more people, it became harder and harder. Each need to learn a lot before they can contribute bug fix to product. They need to learn:

  - Scala

  - Akka

  - very basic of sbt (if they need to change more than basic usage, they come to me for that change, as I'm the only one who learned complex sbt syntax in our team currently)

  - Play framework

  - Slick

But now, several years later, Akka's license change really make us to consider switch back to plain Java and Maven one part by another. For the actor model, I really like it, it can simplify Synchronization A lot, we researched Vert.X, which seems can do most of Akka (Although I haven't research whether Akka Clustering, persistent can work similar in Vert.X yet).

I planned to write a series of articles about how to build distributed applications on Akka Clustering, now, there's no need for that. I wish I didn't recommend Akka to my friends. Thanks.

I would also suggest prql, which is also great. Plus: - the license of prql is better (APACHE v2 vs GPL v2) - although having modeling layer is good, but something like dbt-metrics maybe better. In this point, prql is more focus, on querying part.

OK, thanks, didn't notice this when I read it.

Do anyone know if I depends on the following 2: - org.apache.logging.log4j:log4j-api - org.apache.logging.log4j:log4j-to-slf4j

But without dependency on - org.apache.logging.log4j:log4j-core

in this situation, is this safe from this RCE? Thanks.

Edit, This may affect both log4j 2.x and log4j 1.x (see comments bellow, thanks.)