high_scalability high_scalability-2009 high_scalability-2009-500 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: I follow a certain philosophy when developing system architectures. I assume that very few systems will ever exist in a consistent form for more than a short period of time. What constitutes a “short period of time” differs depending on the specifics of each system, but in an effort to quantify it, I generally find that it falls somewhere between a week and a month. The driving forces behind the need for an ever changing architecture are largely business requirement based. This is a side effect of the reality that software development, in most cases, is used as a supporting role within the business unit it serves. As business requirements (i.e. additional features, new products, etc.) pour forth, it is the developer’s job to evolve their software system to accommodate these requirements and provide a software based solution to whatever problems lay ahead. Given that many businesses can be identified as having the above characteristics, I can now begin to explain why I believe t
sentIndex sentText sentNum sentScore
1 I follow a certain philosophy when developing system architectures. [sent-1, score-0.455]
2 I assume that very few systems will ever exist in a consistent form for more than a short period of time. [sent-2, score-0.705]
3 What constitutes a “short period of time” differs depending on the specifics of each system, but in an effort to quantify it, I generally find that it falls somewhere between a week and a month. [sent-3, score-1.603]
4 The driving forces behind the need for an ever changing architecture are largely business requirement based. [sent-4, score-0.784]
5 This is a side effect of the reality that software development, in most cases, is used as a supporting role within the business unit it serves. [sent-5, score-0.801]
6 ) pour forth, it is the developer’s job to evolve their software system to accommodate these requirements and provide a software based solution to whatever problems lay ahead. [sent-9, score-1.298]
7 Given that many businesses can be identified as having the above characteristics, I can now begin to explain why I believe that Heterogeneous System Architectures hold a significant advantage over Homogeneous System Architectures, in many distributed system cases. [sent-10, score-0.927]
wordName wordTfidf (topN-words)
[('constitutes', 0.227), ('pour', 0.227), ('period', 0.207), ('specifics', 0.196), ('homogeneous', 0.18), ('business', 0.168), ('lay', 0.164), ('quantify', 0.164), ('requirements', 0.163), ('differs', 0.162), ('cases', 0.159), ('architectures', 0.154), ('accommodate', 0.153), ('short', 0.145), ('forth', 0.145), ('heterogeneous', 0.145), ('falls', 0.141), ('system', 0.139), ('philosophy', 0.137), ('identified', 0.137), ('ever', 0.136), ('evolve', 0.124), ('businesses', 0.122), ('requirement', 0.122), ('begin', 0.121), ('largely', 0.121), ('somewhere', 0.119), ('driving', 0.119), ('forces', 0.118), ('hold', 0.118), ('characteristics', 0.117), ('reality', 0.117), ('software', 0.111), ('assume', 0.11), ('explain', 0.11), ('unit', 0.108), ('exist', 0.107), ('effect', 0.107), ('whatever', 0.106), ('depending', 0.104), ('week', 0.098), ('role', 0.096), ('significant', 0.095), ('supporting', 0.094), ('generally', 0.093), ('effort', 0.092), ('follow', 0.09), ('developing', 0.089), ('additional', 0.087), ('believe', 0.085)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 500 high scalability-2009-01-22-Heterogeneous vs. Homogeneous System Architectures
Introduction: I follow a certain philosophy when developing system architectures. I assume that very few systems will ever exist in a consistent form for more than a short period of time. What constitutes a “short period of time” differs depending on the specifics of each system, but in an effort to quantify it, I generally find that it falls somewhere between a week and a month. The driving forces behind the need for an ever changing architecture are largely business requirement based. This is a side effect of the reality that software development, in most cases, is used as a supporting role within the business unit it serves. As business requirements (i.e. additional features, new products, etc.) pour forth, it is the developer’s job to evolve their software system to accommodate these requirements and provide a software based solution to whatever problems lay ahead. Given that many businesses can be identified as having the above characteristics, I can now begin to explain why I believe t
2 0.1065481 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
Introduction: It remains that, from the same principles, I now demonstrate the frame of the System of the World. -- Isaac Newton The practice of IT reminds me a lot of the practice of science before Isaac Newton. Aristotelianism was dead, but there was nothing to replace it. Then Newton came along, created a scientific revolution with his System of the World . And everything changed. That was New System of the World number one. New System of the World number two was written about by the incomparable Neal Stephenson in his incredible Baroque Cycle series. It explores the singular creation of a new way of organizing society grounded in new modes of thought in business, religion, politics, and science. Our modern world emerged Enlightened as it could from this roiling cauldron of forces. In IT we may have had a Leonardo da Vinci or even a Galileo, but we’ve never had our Newton. Maybe we don't need a towering genius to make everything clear? For years startups, like the frenetically inventive
3 0.092392609 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
Introduction: We are on the edge of two potent technological changes: Clouds and Memory Based Architectures. This evolution will rip open a chasm where new players can enter and prosper. Google is the master of disk. You can't beat them at a game they perfected. Disk based databases like SimpleDB and BigTable are complicated beasts, typical last gasp products of any aging technology before a change. The next era is the age of Memory and Cloud which will allow for new players to succeed. The tipping point will be soon. Let's take a short trip down web architecture lane: It's 1993: Yahoo runs on FreeBSD, Apache, Perl scripts and a SQL database It's 1995: Scale-up the database. It's 1998: LAMP It's 1999: Stateless + Load Balanced + Database + SAN It's 2001: In-memory data-grid. It's 2003: Add a caching layer. It's 2004: Add scale-out and partitioning. It's 2005: Add asynchronous job scheduling and maybe a distributed file system. It's 2007: Move it all into the cloud. It's 2008: C
4 0.085035831 822 high scalability-2010-05-04-Business continuity with real-time data integration
Introduction: Enterprises want to protect their data. As the appetite for data volumes grows, storage technology becomes a critical business asset on which business continuity relies. My recent survey in the medium-size enterprise segment shows the five dominant investment directions at the level of data management architecture: disaster recovery (DR), high availability (HA), backup, data processing performance and migration to more advanced databases. This suggests that corporations generally have sufficiently structured data collections but are concerned with business continuity and continuous availability of data. What infrastructures can provide these assurances? In this post I want to focus on yet another option, and that is the Real-Time Data Integration model. As an example I am going to discuss Oracle GoldenGate, which permits you to manage the data critical to your business in safety, ensuring business continuity without disruption even if the data is distributed among multiple, h
5 0.082123108 1654 high scalability-2014-06-05-Cloud Architecture Revolution
Introduction: The introduction of cloud technologies is not a simple evolution of existing ones, but a real revolution. Like all revolutions, it changes the points of views and redefines all the meanings. Nothing is as before. This post wants to analyze some key words and concepts, usually used in traditional architectures, redefining them according the standpoint of the cloud. Understanding the meaning of new words is crucial to grasp the essence of a pure cloud architecture. << There is no greater impediment to the advancement of knowledge than the ambiguity of words. >> THOMAS REID, Essays on the Intellectual Powers of Man Nowadays, it is required to challenge the limits of traditional architectures that go beyond the normal concepts of scalability and support millions of users (What's Up 500 Million) billions of transactions per day (Salesforce 1.3 billion), five 9s of availability (99.999 AOL). I wish all of you the success of the examples cited above, but do not think that it is co
6 0.081411734 1090 high scalability-2011-08-01-Peecho Architecture - scalability on a shoestring
7 0.081272684 1160 high scalability-2011-12-21-In Memory Data Grid Technologies
8 0.080349132 782 high scalability-2010-02-23-When to migrate your database?
9 0.079985835 259 high scalability-2008-02-25-Any Suggestions for the Architecture Template?
10 0.079985835 260 high scalability-2008-02-25-Architecture Template Advice Needed
11 0.078382038 235 high scalability-2008-02-02-The case against ORM Frameworks in High Scalability Architectures
12 0.076970384 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
13 0.076900981 346 high scalability-2008-06-28-ID generation schemes
15 0.075767122 1343 high scalability-2012-10-18-Save up to 30% by Selecting Better Performing Amazon Instances
16 0.069953665 918 high scalability-2010-10-12-The CIO’s Problem: Cloud “Mess” or Cloud “Mash”
17 0.069795489 1568 high scalability-2013-12-23-What Happens While Your Brain Sleeps is Surprisingly Like How Computers Stay Sane
18 0.06826929 1446 high scalability-2013-04-25-Paper: Making reliable distributed systems in the presence of software errors
19 0.067843787 1258 high scalability-2012-06-05-Thesis: Concurrent Programming for Scalable Web Architectures
topicId topicWeight
[(0, 0.117), (1, 0.033), (2, 0.022), (3, 0.036), (4, 0.008), (5, -0.006), (6, 0.004), (7, -0.02), (8, -0.052), (9, 0.016), (10, -0.033), (11, 0.056), (12, -0.014), (13, 0.013), (14, 0.027), (15, -0.003), (16, 0.033), (17, -0.03), (18, 0.026), (19, 0.031), (20, 0.0), (21, -0.006), (22, -0.009), (23, -0.001), (24, -0.041), (25, -0.007), (26, -0.027), (27, -0.021), (28, 0.007), (29, 0.006), (30, -0.026), (31, 0.056), (32, 0.025), (33, -0.041), (34, -0.053), (35, 0.006), (36, -0.015), (37, 0.015), (38, 0.036), (39, -0.029), (40, 0.005), (41, 0.032), (42, 0.064), (43, 0.04), (44, 0.014), (45, 0.002), (46, -0.034), (47, -0.008), (48, 0.016), (49, -0.015)]
simIndex simValue blogId blogTitle
same-blog 1 0.94465226 500 high scalability-2009-01-22-Heterogeneous vs. Homogeneous System Architectures
Introduction: I follow a certain philosophy when developing system architectures. I assume that very few systems will ever exist in a consistent form for more than a short period of time. What constitutes a “short period of time” differs depending on the specifics of each system, but in an effort to quantify it, I generally find that it falls somewhere between a week and a month. The driving forces behind the need for an ever changing architecture are largely business requirement based. This is a side effect of the reality that software development, in most cases, is used as a supporting role within the business unit it serves. As business requirements (i.e. additional features, new products, etc.) pour forth, it is the developer’s job to evolve their software system to accommodate these requirements and provide a software based solution to whatever problems lay ahead. Given that many businesses can be identified as having the above characteristics, I can now begin to explain why I believe t
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.71450913 1628 high scalability-2014-04-08-Microservices - Not a free lunch!
Introduction: This is a guest post by Benjamin Wootton , CTO of Contino , a London based consultancy specialising in applying DevOps and Continuous Delivery to software delivery projects. Microservices are a style of software architecture that involves delivering systems as a set of very small, granular, independent collaborating services. Though they aren't a particularly new idea, Microservices seem to have exploded in popularity this year, with articles, conference tracks, and Twitter streams waxing lyrical about the benefits of building software systems in this style. This popularity is partly off the back of trends such as Cloud, DevOps and Continuous Delivery coming together as enablers for this kind of approach, and partly off the back of great work at companies such as Netflix who have very visibly applied the pattern to great effect. Let me say up front that I am a fan of the approach. Microservices architectures have lots of very real and significant benefits: The service
4 0.69714987 731 high scalability-2009-10-28-Need for change in your IT infrastructure
Introduction: Companies earnings outstrip forecasts , consumer confidence is retuning and city bonuses are back . What does this mean for business? Growth! After the recent years of cost cutting in IT budgets, there is the sudden fear induced from increased demand. Pre-existing trouble points in IT infrastructures that have lain dormant will suddenly be exposed. Monthly reporting and real time analytics will suffer as data grows. IT departments across the land will be crying out “The engine canna take no more captain”. What can be done? What we need is a scalable system that grows with the business. A system that can handle sudden increases in data growth without falling over. There are two core principles to a scalable system (1) Users experience constant QoS as demand grows (2) System Architects can grow system capacity proportionally with the available resources. In other words, if demand increases twofold, it is “enough” to purchase twice the hardware. This is linear growth. Is it e
5 0.69243592 1012 high scalability-2011-03-28-Aztec Empire Strategy: Use Dual Pipes in Your Aqueduct for High Availability
Introduction: With the Chapultepec aqueduct , also named the great aqueduct , the Aztecs built a novel uninterruptible water supply for providing fresh water to Tenochtitlan , their fast growing jewel of a capital city. A section of the aqueduct is still around today: It's fun to think about how even 600 years ago how it was built with high availability in mind. We find engineers being engineers , no matter the age: It consisted of a twin pipe distribution system made in part of compacted soil and in part of wood for the crossings of the aqueduct over the bridges built to allow the passage of the canoes. It was finished around 1466 AD, and the main purpose was to supply fresh water to Mexico-Tenochtitlan, to mitigate its thirst. The main source for the aqueduct was the spring of Chapultepec and the purpose of the twin pipes was to ease the maintenance of the system, because the water was conveyed through one pipe, and when it got dirty, the water was diverted to the other pipe
6 0.68393499 1379 high scalability-2012-12-31-Designing for Resiliency will be so 2013
7 0.67354298 894 high scalability-2010-09-03-Six guiding principles to Consolidate your IT
8 0.66843474 1366 high scalability-2012-12-03-Resiliency is the New Normal - A Deep Look at What It Means and How to Build It
9 0.66409427 288 high scalability-2008-03-25-Paper: On Designing and Deploying Internet-Scale Services
10 0.65889961 813 high scalability-2010-04-19-The cost of High Availability (HA) with Oracle
11 0.64865267 1568 high scalability-2013-12-23-What Happens While Your Brain Sleeps is Surprisingly Like How Computers Stay Sane
12 0.64508331 697 high scalability-2009-09-09-GridwiseTech revolutionizes data management
13 0.64359349 96 high scalability-2007-09-18-Amazon Architecture
14 0.64221781 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
15 0.64064008 977 high scalability-2011-01-21-PaaS shouldn’t be built in Silos
16 0.63977212 400 high scalability-2008-10-01-The Pattern Bible for Distributed Computing
18 0.62874597 357 high scalability-2008-07-26-Google's Paxos Made Live – An Engineering Perspective
19 0.62542641 1234 high scalability-2012-04-26-Akaros - an open source operating system for manycore architectures
20 0.62311435 1636 high scalability-2014-04-23-Here's a 1300 Year Old Solution to Resilience - Rebuild, Rebuild, Rebuild
topicId topicWeight
[(1, 0.17), (2, 0.13), (30, 0.463), (79, 0.129)]
simIndex simValue blogId blogTitle
1 0.98168117 131 high scalability-2007-10-25-Should JSPs be avoided for high scalability?
Introduction: I just heard about some web sites where Velocity templates are used to render HTML instead of using JSPs and all the processing in performed in servlets. Can JSPs cause issue with scalability? Thanks, Unmesh
2 0.95443368 1016 high scalability-2011-04-04-Scaling Social Ecommerce Architecture Case study
Introduction: A recent study showed that over 92 percent of executives from leading retailers are focusing their marketing efforts on Facebook and subsequent applications. Furthermore, over 71 percent of users have confirmed they are more likely to make a purchase after “liking” a brand they find online. ( source ) Sears Architect Tomer Gabel provides an insightful overview on how they built a Social Ecommerce solution for Sears.com that can handle complex relationship quires in real time. Tomer goes through: the architectural considerations behind their solution why they chose memory over disk how they partitioned the data to gain scalability why they chose to execute code with the data using GigaSpaces Map/Reduce execution framework how they integrated with Facebook why they chose GigaSpaces over Coherence and Terracotta for in-memory caching and scale In this post I tried to summarize the main takeaway from the interview. You can also watch the full interview (highly reco
3 0.94717753 991 high scalability-2011-02-16-Paper: An Experimental Investigation of the Akamai Adaptive Video Streaming
Introduction: Video is hot on the Internet and people are really interested in knowing how to make it work. Dan Rayburn has a post pointing to a fascinating paper: An Experimental Investigation of the Akamai Adaptive Video Streaming , which talks in some detail about the protocols big players like YouTube, Skype and Akamai use to serve video over on an inherently video unfriendly medium like the Internet. For Akamai they found: Each video is encoded in five versions at different bit rates and stored in separate files. The client sends commands to the server with an average inter departure time of about 2 s, i.e. the control algorithm is executed on average each 2 seconds. Akamai uses only the video level to adapt the video source to the available bandwidth, whereas the frame rate of the video is kept constant. When a sudden drop in the available bandwidth occurs, short interruptions of the video playback can occur due to the a large actuation delay. For a sudden increase of the avai
4 0.94404805 14 high scalability-2007-07-15-Web Analytics: An Hour a Day
Introduction: Web Analytics: An Hour A Day is the first book by an in-the-trenches practitioner of web analytics. It provides a unique insider’s perspective of the challenges and opportunities that web analytics presents to each person who touches the Web in your organization. Rather than spamming you with metrics and definitions, Web Analytics: An Hour A Day will enhance your mindset and teach you how to fish for yourself. Avinash Kaushik is a expert in web analytics and author of the top-rated blog Occam’s Razor (http://www.kaushik.net/avinash). In this book, he goes beyond web analytics concepts and definitions to provide a step-by-step guide to implementing a successful web analytics strategy. His revolutionary approach to web analytics challenges prevalent thinking about the field and guides readers to a solution that will provide truly informed and actionable insights.
5 0.94247735 1459 high scalability-2013-05-16-Paper: Warp: Multi-Key Transactions for Key-Value Stores
Introduction: Looks like an interesting take on "a completely asynchronous, low-latency transaction management protocol, in line with the fully distributed NoSQL architecture." Warp: Multi-Key Transactions for Key-Value Stores  overview: Implementing ACID transactions has been a longstanding challenge for NoSQL systems. Because these systems are based on a sharded architecture, transactions necessarily require coordination across multiple servers. Past work in this space has relied either on heavyweight protocols such as Paxos or clock synchronization for this coordination. This paper presents a novel protocol for coordinating distributed transactions with ACID semantics on top of a sharded data store. Called linear transactions, this protocol achieves scalability by distributing the coordination task to only those servers that hold relevant data for each transaction. It achieves high performance by serializing only those transactions whose concurrent execution could potentially yield a vio
6 0.91148233 16 high scalability-2007-07-16-Book: High Performance MySQL
same-blog 7 0.90043527 500 high scalability-2009-01-22-Heterogeneous vs. Homogeneous System Architectures
8 0.89042079 182 high scalability-2007-12-12-Oracle Can Do Read-Write Splitting Too
9 0.88020152 308 high scalability-2008-04-22-Simple NFS failover solution with symbolic link?
10 0.81861806 336 high scalability-2008-05-31-Biggest Under Reported Story: Google's BigTable Costs 10 Times Less than Amazon's SimpleDB
11 0.81656194 261 high scalability-2008-02-25-Make Your Site Run 10 Times Faster
12 0.80590856 831 high scalability-2010-05-26-End-To-End Performance Study of Cloud Services
13 0.80314672 783 high scalability-2010-02-24-Hot Scalability Links for February 24, 2010
14 0.79872167 334 high scalability-2008-05-29-Amazon Improves Diagonal Scaling Support with High-CPU Instances
15 0.78263324 263 high scalability-2008-02-27-Product: System Imager - Automate Deployment and Installs
16 0.76433021 43 high scalability-2007-07-30-Product: ImageShack
17 0.75248241 1284 high scalability-2012-07-16-Cinchcast Architecture - Producing 1,500 Hours of Audio Every Day
18 0.71624804 291 high scalability-2008-03-29-20 New Rules for Faster Web Pages
20 0.68966067 788 high scalability-2010-03-04-How MySpace Tested Their Live Site with 1 Million Concurrent Users