[irq]: techie interrupted


“ What we have seen is that a logically centralized, hierarchical control plane with a peer-to-peer data plane beats full decentralization,” explained Vahdat in his keynote. “All of these flew in the face of conventional wisdom,” he continued, referring to all of those projects above, and added that everyone was shocked back in 2002 that Google would, for instance, build a large-scale storage system like GFS with centralized control. “We are actually pretty confident in the design pattern at this point. We can build a fundamentally more efficient system by prudently leveraging centralization rather than trying to manage things in a peer-to-peer, decentralized manner. „

Google Lifts Veil On “Andromeda” Virtual Networking


“ I think enterprises should care more about full stack independence to manage vertical risk. Why? When a technology is vertically prescriptive (i.e. Pivotal CF One requiring VMware), it hurts an organizations’ ability to manage supply chain risk by ensuring they can source vendors to fulfill needs at other parts in the stack. This means that a customer loses cost control leverage, feature leverage, and can be held hostage in the face of overall stack quality degradation. By optimizing for vertical independence, an enterprise ensures that vendor selection at any tier in the IT stack does not dictate what vendors they use above and below that part of the stack. „

The LIES That Come With Some Flavors of PaaS


“ It used to be that the physical hardware was orders of magnitude more expensive than engineers but this hasn’t been true for decades now - it’s perfectly reasonable to look for ways to reduce yours costs especially if it can be done quickly but obsessing over hardware costs, especially while you’re still growing, is a red herring. Building large systems is tough and the fewer things you have to worry about the better - using AWS reduces the chance that you will run into a scenario where you’re just not able to do something without changing your host and rewriting your architecture. „

AWS is about infrastructure optionality


“ Imagine a cloud in which servers were automatically decommissioned after a week of use. In a sort of DevOps anti-SLA, any VM running for more than 168 hours would be (gracefully) terminated. This would force a constant churn of resources within the infrastructure that enables true cattle-like management. This cloud would be able to very gracefully rebalance load and handle disruptive management operations because the workloads are designed for the churn. „

Mayflies and Dinosaurs (extending Puppies and Cattle) | Rob Hirschfeld


“ The thing you have to get comfortable with is you’re relinquishing a lot of control to this system and allowing it to do the right thing for you, and trusting it – it may take steps you don’t know about," Neil says. "These systems are so large that no one person is keeping track. That’s what the system is designed to do – take care of the details. „

Inside Microsoft’s Autopilot: Nadella’s secret cloud weapon • The Register



“ It’s scale that funds the innovations and it’s scale that makes even small gains worth pursuing since the multiplier is so large. „

Perspectives - The Cloud: Fastest Industry Transition Ever



“ We gave every engineer a full AWS IAM account, allowing them unfettered access to Amazon’s wide array of higher level services like Simple Work Flow service, Elastic MapReduce, and Redshift. We chose to optimize for engineer agility over efficiency. But to make sure that our costs don’t get completely out of hand, the Platform Infrastructure team enforces tag conformity. To conform, each team must use two tags across all of their resources: team and VPC. Any AWS resource without proper tags is automatically terminated. One huge benefit of having consistent and enforced tagging is that we were able to determine the exact cost per team. „

High Scalability - High Scalability - Evolution of Bazaarvoice’s Architecture to 500M Unique Users Per Month


“ Over the last two years, I have had the chance to validate these guidelines with many SaaS businesses, and it turns out that these early guesses have held up well. The best SaaS businesses have a LTV to CAC ratio that is higher than 3, sometimes as high as 7 or 8. And many of the best SaaS businesses are able to recover their CAC in 5-7 months. However many healthy SaaS businesses don’t meet the guidelines in the early days, but can see how they can improve the business over time to get there. „

SaaS Metrics 2.0 – A Guide to Measuring and Improving what Matters | For Entrepreneurs

blog comments powered by Disqus
page 1 of 99 | next »
Tumblr » powered Sid05 » templated Disquss » commented