high_scalability high_scalability-2014 high_scalability-2014-1571 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: The great thing about standards is there are so many to choose from. What is it about human nature that makes this so recognizably true?
sentIndex sentText sentNum sentScore
1 The great thing about standards is there are so many to choose from. [sent-1, score-1.482]
2 What is it about human nature that makes this so recognizably true? [sent-2, score-0.961]
wordName wordTfidf (topN-words)
[('standards', 0.529), ('choose', 0.39), ('nature', 0.38), ('human', 0.379), ('true', 0.35), ('thing', 0.267), ('makes', 0.202), ('great', 0.174), ('many', 0.122)]
simIndex simValue blogId blogTitle
same-blog 1 1.0 1571 high scalability-2014-01-02-xkcd: How Standards Proliferate:
Introduction: The great thing about standards is there are so many to choose from. What is it about human nature that makes this so recognizably true?
2 0.1188164 852 high scalability-2010-07-07-Strategy: Recompute Instead of Remember Big Data
Introduction: Professor Lance Fortnow, in his blog post Drowning in Data , says complexity has taught him this lesson: When storage is expensive, it is cheaper to recompute what you've already computed. And that's the world we now live in: Storage is pretty cheap but data acquisition and computation are even cheaper. Jouni, one of the commenters, thinks the opposite is true: storage is cheap, but computation is expensive. When you are dealing with massive data, the size of the data set is very often determined by the amount of computing power available for a certain price . With such data, a linear-time algorithm takes O(1) seconds to finish, while a quadratic-time algorithm requires O(n) seconds. But as computing power increases exponentially over time, the quadratic algorithm gets exponentially slower . For me it's not a matter of which is true, both positions can be true, but what's interesting is to think that storage and computation are in some cases fungible. Your architecture can dec
3 0.11874673 919 high scalability-2010-10-14-I, Cloud
Introduction: Every time a technological innovation has spurred automation – since the time of Henry Ford right up to a minute ago – someone has claimed that machines will displace human beings. But the rainbow and unicorn dream attributed to business stakeholders everywhere, i.e. the elimination of IT, is just that – a dream. It isn’t realistic and in fact it’s downright silly to think that systems that only a few years ago were unable to automatically scale up and scale down will suddenly be able to perform the complex analysis required of IT to keep the business running. The rare reports of the elimination of IT staff due to cloud computing and automation are highlighted in the news because they evoke visceral reactions in technologists everywhere and, to be honest, they get the click counts rising. But the jury remains out on this one and in fact many postulate that it is not a reduction in staff that will occur, but a transformation of staff, which may eliminate some old timey positions
4 0.11210758 56 high scalability-2007-08-03-Running Hadoop MapReduce on Amazon EC2 and Amazon S3
Introduction: Excellent article on using Hadoop in Amazon's services environment to solve real problems for very little money. It's excellent because it shows how the stack works together and it actually seems like something a real human could do.
5 0.1005505 403 high scalability-2008-10-06-Paper: Scaling Genome Sequencing - Complete Genomics Technology Overview
Introduction: Although the problem of scaling human genome sequencing is not exactly about building bigger, faster and more reliable websites it is most interesting in terms of scalability. The paper describes a new technology by the startup company Complete Genomics to sequence the full human genome for the fraction of the cost of earlier possibilities. Complete Genomics is building the world’s largest commercial human genome sequencing center to provide turnkey, outsourced complete human genome sequencing to customers worldwide. By 2010, their data center will contain approximately 60,000 processors with 30 petabytes of storage running their sequencing software on Linux clusters. Do you find this interesting and relevant to HighScalability.com?
6 0.098500021 11 high scalability-2007-07-15-Coyote Point Load Balancing Systems
7 0.093125001 26 high scalability-2007-07-25-Paper: Lightweight Web servers
8 0.081252187 1556 high scalability-2013-11-29-One Story of Life as Told Through Queues
9 0.080566168 918 high scalability-2010-10-12-The CIO’s Problem: Cloud “Mess” or Cloud “Mash”
10 0.076595128 1592 high scalability-2014-02-07-Stuff The Internet Says On Scalability For February 7th, 2014
11 0.070970438 1150 high scalability-2011-12-02-Stuff The Internet Says On Scalability For December 2, 2011
12 0.066981345 1516 high scalability-2013-09-13-Stuff The Internet Says On Scalability For September 13, 2013
13 0.065476641 950 high scalability-2010-11-30-NoCAP – Part III – GigaSpaces clustering explained..
14 0.064388834 626 high scalability-2009-06-10-Paper: Graph Databases and the Future of Large-Scale Knowledge Management
15 0.059544172 1199 high scalability-2012-02-27-Zen and the Art of Scaling - A Koan and Epigram Approach
16 0.057538427 1092 high scalability-2011-08-04-Jim Starkey is Creating a Brave New World by Rethinking Databases for the Cloud
17 0.057481874 1354 high scalability-2012-11-05-Are we seeing the renaissance of enterprises in the cloud?
18 0.057106424 1365 high scalability-2012-11-30-Stuff The Internet Says On Scalability For November 30, 2012
19 0.056385424 340 high scalability-2008-06-06-Economies of Non-Scale
20 0.054866895 877 high scalability-2010-08-12-Designing Web Applications for Scalability
topicId topicWeight
[(0, 0.047), (1, 0.04), (2, 0.004), (3, 0.034), (4, -0.001), (5, -0.022), (6, -0.012), (7, 0.02), (8, -0.008), (9, -0.011), (10, -0.011), (11, 0.011), (12, -0.019), (13, 0.028), (14, 0.007), (15, -0.014), (16, 0.051), (17, 0.008), (18, 0.001), (19, 0.004), (20, -0.026), (21, -0.021), (22, 0.002), (23, 0.007), (24, -0.011), (25, 0.003), (26, 0.011), (27, 0.009), (28, -0.023), (29, 0.015), (30, -0.053), (31, 0.025), (32, 0.009), (33, -0.012), (34, -0.001), (35, 0.01), (36, 0.018), (37, 0.046), (38, 0.029), (39, -0.027), (40, -0.007), (41, -0.005), (42, 0.001), (43, 0.002), (44, -0.001), (45, 0.033), (46, 0.018), (47, 0.0), (48, -0.004), (49, -0.067)]
simIndex simValue blogId blogTitle
same-blog 1 0.98301136 1571 high scalability-2014-01-02-xkcd: How Standards Proliferate:
Introduction: The great thing about standards is there are so many to choose from. What is it about human nature that makes this so recognizably true?
2 0.6333276 1556 high scalability-2013-11-29-One Story of Life as Told Through Queues
Introduction: Love this little example of the human condition from John Kellden  via Ilya Grigorik . This happens so often to me shopping at Costco or making lane changes on the highway or picking stocks. Sometimes it's just never the right line and trying to make it better only makes it worse. Stick and stay. Buy and hold. Live to queue another day.
3 0.61254901 390 high scalability-2008-09-23-Scaling your cookie recipes
Introduction: This article on scaling cookie baking recipes showed up in one my key word alerts. Lots of weird things show up in alerts, but I really like cookies and the parallels were just so delicious. Scaling in the cookie baking world is: the process of multiplying your recipe by many times to produce much more dough for many more cookies. It’s the difference between making enough dough in one batch to make two dozen cookies, or 2000 cookies. Hey, pretty close to the website notion. Yet as any good cook knows any scaled up recipe must be tweaked a little as things change at scale. Let's see what else we're supposed to do (quoted from the article): Be Patient - When making large batches of cookies, the most important thing that you have to remember is not to rush. Use Fresh Ingredients - This is always an important thing to keep in mind. Don’t use as much leavening - When you’re making a large batch of cookie dough, remember to scale down the amount of baking powder that you
4 0.58571213 1524 high scalability-2013-09-30-Expandability: Steve Wozniak's Biggest Success and Nolan Bushnell's Biggest Regret
Introduction: When two titans of the early computing industry, Apple co-founder Steve Wozniak and Atari founder Nolan Bushnell , had a chance to sit down for a chat at the C2SV conference last Friday, we learned how a little foresight and luck can decide futures. Steve Wozniak's Success - Expandability Steve talked about how the Apple II was the primary source of revenue for Apple's first 10 years of life. The reason the Apple II could last so long was that it was expandable. It had eight expansion slots and the RAM was also expandable (starting at 4K). No computer at the time had this kind of flexibility or expansion capabilities . Steve Wozniak and Steve Jobs argued over keeping the Apple II open. Jobs wanted closed, Wozniak wanted open and fortunately Wozniak won. In fact, the Apple II was completely open (those were the days). They published the complete specs before there was anything like a developer community. So even though the Apple III, Lisa, and the Macintosh al
5 0.57949865 347 high scalability-2008-07-07-Five Ways to Stop Framework Fixation from Crashing Your Scaling Strategy
Introduction: If you've wondered why I haven't been posting lately it's because I've been on an amazing Beach's motorcycle tour of the Alps ( and , and , and , and , and , and , and , and ). My wife (Linda) and I rode two-up on a BMW 1200 GS through the alps in Germany, Austria, Switzerland, Italy, Slovenia, and Lichtenstein. The trip was more beautiful than I ever imagined. We rode challenging mountain pass after mountain pass, froze in the rain, baked in the heat, woke up on excellent Italian coffee, ate slice after slice of tasty apple strudel, drank dazzling local wines, smelled the fresh cut grass as the Swiss en masse cut hay for the winter feeding of their dairy cows, rode the amazing Munich train system, listened as cow bells tinkled like wind chimes throughout small valleys, drank water from a pure alpine spring on a blisteringly hot hike, watched local German folk dancers represent their regions, and had fun in the company of fellow riders. Magical. They say you'll ride more
6 0.56626099 352 high scalability-2008-07-18-Robert Scoble's Rules for Successfully Scaling Startups
7 0.55387855 1503 high scalability-2013-08-19-What can the Amazing Race to the South Pole Teach us About Startups?
8 0.54997009 1027 high scalability-2011-04-20-Packet Pushers: How to Build a Low Cost Data Center
9 0.54635555 1635 high scalability-2014-04-21-This is why Microsoft won. And why they lost.
10 0.54474556 1172 high scalability-2012-01-10-A Perfect Fifth of Notes on Scalability
11 0.53754365 1462 high scalability-2013-05-22-Strategy: Stop Using Linked-Lists
12 0.53499448 1263 high scalability-2012-06-13-Why My Soap Film is Better than Your Hadoop Cluster
13 0.53219664 403 high scalability-2008-10-06-Paper: Scaling Genome Sequencing - Complete Genomics Technology Overview
15 0.53057045 193 high scalability-2007-12-26-Finding an excellent LAMP developer
16 0.52873713 1534 high scalability-2013-10-18-Stuff The Internet Says On Scalability For October 18th, 2013
17 0.52812976 1506 high scalability-2013-08-23-Stuff The Internet Says On Scalability For August 23, 2013
18 0.52767968 1388 high scalability-2013-01-16-What if Cars Were Rented Like We Hire Programmers?
19 0.52699012 120 high scalability-2007-10-11-How Flickr Handles Moving You to Another Shard
20 0.52433509 1500 high scalability-2013-08-12-100 Curse Free Lessons from Gordon Ramsay on Building Great Software
topicId topicWeight
[(2, 0.234), (10, 0.11), (61, 0.161), (77, 0.242)]
simIndex simValue blogId blogTitle
same-blog 1 0.95290059 1571 high scalability-2014-01-02-xkcd: How Standards Proliferate:
Introduction: The great thing about standards is there are so many to choose from. What is it about human nature that makes this so recognizably true?
Introduction: Successful software design is all about trade-offs. In the typical (if there is such a thing) distributed system, recognizing the importance of trade-offs within the design of your architecture is integral to the success of your system. Despite this reality, I see time and time again, developers choosing a particular solution based on an ill-placed belief in their solution as a “silver bullet”, or a solution that conquers all, despite the inevitable occurrence of changing requirements. Regardless of the reasons behind this phenomenon, I’d like to outline a few of the methods I use to ensure that I’m making good scalable decisions without losing sight of the trade-offs that accompany them. I’d also like to compile (pun intended) the issues at hand, by formulating a simple theorem that we can use to describe this oft occurring situation.
3 0.85301292 258 high scalability-2008-02-24-Yandex Architecture
Introduction: Update: Anatomy of a crash in a new part of Yandex written in Django . Writing to a magic session variable caused an unexpected write into an InnoDB database on every request. Writes took 6-7 seconds because of index rebuilding. Lots of useful details on the sizing of their system, what went wrong, and how they fixed it. Yandex is a Russian search engine with 3.5 billion pages in their search index. We only know a few fun facts about how they do things, nothing at a detailed architecture level. Hopefully we'll learn more later, but I thought it would still be interesting. From Allen Stern's interview with Yandex's CTO Ilya Segalovich, we learn: 3.5 billion pages in the search index. Over several thousand servers. 35 million searches a day. Several data centers around Russia. Two-layer architecture. The database is split in pieces and when a search is requested, it pulls the bits from the different database servers and brings it together for the user. Languages
4 0.84431183 766 high scalability-2010-01-26-Product: HyperGraphDB - A Graph Database
Introduction: With the success of Neo4j as a graph database in the NoSQL revolution, it's interesting to see another graph database, HyperGraphDB , in the mix. Their quick blurb on HyperGraphDB says it is a: general purpose, extensible, portable, distributed, embeddable, open-source data storage mechanism. It is a graph database designed specifically for artificial intelligence and semantic web projects, it can also be used as an embedded object-oriented database for projects of all sizes. From the NoSQL Archive the summary on HyperGraphDB is: API: Java (and Java Langs), Written in: Java , Query Method: Java or P2P, Replication: P2P , Concurrency: STM , Misc: Open-Source, Especially for AI and Semantic Web. So it has some interesting features, like software transactional memory and P2P for data distribution , but I found that my first and most obvious question was not answered: what the heck is a hypergraph and why do I care? Buried in the tutorial was: A HyperGraphD
5 0.82782441 1059 high scalability-2011-06-14-A TripAdvisor Short
Introduction: Sometimes I get article proposals and then there's no follow up. Though these TripAdvisor data points are from 2010, I thought them worth sharing: Our site serves in excess of 100M dynamically generated page view a day (all media and static content goes through CDN), and we do this with about 100 machines, no single point of failure, supported by distributed service architecture that that responds to over 2B requests a day, and a data warehouse of over 20TB that is used to drive email campaigns, SEM, and general reporting. We are a Linux/Java/Apache/Tomcat/Postgres/Lucene shop, and have built our own distributed computing architecture. We also maintain duplicate data centers (one active, one standby) for redundancy and maintenance purposes. Too bad, it sounds like it would have been a good article. Related Articles A new twist on "data-driven site" by Mac Slocum. How a billion points of app data shape TripAdvisor's website.
6 0.79632086 959 high scalability-2010-12-17-Stuff the Internet Says on Scalability For December 17th, 2010
7 0.79433107 1116 high scalability-2011-09-15-Paper: It's Time for Low Latency - Inventing the 1 Microsecond Datacenter
8 0.78218156 1195 high scalability-2012-02-17-Stuff The Internet Says On Scalability For February 17, 2012
9 0.76494521 753 high scalability-2009-12-21-Hot Holiday Scalability Links for 2009
10 0.76157689 1158 high scalability-2011-12-16-Stuff The Internet Says On Scalability For December 16, 2011
11 0.74545753 1377 high scalability-2012-12-26-Ask HS: What will programming and architecture look like in 2020?
12 0.74359071 1531 high scalability-2013-10-13-AIDA: Badoo’s journey into Continuous Integration
13 0.73921406 211 high scalability-2008-01-13-Google Reveals New MapReduce Stats
14 0.7342394 52 high scalability-2007-08-01-Product: Memcached
15 0.73269212 1567 high scalability-2013-12-20-Stuff The Internet Says On Scalability For December 20th, 2013
16 0.72736758 1493 high scalability-2013-07-17-Steve Ballmer Says Microsoft has Over 1 Million Servers - What Does that Really Mean?
17 0.72653383 342 high scalability-2008-06-08-Search fast in million rows
18 0.71520531 635 high scalability-2009-06-22-Improving performance and scalability with DDD
19 0.70100981 1287 high scalability-2012-07-20-Stuff The Internet Says On Scalability For July 20, 2012
20 0.69953489 525 high scalability-2009-03-05-Product: Amazon Simple Storage Service