Right now, my customers are split about 50:30:20 AWS:GPC:Azure
Deploying the app is not complicated - just a bunch of cloud instances and object storage.
What is complicated is interlinking regions/zones, understanding current other offerings (things like lambda, serverless offerings, strategies to simplify/reduce egress, etc)
Thanks - but that is a distinctly unhelpful (and untrue) answer
I have a relatively string on-prem background (decades)
Most of my customers are moving off-prem to the cloud (or going for a hybridized approach)
That trend is not going away any time soon - which is part of why I am looking for a [somewhat] simplified approach to tackling major aspects of each of the providers
(I am already pretty adept at a couple small cloud providers from personal projects and a previous employer - it's getting up to speed with offerings past VPS instances and object storage I need now)
Gus Gorman is someone I would have expected would be identifiable from pop culture, based on the other descriptions I gave of him (collecting fractional cents lopped off transactions, being to flashy with buying a sports car, etc) - if not immediately by name, surely by description: Richard Pryor played him in Superman III
>Many systems use encryption in some way or another. However, when we talk about encryption in the context of modern private messaging services, the word typically has a very specific meaning: it refers to the use of default end-to-end encryption to protect users’ message content. When used in an industry-standard way, this feature ensures that every message will be encrypted using encryption keys that are only known to the communicating parties, and not to the service provider.
>From your perspective as a user, an “encrypted messenger” ensures that each time you start a conversation, your messages will only be readable by the folks you intend to speak with. If the operator of a messaging service tries to view the content of your messages, all they’ll see is useless encrypted junk. That same guarantee holds for anyone who might hack into the provider’s servers, and also, for better or for worse, to law enforcement agencies that serve providers with a subpoena.
>Telegram clearly fails to meet this stronger definition for a simple reason: it does not end-to-end encrypt conversations by default. If you want to use end-to-end encryption in Telegram, you must manually activate an optional end-to-end encryption feature called “Secret Chats” for every single private conversation you want to have. The feature is explicitly not turned on for the vast majority of conversations, and is only available for one-on-one conversations, and never for group chats with more than two people in them.
The Travels of Marco Polo (I prefer the Modern Library edition translated by Manuel Komroff (it was published in 1931, but the source dates to the 13th-14th centuries))
Institutes of the Christian Religion by John Calvin
Regardless of whether you are Protestant or not (or religious or not) - understanding the theological philosophy of one of the great thinkers of the Protestant Reformation is a wonderful addition to your own mental maps fo the world at large
Deploying the app is not complicated - just a bunch of cloud instances and object storage.
What is complicated is interlinking regions/zones, understanding current other offerings (things like lambda, serverless offerings, strategies to simplify/reduce egress, etc)
reply