4 ms·
This is based on the assumption that Azure has modern tech, hires well, DR, and better resiliency than LinkedIn's "cloud" for LinkedIn's needs. There's a bit of
by sargun 3y ago
This is based on the assumption that Azure has modern tech, hires well, DR, and better resiliency than LinkedIn's "cloud" for LinkedIn's needs. There's a bit of a problem around incentives here, where Azure is built to sell to Azure's customer base, whereas LinkedIn has evolved their own stack over the years.
The questions become:
1. Does it make sense to dump our special features in the stack, or move them to a higher level in the stack?
2. Does Azure have comparable capabilities for the LinkedIn stack?
3. Is LinkedIn worth it to Azure to sell to?
---
Often times, "at scale", you can support custom solutions outside of cloud providers that are purpose-built, and often times more resilient and efficient than the cloud providers.
AWS has taken a very interesting approach of building an incredibly wide set of solutions to support every customer under the sun, and their approach to being "customer obsessed" leads to them building super niche solutions if the deal is worth it.
I'm not sure how Google and Azure handle these engagements.
- alphager 3y agoGoogle doesn't acknowledge that the customer exists or has wishes. Microsoft will allow you access to the PM of the product if you are big enough, but his answer will be a not-exactly-committing "in 3 years" because their roadmap is full.
- vasco 3y agoEvery once in a while Google acknowledges the customer exists, but usually for a brief moment, either to close their account, or to tell them they are using the product wrong. They promptly go back to work after such brief outings, so as to not fall into the mistake of actually listening.
- everforward 3y ago> 3. Is LinkedIn worth it to Azure to sell to? Microsoft owns both, so that question gets convoluted. It's not really about whether LinkedIn pays Azure enough to care.