platform android iOS desktop cli server
signal   yes     yes yes     no  yes
wire     yes     yes yes     no  yes
whatsapp no      no  no      no  no
telegram yes     yes yes     no  no

This article has many factual flaws. EMR is not a clone of s3mper. Trolly title, as well, as its really about the API of S3, not the architecture. (which the author knows nothing about)

Great guide! One small note; you should use AWS credentials associated with an IAM role that has the least privileges required to get the job done. In this case, using creds from an IAM role that could only write to the particular S3 bucket and invalidate the specific CloudFront domain would be most secure.

I’ve not read this yet. I’m cautious about new kinds of trees. I didn’t see much in a scan of the readme about balancing. My initial question is how this compares to a Scapegoat Tree.

This post is describing CQRS. It has existed and been pretty well fleshed-out for some time now. It also seems to misunderstand the term “domain-driven design”, as CQRS is a key technique in DDD.

I see future customer-base-impacting issues with this move for Jetbrains. E.g. a Jetbrains customer that uses their software and likes it can no longer afford the subscription, for whatever reason. They will of course find something else to use because they have to get their work done. They may or may not like as much, but its quite unlikely they will ever come back to Jetbrains. Perhaps this is offset by the rate of new customer acquisition, but perhaps its not. Adobe found that it was not and they had much “stickier” products than Jetbrains sells, in that, there were sometimes no good alternatives to the software Adobe sold.