high_scalability high_scalability-2008 high_scalability-2008-475 knowledge-graph by maker-knowledge-mining

475 high scalability-2008-12-22-SLAs in the SaaS space


meta infos for this blog

Source: html

Introduction: This may be a bit higher level then the general discussion here, but I think this is an important issue in how it relates to reliability and uptime. What kind of SLAs should we be expecting from SaaS services and platforms (e.g. AWS, Google App Engine, Google Premium Apps, salesforce.com, etc.)? Up to today, most SaaS services either have no SLAs or offer very weak penalties. What will it take to get these services up to the point where they can offer the SLAs that users (and more importantly, businesses) require? I presume most of the members here want to see more movement into the cloud and to SaaS services, and I'm thinking that until we see more substantial SLA guarantees, most businesses will continue to shy away as long as they can. Would love to hear what others think. Or am I totally off base?


Summary: the most important sentenses genereted by tfidf model

sentIndex sentText sentNum sentScore

1 This may be a bit higher level then the general discussion here, but I think this is an important issue in how it relates to reliability and uptime. [sent-1, score-0.888]

2 What kind of SLAs should we be expecting from SaaS services and platforms (e. [sent-2, score-0.542]

3 Up to today, most SaaS services either have no SLAs or offer very weak penalties. [sent-7, score-0.606]

4 What will it take to get these services up to the point where they can offer the SLAs that users (and more importantly, businesses) require? [sent-8, score-0.453]

5 I presume most of the members here want to see more movement into the cloud and to SaaS services, and I'm thinking that until we see more substantial SLA guarantees, most businesses will continue to shy away as long as they can. [sent-9, score-1.444]


similar blogs computed by tfidf model

tfidf for this blog:

wordName wordTfidf (topN-words)

[('slas', 0.553), ('saas', 0.279), ('businesses', 0.265), ('shy', 0.201), ('services', 0.195), ('expecting', 0.176), ('relates', 0.176), ('offer', 0.166), ('sla', 0.161), ('weak', 0.157), ('substantial', 0.147), ('movement', 0.139), ('importantly', 0.135), ('members', 0.135), ('premium', 0.132), ('guarantees', 0.129), ('totally', 0.12), ('hear', 0.117), ('continue', 0.11), ('google', 0.104), ('issue', 0.102), ('base', 0.102), ('platforms', 0.098), ('reliability', 0.091), ('either', 0.088), ('love', 0.087), ('others', 0.086), ('discussion', 0.084), ('thinking', 0.084), ('bit', 0.082), ('general', 0.081), ('see', 0.079), ('require', 0.078), ('aws', 0.076), ('engine', 0.076), ('higher', 0.074), ('kind', 0.073), ('apps', 0.072), ('today', 0.072), ('away', 0.07), ('app', 0.063), ('important', 0.059), ('level', 0.055), ('long', 0.054), ('point', 0.05), ('think', 0.043), ('users', 0.042), ('may', 0.041), ('want', 0.041), ('cloud', 0.04)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.99999994 475 high scalability-2008-12-22-SLAs in the SaaS space

Introduction: This may be a bit higher level then the general discussion here, but I think this is an important issue in how it relates to reliability and uptime. What kind of SLAs should we be expecting from SaaS services and platforms (e.g. AWS, Google App Engine, Google Premium Apps, salesforce.com, etc.)? Up to today, most SaaS services either have no SLAs or offer very weak penalties. What will it take to get these services up to the point where they can offer the SLAs that users (and more importantly, businesses) require? I presume most of the members here want to see more movement into the cloud and to SaaS services, and I'm thinking that until we see more substantial SLA guarantees, most businesses will continue to shy away as long as they can. Would love to hear what others think. Or am I totally off base?

2 0.1115797 38 high scalability-2007-07-30-Build an Infinitely Scalable Infrastructure for $100 Using Amazon Services

Introduction: Can you really create an infinitely scalable infrastructure for less than $100 using Amazon's storage, grid, and queuing services platform? It appears so, at least for the right application. Amazon beams a spot light on the future battle of the roll-your-own versus the connect-the-dots approach to building next generation websites using core external services. Their argument is strong. Using Amazon's platform you can quickly build an infrastructure that would otherwise take an eternity to make, a pile of money to create, and an unbounded mass of people to implement and maintain. Yet Amazon doesn't provide SLAs, so you can you really trust them with your crown jewels? Facebook recently leap frogged Amazon's vision with an even more comprehensive set of services. The battle for the future is on. Site: http://aws.amazon.com/ Information Sources Slides: Building Highly Scalable Web Applications Podcast: Technometria: Amazon Web Services Amazon Services Home . Platform

3 0.098190747 1367 high scalability-2012-12-05-5 Ways to Make Cloud Failure Not an Option

Introduction: With cloud SLAs generally being worth what you don't pay for them, what can you do to protect yourself? Sean Hull in AirBNB didn’t have to fail   has some solid advice on how to deal with outages: Use Redundancy . Make database and webserver tiers redundant using multi-az or alternately read-replicas.  Have a browsing only mode . Give users a read-only version of your site. Users may not even notice failures as they will only see problems when they need to perform a write operation. Web Applications need Feature Flags . Build in the ability to turn off and on major parts of your site and flip the switch when problems arise. Consider Netflix’s Simian . By randomly causing outages in your application you can continually test your failover and redundancy infrastructure. Use multiple clouds . Use Redundant Arrays of Inexpensive Clouds as a way of surviving outages in any one particular cloud. None of these are easy and it's worth considering that your application may

4 0.092295609 183 high scalability-2007-12-12-Report from OpenSocial Meetup at Google

Introduction: Update: Facebook pulls a Microsoft and embraces and extends by opening their platform to other social sites like Bebo. Very smart and unexpected. More info at Facebook to let other sites access platform code . This month's regular Facebook Meetup was held at Google and the topic of the day was OpenSocial . For those of you with real lives, OpenSocial "provides a common set of APIs for social applications across multiple websites." Over 200 excited people, hoping to do very exciting things, and dreaming of making an exciting pile of money, watched an OpenSocial presentation put on by a couple of appropriately knowledgeable evangelists. I could feel my social graph being more successfully monetized with each passing minute. Normally the meetings are much smaller, but Google puts on a very nice spread, so I think people may have showed up to dine :-) Or they could have showed up to learn why and how they should code to the new uber social API. By the looks of the full pl

5 0.087578073 241 high scalability-2008-02-05-SLA monitoring

Introduction: Hi, We're running a enterprise SaaS solution that currently holds about 700 customers with up to 50.000 users per customer (growing quickly). Our customers have SLA agreements with us that contains guaranteed uptimes, response times and other performance counters. With an increasing number of customers and traffic we find it difficult to provide our customer with actual SLA data. We could set up external probes that monitors certain parts of the application, but this is time consuming with 700 customers (we do it today for our biggest clients). We can also extract data from web logs but they are now approaching about 30-40 GB a day. What we really need is monitoring software that not only focuses on the internal performance counters but also lets us see the application from the customers viewpoint and allows us to aggregate data in different ways. Would the best approach be to develop a custom solution (for instance a distributed app that aggregates data from different logs e

6 0.086070508 301 high scalability-2008-04-08-Google AppEngine - A First Look

7 0.082736224 450 high scalability-2008-11-24-Scalability Perspectives #3: Marc Andreessen – Internet Platforms

8 0.079577692 96 high scalability-2007-09-18-Amazon Architecture

9 0.078971475 517 high scalability-2009-02-21-Google AppEngine - A Second Look

10 0.076447368 1084 high scalability-2011-07-22-Stuff The Internet Says On Scalability For July 22, 2011

11 0.074772611 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT

12 0.073839314 641 high scalability-2009-06-29-Google App Engine plus Amazon AWS: Best of both worlds

13 0.073726714 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture

14 0.072708316 918 high scalability-2010-10-12-The CIO’s Problem: Cloud “Mess” or Cloud “Mash”

15 0.071225345 1575 high scalability-2014-01-08-Under Snowden's Light Software Architecture Choices Become Murky

16 0.068335414 1465 high scalability-2013-05-28-Sponsored Post: Blurocket, Incapsula, Dow Jones, Surge, Rackspace, Amazon, Booking, aiCache, Aerospike, Percona, ScaleOut, New Relic, LogicMonitor, AppDynamics, ManageEngine, Site24x7

17 0.067848921 46 high scalability-2007-07-30-Product: Sun Utility Computing

18 0.066234723 1055 high scalability-2011-06-08-Stuff to Watch from Google IO 2011

19 0.065681256 1457 high scalability-2013-05-14-Sponsored Post: Dow Jones, Spotify, Evernote, Surge, Rackspace, Amazon, Booking, aiCache, Aerospike, Percona, ScaleOut, New Relic, LogicMonitor, AppDynamics, ManageEngine, Site24x7

20 0.063813053 1095 high scalability-2011-08-09-Sponsored Post: Box, BetterWorks, New Relic, NoSQL Now!, Surge, Tungsten, AppDynamics, ScaleOut, Couchbase, CloudSigma, ManageEngine, Site24x7


similar blogs computed by lsi model

lsi for this blog:

topicId topicWeight

[(0, 0.101), (1, 0.006), (2, 0.032), (3, 0.056), (4, -0.015), (5, -0.05), (6, -0.016), (7, -0.036), (8, 0.036), (9, -0.032), (10, -0.026), (11, 0.01), (12, -0.007), (13, -0.013), (14, 0.013), (15, -0.013), (16, -0.029), (17, -0.002), (18, 0.056), (19, -0.058), (20, 0.03), (21, -0.011), (22, 0.013), (23, -0.014), (24, -0.006), (25, 0.01), (26, 0.002), (27, -0.022), (28, -0.022), (29, -0.033), (30, -0.009), (31, -0.047), (32, 0.009), (33, -0.041), (34, -0.009), (35, 0.047), (36, 0.034), (37, 0.003), (38, -0.004), (39, -0.001), (40, 0.015), (41, -0.01), (42, -0.018), (43, -0.066), (44, -0.037), (45, -0.01), (46, 0.007), (47, -0.002), (48, -0.007), (49, -0.01)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.98177487 475 high scalability-2008-12-22-SLAs in the SaaS space

Introduction: This may be a bit higher level then the general discussion here, but I think this is an important issue in how it relates to reliability and uptime. What kind of SLAs should we be expecting from SaaS services and platforms (e.g. AWS, Google App Engine, Google Premium Apps, salesforce.com, etc.)? Up to today, most SaaS services either have no SLAs or offer very weak penalties. What will it take to get these services up to the point where they can offer the SLAs that users (and more importantly, businesses) require? I presume most of the members here want to see more movement into the cloud and to SaaS services, and I'm thinking that until we see more substantial SLA guarantees, most businesses will continue to shy away as long as they can. Would love to hear what others think. Or am I totally off base?

2 0.74346679 299 high scalability-2008-04-07-Rumors of Signs and Portents Concerning Freeish Google Cloud

Introduction: Update 2: Rumor no more. Google Jumps Head First Into Web Services With Google App Engine . The quick and dirty of it: developers simply upload their Python code to Google, launch the application, and can monitor usage and other metrics via a multi-platform desktop application. There were 10,000 developer slots open and of course I was too late. More as the cobra strikes. Update: TechCrunch reports Google To Launch BigTable As Web Service next week. It competes with Amazon's SimpleDB. Though it won't be truly comparable until they also release an EC2 and S3 equivalent. An internet hit for each data access is a little painful. As Jimmy says in Goodfellas, "That's the way. You don't take no sh*t from nobody. " First Dave Winer hallucinates a pig on the mean streets of Walnut Creek that told him Google's long foretold cloud offering will be free for bloggers of "modest needs." GigaOM then says a free cloud service is how Google could eat Amazon's bacon for lunch .

3 0.67806333 641 high scalability-2009-06-29-Google App Engine plus Amazon AWS: Best of both worlds

Introduction: Google App Engine (GAE) is focused on making development easy, but limits your options. Amazon Web Services is focused on making development flexible, but complicates the development process. Real enterprise applications require both of these paradigms to achieve success… What we really want is the flexibility of AWS and the simplicity of GAE. For the rest of the post see  http://natishalom.typepad.com/nati_shaloms_blog/2009/06/google-app-engine-plus-amazon-aws-best-of-both-worlds.html

4 0.66378605 1575 high scalability-2014-01-08-Under Snowden's Light Software Architecture Choices Become Murky

Introduction: Adrian Cockcroft on the future of Cloud, Open Source, SaaS and the End of Enterprise Computing : Most big enterprise companies are actively working on their AWS rollout now. Most of them are also trying to get an in-house cloud to work, with varying amounts of success, but even the best private clouds are still years behind the feature set of public clouds, which is has a big impact on the agility and speed of product development While the Snowden revelations have tattered the thin veil of trust secreting Big Brother from We the People, they may also be driving a fascinating new tension in architecture choices between Cloud Native (scale-out, IaaS), Amazon Native (rich service dependencies), and Enterprise Native (raw hardware, scale-up). This tension became evident in a recent HipChat interview where HipChat, makers of an AWS based SaaS chat product, were busy creating an on-premises version of their product that could operate behind the firewall in

5 0.64423442 305 high scalability-2008-04-21-Google App Engine - what about existing applications?

Introduction: Recently, Google announced Google App Engine, another announcement in the rapidly growing world of cloud computing. This brings up some very serious questions: 1. If we want to take advantage of one of the clouds, are we doomed to be locked-in for life? 2. Must we re-write our existing applications to use the cloud? 3. Do we need to learn a brand new technology or language for the cloud? This post presents a pattern that will enable us to abstract our application code from the underlying cloud provider infrastructure. This will enable us to easily migrate our EXISTING applications to cloud based environment thus avoiding the need for a complete re-write.

6 0.6419223 1084 high scalability-2011-07-22-Stuff The Internet Says On Scalability For July 22, 2011

7 0.63819337 1647 high scalability-2014-05-14-Google Says Cloud Prices Will Follow Moore’s Law: Are We All Renters Now?

8 0.63366431 301 high scalability-2008-04-08-Google AppEngine - A First Look

9 0.62201327 1328 high scalability-2012-09-24-Google Spanner's Most Surprising Revelation: NoSQL is Out and NewSQL is In

10 0.62019843 853 high scalability-2010-07-08-Cloud AWS Infrastructure vs. Physical Infrastructure

11 0.6199981 1275 high scalability-2012-07-02-C is for Compute - Google Compute Engine (GCE)

12 0.61781496 1448 high scalability-2013-04-29-AWS v GCE Face-off and Why Innovation Needs Lower Cost Infrastructures

13 0.60812509 1627 high scalability-2014-04-07-Google Finds: Centralized Control, Distributed Data Architectures Work Better than Fully Decentralized Architectures

14 0.60718131 1078 high scalability-2011-07-12-Google+ is Built Using Tools You Can Use Too: Closure, Java Servlets, JavaScript, BigTable, Colossus, Quick Turnaround

15 0.60679215 640 high scalability-2009-06-28-Google Voice Architecture

16 0.60657382 531 high scalability-2009-03-11-Classifying XTP systems and how cloud changes which type startups will use

17 0.60399908 517 high scalability-2009-02-21-Google AppEngine - A Second Look

18 0.59877414 1107 high scalability-2011-08-29-The Three Ages of Google - Batch, Warehouse, Instant

19 0.5926491 618 high scalability-2009-06-05-Google Wave Architecture

20 0.59131932 1412 high scalability-2013-02-25-SongPop Scales to 1 Million Active Users on GAE, Showing PaaS is not Passé


similar blogs computed by lda model

lda for this blog:

topicId topicWeight

[(1, 0.11), (2, 0.157), (10, 0.086), (18, 0.263), (61, 0.194), (79, 0.052)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.85582513 475 high scalability-2008-12-22-SLAs in the SaaS space

Introduction: This may be a bit higher level then the general discussion here, but I think this is an important issue in how it relates to reliability and uptime. What kind of SLAs should we be expecting from SaaS services and platforms (e.g. AWS, Google App Engine, Google Premium Apps, salesforce.com, etc.)? Up to today, most SaaS services either have no SLAs or offer very weak penalties. What will it take to get these services up to the point where they can offer the SLAs that users (and more importantly, businesses) require? I presume most of the members here want to see more movement into the cloud and to SaaS services, and I'm thinking that until we see more substantial SLA guarantees, most businesses will continue to shy away as long as they can. Would love to hear what others think. Or am I totally off base?

2 0.76087397 1140 high scalability-2011-11-10-Kill the Telcos Save the Internet - The Unsocial Network

Introduction: Someone is killing the Internet. Since you probably use the Internet everyday you might find this surprising. It almost sounds silly, and the reason is technical, but our crack team of networking experts has examined the patient and made the diagnosis. What did they find? Diagnostic team : the  Packet Pushers  gang ( Greg Ferro , Jan Zorz , Ivan Pepelnjak ) in the podcast  How We Are Killing the Internet . Diagnosis : invasive tunnelation. ( tubes anyone? ) Prognosis : even Dr. House might not be able to help. Cure : go back to what the Internet was; kill the tunnels; route IPv4 and IPv6; have public addresses on everything; disrupt the telcos. This is a classic story in a strange setting--the network--but the themes are universal: centralization vs. decentralization (that's where the telcos obviously come in), good vs. evil, order vs. disorder, tyranny vs. freedom, change vs. stasis, simplicity vs. complexity. And it's all being carried out on battlefield few get

3 0.75172132 1344 high scalability-2012-10-19-Stuff The Internet Says On Scalability For October 19, 2012

Introduction: It's HighScalability Time: @davilagrau : Youtube, GitHub,..., Are cloud services facing a entropic limit to scalability? Async all the way down?  The Tyranny of the Clock : The cost of logic and memory dominated Turing's thinking, but today, communication rather than logic should dominate our thinking. Clock-free design uses less than half, about 40%, as much energy per addition as its clocked counterpart. We can regain the efficiency of local decision making by revolting against the pervasive beat of an external clock.  Why Google Compute Engine for OpenStack . Smart move. Having OpenStack work inside a super charged cloud, in private clouds, and as a bridge between the two ought to be quite attractive to developers looking for some sort of ally for independence. All it will take are a few victories to cement new alliances. 3 Lessons That Startups Can Learn From Facebook’s Failed Credits Experiment . I thought this was a great idea too. So what happened? FACEBOOK DID NOT

4 0.75164455 379 high scalability-2008-09-04-Database question for upcoming project

Introduction: We will be developing an RIA that will have a lot of database access. Think something like a QuickBooks but with about 50 transactions entered per hour per user. Users will be in the system for 7 to 9 hours a day and there will be around 20,000 users, all logged in at the same time. Reporting will be done just like a QuickBooks style app plus a lot of extra things you don't do in QuickBooks. Our operations is familiar with W2003 Server and MS SQL Server so they are recommending we stick with that. I originally requested Linux and PostgreSQL. How far can a single database server get me? If we have a 4 processor, 8 core, 128gb server, how far am I going to get before I need to shard or do something else? I know there are a lot of factors involved but in general for this size of a site, what should the strategy be? I've read almost all articles on this website but most of the applications are not RIA type of apps with this type of usage or they are architectures for

5 0.74269068 139 high scalability-2007-10-30-Paper: Dynamo: Amazon’s Highly Available Key-value Store

Introduction: Update 2 : Read/WriteWeb has a good article talking about the scalability issues of relational databases and how Dynamo solves them: Amazon Dynamo: The Next Generation Of Virtual Distributed Storage . But since Dynamo is just another frustrating walled garden protected by barbed wire and guard dogs, its relevance is somewhat overstated. Update : Greg Linden has a take on the paper where he questions some of Amazon's design choices: emphasizing write availability over fast reads, a lack of indexing support, use of random distribution for load balancing, and punting on some scalability issues. Werner Vogels, Amazon's avuncular CTO, just announced a new paper on the internal database technology Amazon uses to handle tens of millions customers. I'll dive into more details later, but I thought you'd want to read it hot off the blog. The bad news is it won't be a service. They are keeping this tech not so secret, but very safe. Happily, it's another real-life example to learn from.

6 0.72021878 64 high scalability-2007-08-10-How do we make a large real-time search engine?

7 0.7198382 150 high scalability-2007-11-12-Slashdot Architecture - How the Old Man of the Internet Learned to Scale

8 0.71787649 1031 high scalability-2011-04-28-PaaS on OpenStack - Run Applications on Any Cloud, Any Time Using Any Thing

9 0.71605331 1411 high scalability-2013-02-22-Stuff The Internet Says On Scalability For February 22, 2013

10 0.71578252 1184 high scalability-2012-01-31-Performance in the Cloud: Business Jitter is Bad

11 0.70900565 383 high scalability-2008-09-10-Shard servers -- go big or small?

12 0.70877016 1287 high scalability-2012-07-20-Stuff The Internet Says On Scalability For July 20, 2012

13 0.70862281 1390 high scalability-2013-01-21-Processing 100 Million Pixels a Day - Small Amounts of Contention Cause Big Problems at Scale

14 0.70768905 1360 high scalability-2012-11-19-Gone Fishin': Tumblr Architecture - 15 Billion Page Views A Month And Harder To Scale Than Twitter

15 0.70768893 1191 high scalability-2012-02-13-Tumblr Architecture - 15 Billion Page Views a Month and Harder to Scale than Twitter

16 0.7073034 1461 high scalability-2013-05-20-The Tumblr Architecture Yahoo Bought for a Cool Billion Dollars

17 0.70577222 1089 high scalability-2011-07-29-Stuff The Internet Says On Scalability For July 29, 2011

18 0.70028073 1142 high scalability-2011-11-14-Using Gossip Protocols for Failure Detection, Monitoring, Messaging and Other Good Things

19 0.69992447 775 high scalability-2010-02-10-ElasticSearch - Open Source, Distributed, RESTful Search Engine

20 0.69939846 501 high scalability-2009-01-25-Where do I start?