4 ms·
It means that for certain functions you need people on site, so someone can physically get to the server or router that is causing the problem. It doesn't mean
by not2b 5y ago
It means that for certain functions you need people on site, so someone can physically get to the server or router that is causing the problem. It doesn't mean you suddenly need everyone on site.
It may also mean that you need more decentralization. They put all their eggs in one basket, so they took down Instagram, Messenger, and WhatsApp as well as Facebook, as well as their internal network, their building security, everything. Seems that they need to look at redesign to create more resiliency even if some efficiency is lost, so they don't lose everything again at some point.
- treesknees 5y agoIs this what happens when product engineering runs the company? In all of my previous jobs, the production customer-facing systems have been separated from the internal day-to-day IT systems. Beyond potentially sharing a physical building/dc, IT and engineering could in no way interfere with each other.
- Jare 5y agoIf your company dogfoods their own products then this can happen. I would expect the value of dogfooding to be massively larger than the cost of internal losses in cases like this. But it's good to remember to have a plan B.
- treesknees 5y agoI'm not sure I agree. It's one thing to treat IT as a customer for a product or service your company offers. I don't doubt that the business also uses FB messenger to communicate for example. But FB as a consumer product doesn't offer DNS or SAML or any of these other critical services, so why would IT share infrastructure for those? That's not dogfooding.
- htrp 5y agoIts a very efficient single point of failure