high_scalability high_scalability-2011 high_scalability-2011-1087 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: It started out innocently enough with a simple question, “What exactly *is* the model for PaaS services scalability? If based on HTTP/REST API integration, fairly easy. If native middleware… input?” You’ll forgive the odd phrasing – Twitter’s limitations sometimes make conversations of this nature … interesting. The discussion culminated in what appeared to be the sentiment that middleware was mostly obsolete with respect to PaaS. THE OLD WAY Very briefly for those of you who are more infrastructure / network minded than application architecture fluent, let’s review the traditional middleware-based application architecture. Generally speaking, middleware – a.k.a. JMS, MQ Series and most recently, ESB – is leveraged as means to enable a publish-subscribe model of sharing data. Basically, it’s an integration pattern, but no one really likes to admit that because of the connotations associated with the evil word “integration” in the enterprise. But that’s what it’s
sentIndex sentText sentNum sentScore
1 The discussion culminated in what appeared to be the sentiment that middleware was mostly obsolete with respect to PaaS. [sent-5, score-0.646]
2 The difference between Web-based social networking and traditional enterprise applications is two-fold: First – web-based applications were not, until the advent of Web 2. [sent-18, score-0.61]
3 0 and specifically AJAX, well-suited to “polling for” or “subscribing to” messages (updates, statuses, etc…) thus the use of traditional pub-sub architectures for web applications never much gained traction. [sent-19, score-0.491]
4 Web-based applications generally require higher capacity and transaction rates than traditional applications taking advantage of middleware, making middleware’s inability to scale problematic. [sent-21, score-0.517]
5 It is unsuited to use in social networking and other high-volume data sharing systems, where rapidity of response is vital to success. [sent-22, score-0.421]
6 Generally that means a database-based solution even if we use the power of virtualization and cloud computing to address the innate challenges associated with scaling messaging middleware. [sent-28, score-0.411]
7 THE NEW WAY Now this is not meant to say the concept of queuing, of pub-sub, is absent in web applications and social networking. [sent-30, score-0.551]
8 What’s absent is the traditional middleware as a means to manage the messages across those people (and applications). [sent-33, score-1.012]
9 See, scaling middleware ran into the same issues as stateful applications – they required persistence or a shared-nothing architecture to ensure proper behavior. [sent-34, score-1.018]
10 The problem as you added middleware servers became the same as other persistence-based issues seen in web applications, digital shopping carts and even today’s VDI implementations. [sent-35, score-0.818]
11 What you end up with is essentially 4 tiers – web, application, middleware and database. [sent-39, score-0.754]
12 0 applications don’t generally use a middleware tier to facilitate messaging across users or applications. [sent-45, score-1.071]
13 One of those components is messaging and, so it would seem, traditional middleware (as a service, of course). [sent-52, score-0.935]
14 But the scalability issues with middleware really haven’t been solved and the persistence issues remain. [sent-53, score-0.954]
15 Adding pressure is the web development paradigm in which middleware has traditionally been excluded. [sent-54, score-0.734]
16 They’re a three-tier generation of developers who implement the concept of messaging by leveraging database connectivity directly and most recently polling via AJAX and APIs. [sent-56, score-0.393]
17 The ease with which web and application tiers are scaled in a cloud computing environment, moreover, meets the higher concurrent user and transaction volume requirements (not to mention performance) associated with highly integrated web applications today. [sent-58, score-0.784]
18 Scaling middleware services at the virtualization layer, as noted above, is possible, but reintroduces the necessity of a persistent store. [sent-59, score-0.81]
19 0 having been forced to solve the shared messaging concept without middleware – and having done so successfully – that middleware as a service is obsolete. [sent-63, score-1.615]
20 0 forced a solution that did not require middleware and that nearly all web-based applications eschew middleware as the mechanism for implementing pub-sub and other similar architectural patterns. [sent-66, score-1.506]
wordName wordTfidf (topN-words)
[('middleware', 0.646), ('traditional', 0.153), ('applications', 0.148), ('persistence', 0.14), ('messaging', 0.136), ('concept', 0.121), ('absent', 0.111), ('integration', 0.11), ('tiers', 0.108), ('associated', 0.105), ('messages', 0.102), ('persistent', 0.101), ('web', 0.088), ('subscribed', 0.088), ('issues', 0.084), ('social', 0.083), ('vital', 0.083), ('paas', 0.079), ('networking', 0.078), ('basically', 0.077), ('volume', 0.073), ('tier', 0.073), ('layer', 0.07), ('application', 0.069), ('directly', 0.068), ('polling', 0.068), ('generally', 0.068), ('conversation', 0.067), ('sharing', 0.067), ('forced', 0.066), ('message', 0.063), ('virtualization', 0.063), ('viable', 0.062), ('ajax', 0.061), ('queuing', 0.057), ('forgive', 0.055), ('innate', 0.055), ('jms', 0.055), ('rapidity', 0.055), ('statuses', 0.055), ('subscribing', 0.055), ('theload', 0.055), ('unsuited', 0.055), ('consistency', 0.055), ('scaled', 0.053), ('computing', 0.052), ('nebulous', 0.052), ('vdi', 0.052), ('byjames', 0.052), ('computingand', 0.052)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 1087 high scalability-2011-07-26-Web 2.0 Killed the Middleware Star
Introduction: It started out innocently enough with a simple question, “What exactly *is* the model for PaaS services scalability? If based on HTTP/REST API integration, fairly easy. If native middleware… input?” You’ll forgive the odd phrasing – Twitter’s limitations sometimes make conversations of this nature … interesting. The discussion culminated in what appeared to be the sentiment that middleware was mostly obsolete with respect to PaaS. THE OLD WAY Very briefly for those of you who are more infrastructure / network minded than application architecture fluent, let’s review the traditional middleware-based application architecture. Generally speaking, middleware – a.k.a. JMS, MQ Series and most recently, ESB – is leveraged as means to enable a publish-subscribe model of sharing data. Basically, it’s an integration pattern, but no one really likes to admit that because of the connotations associated with the evil word “integration” in the enterprise. But that’s what it’s
2 0.3141284 727 high scalability-2009-10-25-Is Your Data Really Secured?
Introduction: Caching/data-grids are going through a similar evolution to databases. As with databases, we started by using caching as an embedded service to the application. Now we are in the phase where we need to be able to share the data between multiple applications, or in cases where we don’t want to share the data, we need to be able to share the resources for managing the data, while keeping a high degree of isolation. The demand for these sort of requirements becomes much more common with SOA or SaaS-based applications. As we approach the next generation of middleware and data-centers, it becomes clear that we cannot move to the next wave of virtualization and cloud computing without a strong security and isolation solution that is built-in to all layers of our application and middleware.
3 0.18919118 453 high scalability-2008-12-01-Breakthrough Web-Tier Solutions with Record-Breaking Performance
Introduction: With the explosive growth of the Internet, increasing complexity of user requirements, and wide choice of hardware, operating systems, and middleware, IT executives are facing new challenges in their application infrastructures. Rapid expansion of the application tier has resulted in significant cost and complexity, and many organizations are simply running out of datacenter space, power, and cooling.
4 0.16329239 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture
Introduction: Too often software design patterns are overlooked by network and application delivery network architects but these patterns are often equally applicable to addressing a broad range of architectural challenges in the application delivery tier of the data center. By Lori Mac Vittie, F5 Networks The “ High Scalability ” blog is fast becoming one of my favorite reads. Last week did not disappoint with a post highlighting a set of scalability design patterns that was, apparently, inspired by yet another High Scalability post on “ 6 Ways to Kill Your Servers: Learning to Scale the Hard Way. ” Credit:Michael Chow/azcentral.com This particular post caught my attention primarily because although I’ve touched on many of these patterns in the past, I’ve never thought to call them what they are: scalability patterns. That’s probably a side-effect of forgetting that building an architecture of any kind is at its core computer science and thus
5 0.15567832 96 high scalability-2007-09-18-Amazon Architecture
Introduction: This is a wonderfully informative Amazon update based on Joachim Rohde's discovery of an interview with Amazon's CTO. You'll learn about how Amazon organizes their teams around services, the CAP theorem of building scalable systems, how they deploy software, and a lot more. Many new additions from the ACM Queue article have also been included. Amazon grew from a tiny online bookstore to one of the largest stores on earth. They did it while pioneering new and interesting ways to rate, review, and recommend products. Greg Linden shared is version of Amazon's birth pangs in a series of blog articles Site: http://amazon.com Information Sources Early Amazon by Greg Linden How Linux saved Amazon millions Interview Werner Vogels - Amazon's CTO Asynchronous Architectures - a nice summary of Werner Vogels' talk by Chris Loosley Learning from the Amazon technology platform - A Conversation with Werner Vogels Werner Vogels' Weblog - building scalable and robus
7 0.13559408 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
8 0.13153797 955 high scalability-2010-12-07-Sponsored Post: Joyent, Membase, Appirio, CloudSigma, ManageEngine, Site24x7
9 0.12779681 977 high scalability-2011-01-21-PaaS shouldn’t be built in Silos
10 0.12470006 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
12 0.12429108 947 high scalability-2010-11-23-Sponsored Post: Imo, Undertone, Joyent, Appirio, Tuenti, CloudSigma, ManageEngine, Site24x7
14 0.11669894 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
15 0.11607777 639 high scalability-2009-06-27-Scaling Twitter: Making Twitter 10000 Percent Faster
17 0.11473083 924 high scalability-2010-10-21-What is Network-based Application Virtualization and Why Do You Need It?
topicId topicWeight
[(0, 0.213), (1, 0.043), (2, 0.077), (3, 0.039), (4, 0.013), (5, -0.022), (6, 0.0), (7, -0.078), (8, -0.067), (9, 0.045), (10, 0.054), (11, 0.123), (12, -0.06), (13, 0.02), (14, -0.017), (15, -0.019), (16, 0.036), (17, -0.03), (18, 0.099), (19, -0.012), (20, -0.032), (21, 0.006), (22, 0.006), (23, 0.031), (24, 0.06), (25, -0.015), (26, -0.012), (27, -0.046), (28, 0.009), (29, 0.011), (30, 0.033), (31, -0.017), (32, 0.046), (33, 0.014), (34, -0.019), (35, 0.007), (36, -0.054), (37, 0.008), (38, 0.019), (39, 0.011), (40, 0.027), (41, -0.016), (42, -0.039), (43, 0.037), (44, -0.017), (45, -0.055), (46, -0.006), (47, 0.034), (48, -0.054), (49, -0.026)]
simIndex simValue blogId blogTitle
same-blog 1 0.97065872 1087 high scalability-2011-07-26-Web 2.0 Killed the Middleware Star
Introduction: It started out innocently enough with a simple question, “What exactly *is* the model for PaaS services scalability? If based on HTTP/REST API integration, fairly easy. If native middleware… input?” You’ll forgive the odd phrasing – Twitter’s limitations sometimes make conversations of this nature … interesting. The discussion culminated in what appeared to be the sentiment that middleware was mostly obsolete with respect to PaaS. THE OLD WAY Very briefly for those of you who are more infrastructure / network minded than application architecture fluent, let’s review the traditional middleware-based application architecture. Generally speaking, middleware – a.k.a. JMS, MQ Series and most recently, ESB – is leveraged as means to enable a publish-subscribe model of sharing data. Basically, it’s an integration pattern, but no one really likes to admit that because of the connotations associated with the evil word “integration” in the enterprise. But that’s what it’s
2 0.80488288 1544 high scalability-2013-11-07-Paper: Tempest: Scalable Time-Critical Web Services Platform
Introduction: An interesting and different implementation approach: Tempest: Scalable Time-Critical Web Services Platform : Tempest is a new framework for developing time-critical web services. Tempest enables developers to build scalable, fault-tolerant services that can then be automatically replicated and deployed across clusters of computing nodes. The platform automatically adapts to load fluctuations, reacts when components fail, and ensures consistency between replicas by repairing when inconsistencies do occur. Tempest relies on a family of epidemic protocols and on Ricochet, a reliable time critical multicast protocol with probabilistic guarantees. Tempest is built around a novel storage abstraction called the TempestCollection in which application developers store the state of a service. Our platform handles the replication of this state across clones of the service, persistence, and failure handling. To minimize the need for specialized knowledge on the part of the application deve
3 0.80269706 727 high scalability-2009-10-25-Is Your Data Really Secured?
Introduction: Caching/data-grids are going through a similar evolution to databases. As with databases, we started by using caching as an embedded service to the application. Now we are in the phase where we need to be able to share the data between multiple applications, or in cases where we don’t want to share the data, we need to be able to share the resources for managing the data, while keeping a high degree of isolation. The demand for these sort of requirements becomes much more common with SOA or SaaS-based applications. As we approach the next generation of middleware and data-centers, it becomes clear that we cannot move to the next wave of virtualization and cloud computing without a strong security and isolation solution that is built-in to all layers of our application and middleware.
4 0.78522307 924 high scalability-2010-10-21-What is Network-based Application Virtualization and Why Do You Need It?
Introduction: With all the attention being paid these days to VDI (virtual desktop infrastructure) and application virtualization and server virtualization andvirtualization it’s easy to forget about network-based application virtualization. But it’s the one virtualization technique you shouldn’t forget because it is a foundational technology upon which myriad other solutions will be enabled. WHAT IS NETWORK-BASED APPLICATION VIRTUALIZATION? This term may not be familiar to you but that’s because since its inception oh, more than a decade ago, it’s always just been called “server virtualization”. After the turn of the century (I love saying that, by the way) it was always referred to as service virtualization in SOA and XML circles. With the rise of the likes of VMware and Citrix and Microsoft server virtualization solutions, it’s become impossible to just use the term “server virtualization” and “service virtualization” is just as ambiguous so it seems appropriate to giv
Introduction: How do you layer a programmable Internet of smart things on top of the web? That's the question addressed by Dominique Guinard  in his ambitious dissertation: A Web of Things Application Architecture - Integrating the Real-World  ( slides ). With the continued siloing of content, perhaps we can keep our things open and talking to each other? In the architecture things are modeled using REST, they will be findable via search, they will be social via a social access controller, and they will be mashupable. Here's great graphical overview of the entire system:  Abstract: A central concern in the area of pervasive computing has been the integration of digital artifactsts with the physical world and vice-versa. Recent developments in the fi eld of embedded devices have led to smart things increasingly populating our daily life. We de fine smart things as digitally enhanced physical objectsts and devices that have communication capabilities. Application domains are for i
6 0.74564755 702 high scalability-2009-09-11-The interactive cloud
7 0.74137175 1056 high scalability-2011-06-09-Retrospect on recent AWS outage and Resilient Cloud-Based Architecture
8 0.73958653 180 high scalability-2007-12-10-Scalability Developer Competition Launched by GigaSpaces - $25k in prizes
9 0.72910243 524 high scalability-2009-03-04-Its time for auto scaling – avoid peak load provisioning for web applications
10 0.72469848 453 high scalability-2008-12-01-Breakthrough Web-Tier Solutions with Record-Breaking Performance
11 0.72080112 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture
12 0.71661794 212 high scalability-2008-01-14-OpenSpaces.org community site launched - framework for building scale-out applications
13 0.71306729 933 high scalability-2010-11-01-Hot Trend: Move Behavior to Data for a New Interactive Application Architecture
14 0.71196187 1654 high scalability-2014-06-05-Cloud Architecture Revolution
15 0.71102744 438 high scalability-2008-11-05-Managing application on the cloud using a JMX Fabric
16 0.70243847 762 high scalability-2010-01-18-The Missing Piece in the Virtualization Stack (Part 1)
17 0.70158988 384 high scalability-2008-09-16-EE-Appserver Clustering OR Terracota OR Coherence OR something else?
18 0.69815451 1212 high scalability-2012-03-21-The Conspecific Hybrid Cloud
19 0.6960814 832 high scalability-2010-05-31-Scalable federated security with Kerberos
20 0.69347996 444 high scalability-2008-11-14-Private-Public Cloud
topicId topicWeight
[(1, 0.154), (2, 0.263), (4, 0.01), (10, 0.059), (27, 0.013), (28, 0.014), (30, 0.012), (40, 0.023), (47, 0.021), (57, 0.066), (61, 0.117), (77, 0.012), (79, 0.078), (85, 0.047), (94, 0.04)]
simIndex simValue blogId blogTitle
1 0.98281682 351 high scalability-2008-07-16-The Mother of All Database Normalization Debates on Coding Horror
Introduction: Jeff Atwood started a barn burner of a conversation in Maybe Normalizing Isn't Normal on how to create a fast scalable tagging system. Jeff eventually asks that terrible question: which is better -- a normalized database, or a denormalized database? And all hell breaks loose. I know, it's hard to imagine database debates becoming contentious, but it does happen :-) It's lucky developers don't have temporal power or rivers of blood would flow. Here are a few of the pithier points (summarized): Normalization is not magical fairy dust you sprinkle over your database to cure all ills; it often creates as many problems as it solves. (Jeff) Normalize until it hurts, denormalize until it works. (Jeff) Use materialized views which are tables created and maintained by your RDBMS. So a materialized view will act exactly like a de-normalized table would - except you keep you original normalized structure and any change to original data will propagate to the view automat
2 0.98219442 6 high scalability-2007-07-11-Friendster Architecture
Introduction: Friendster is one of the largest social network sites on the web. it emphasizes genuine friendships and the discovery of new people through friends. Site: http://www.friendster.com/ Information Sources Friendster - Scaling for 1 Billion Queries per day Platform MySQL Perl PHP Linux Apache What's Inside? Dual x86-64 AMD Opterons with 8 GB of RAM Faster disk (SAN) Optimized indexes Traditional 3-tier architecture with hardware load balancer in front of the databases Clusters based on types: ad, app, photo, monitoring, DNS, gallery search DB, profile DB, user infor DB, IM status cache, message DB, testimonial DB, friend DB, graph servers, gallery search, object cache. Lessons Learned No persistent database connections. Removed all sorts. Optimized indexes Don’t go after the biggest problems first Optimize without downtime Split load Moved sorting query types into the application and added LIMITS. Reduced ranges R
3 0.97709554 218 high scalability-2008-01-17-Moving old to new. Do not be afraid of the re-write -- but take some help
Introduction: Recently I had to help users on one of my opensource project ISPMan. http://ispman.net This project started in 2001 as I was too unwilling to take care of the DNS and VitualHosting stuff as it was a side-thing to the company I worked for (so i wrote a software that took care of all these little details) Summary: A large project that needs a rewrite can be done in a matter of day. I will not give you a full case study about a project that went through a re-write but a case study about how easy it is to re-write something. Details: My boss was cool enough to let me open-source the project and obviously, I got a lot of cool-cred out of it. Later on I also did some support and implementation and earned quiet some money with it. Eventually I had to let the project go out of my hand to the community as I only did it to facilitate a job that wasnt williing to do. (Setup DNS zones of multiple servers, find out which host should host the website and put VirtualHost
4 0.97528172 232 high scalability-2008-01-29-When things aren't scalable
Introduction: OK, I know this site is for scalable web site design. But as there aren't any sites I can find for graceful failure under "slashdotted" like pressure I'll ask here. Does anyone have a sensible way, once you have a "web application" that either won't scale, or can't scale, that you can give some users a good consistent experience and bounce other users to a busy site page. I have seen sites do this to varying degrees, some of which work better than others, but no explanations beyond simply bouncing requests to a "we're busy page server" when you have more than a given number of connections. This is obviously useless as a web page likely requires multiple connection (ignoring keep-alive, pipelining etc) multiple connection to completely render properly. The normal problem is users getting a page and not the "furniture" for that page like images or css. Other problems are having to wait ages to get the busy page or the site being slow even if you do "get in". And some site let
same-blog 5 0.97482961 1087 high scalability-2011-07-26-Web 2.0 Killed the Middleware Star
Introduction: It started out innocently enough with a simple question, “What exactly *is* the model for PaaS services scalability? If based on HTTP/REST API integration, fairly easy. If native middleware… input?” You’ll forgive the odd phrasing – Twitter’s limitations sometimes make conversations of this nature … interesting. The discussion culminated in what appeared to be the sentiment that middleware was mostly obsolete with respect to PaaS. THE OLD WAY Very briefly for those of you who are more infrastructure / network minded than application architecture fluent, let’s review the traditional middleware-based application architecture. Generally speaking, middleware – a.k.a. JMS, MQ Series and most recently, ESB – is leveraged as means to enable a publish-subscribe model of sharing data. Basically, it’s an integration pattern, but no one really likes to admit that because of the connotations associated with the evil word “integration” in the enterprise. But that’s what it’s
6 0.97418213 1507 high scalability-2013-08-26-Reddit: Lessons Learned from Mistakes Made Scaling to 1 Billion Pageviews a Month
7 0.97237831 855 high scalability-2010-07-11-So, Why is Twitter Really Not Using Cassandra to Store Tweets?
8 0.97152388 998 high scalability-2011-03-03-Stack Overflow Architecture Update - Now at 95 Million Page Views a Month
9 0.97145605 1151 high scalability-2011-12-05-Stuff The Internet Says On Scalability For December 5, 2011
10 0.97122622 72 high scalability-2007-08-22-Wikimedia architecture
11 0.97121578 821 high scalability-2010-05-03-MocoSpace Architecture - 3 Billion Mobile Page Views a Month
12 0.97071356 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
13 0.96987265 1269 high scalability-2012-06-20-iDoneThis - Scaling an Email-based App from Scratch
14 0.96967566 968 high scalability-2011-01-04-Map-Reduce With Ruby Using Hadoop
15 0.96828055 884 high scalability-2010-08-23-6 Ways to Kill Your Servers - Learning How to Scale the Hard Way
17 0.96730757 1123 high scalability-2011-09-23-The Real News is Not that Facebook Serves Up 1 Trillion Pages a Month…
18 0.96723604 1339 high scalability-2012-10-12-Stuff The Internet Says On Scalability For October 12, 2012
19 0.96675825 1573 high scalability-2014-01-06-How HipChat Stores and Indexes Billions of Messages Using ElasticSearch and Redis
20 0.96644628 1642 high scalability-2014-05-02-Stuff The Internet Says On Scalability For May 2nd, 2014