The email sent will contain a link to this article, the article title, and an article excerpt (if available). For security reasons, your IP address will also be included in the sent email.
We're back and it's HighScalability Time:
- 1B Tweets Every 2.5 Days: Twitter. 1 billion transactions/day: Salesforce.
- Storing 700 terabytes of data into a single gram of DNA. Downside, reading is very slow. And any data might conflict with the messages aliens have already inserted.
- Assuming my infonome is 1 TB, it would cost $1,338,333 to store my existence in Amazon Glacier for a long nowish 10,000 years. #notbad
- Quotable Quotes:
- @cloudpundit: @Werner: "I've hugged a lot of servers in my life, and believe me, they do not hug you back. They hate you." #reinvent
- @jinman: Werner #reinvent The commandments of 21st century architectures 1) Controllable, 2)Resilient, 3)Adaptive and 4) Data Driven #cloud
- @dandonovan78: Wow. Netflix video streaming has grown from 1M hours to 1 BILLION hours a month in less than 4 years. Insane. #scalability #aws #reinvent
- @sandfoxuk: Linear scalability - the spherical cow of cloud systems…. #PlanningFail
- @rbranson: the year is 2020. Atomic clocks now embedded in ARM SoCs. Spanner is commodity. Java still limited to 20GB heaps..
- Why I Have Given Up on Coding Standards. As someone with some experience with coding standards, I'll just note that master craftsman operate to a detailed contract where the patron specifies virtually everything of interest. It's very far from a results only mindset. All those people we thought of as great artists before Michelangelo were considered craftsman in their day, someone with a skill employed for money, like a baker. As a programmer on a team you are operating on behalf of a patron and it's their rules over an artistic/star/look at me temperament. To argue for a design standard and not a coding standard is like saying an architect shouldn't care how their bricks are made when it's really the quality of the bricks that dictates structure under stress. If you are building something that isn't under stress you don't need an architect, you don't need to worry about structure, you can just let your heart move you. But when you are building something that matters, that someone is paying for, that is subject to extreme stress, then structure dictates both form and function and a key part of structure is code, so that's why you have a standard. Unfortunately with code we are still stuck in a highly empirical age, so the standards are experience based and highly arguable, so there's a lot of room for displeasure. But Gothic cathedrals were built to the sky using lessons learned from experience and that's essentially what we are doing with software systems.
Don't miss all that the Internet has to say on Scalability, click below and become eventually consistent with all scalability knowledge...
Return to Article