high_scalability high_scalability-2008 high_scalability-2008-301 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: I haven't developed an AppEngine application yet, I'm just taking a look around their documentation and seeing what stands out for me. It's not the much speculated super cluster VM . AppEngine is solidly grounded in code and structure. It reminds me a little of the guy who ran a website out of S3 with a splash of Heroku thrown in as a chaser. The idea is clearly to take advantage of our massive multi-core future by creating a shared nothing infrastructure based firmly on a core set of infinitely scalable database, storage and CPU services. Don't forget Google also has a few other services to leverage: email, login, blogs, video, search, ads, metrics, and apps. A shared nothing request is a simple beast. By its very nature shared nothing architectures must be composed of services which are themselves already scalable and Google is signing up to supply that scalable infrastructure. Google has been busy creating a platform of out-of-the-box scalable services to build
sentIndex sentText sentNum sentScore
1 By its very nature shared nothing architectures must be composed of services which are themselves already scalable and Google is signing up to supply that scalable infrastructure. [sent-8, score-0.335]
2 CGI is the perfect metaphor for our brave new app container world: get a request, process the request, die, repeat. [sent-15, score-0.348]
3 Using AppEngine you have no choice but to write an app that can be splayed across a pointy well sharpened CPU grid. [sent-16, score-0.286]
4 You basically make a Python app using services and it scales. [sent-33, score-0.355]
5 If email needs to be sent every hour, for example, who will invoke your service every hour so you can get the CPU to send the email? [sent-45, score-0.286]
6 - An application can only access other computers on the Internet through the provided URL fetch and email services and APIs. [sent-63, score-0.313]
7 An app can read files, but only files uploaded with the application code. [sent-66, score-0.417]
8 The app must use the App Engine datastore for all data that persists between requests. [sent-67, score-0.381]
9 A request handler cannot spawn a sub-process or execute code after the response has been sent. [sent-69, score-0.3]
10 An update of a entity occurs in a transaction that is retried a fixed number of times if other processes are trying to update the same entity simultaneously. [sent-76, score-0.243]
11 Your application can assign entities to groups when the entities are created. [sent-80, score-0.443]
12 You've got mail: Applications can also send email messages using App Engine's mail service. [sent-81, score-0.25]
13 The mail service also uses Google infrastructure to send email messages. [sent-82, score-0.302]
14 You can bundle a framework of your choosing with your application code by copying its code into your application directory. [sent-98, score-0.373]
15 Google has their own framework called webapp . [sent-99, score-0.244]
16 Here's a hello world application using webapp: import wsgiref. [sent-101, score-0.261]
17 When webapp receives an HTTP GET request to the URL /, it instantiates the MainPage class and calls the instance's get method. [sent-116, score-0.381]
18 webapp sends a response based on the final state of the MainPage instance. [sent-121, score-0.31]
19 The parameter debug=true passed to its constructor tells webapp to print stack traces to the browser output if a handler encounters an error or raises an uncaught exception. [sent-124, score-0.285]
20 When your application is running on App Engine, users will be directed to the Google Accounts sign-in page, then redirected back to your application after successfully signing in or creating an account. [sent-128, score-0.379]
wordName wordTfidf (topN-words)
[('appengine', 0.296), ('app', 0.286), ('mainpage', 0.24), ('engine', 0.226), ('google', 0.211), ('pet', 0.204), ('webapp', 0.188), ('cgi', 0.169), ('entities', 0.156), ('application', 0.131), ('request', 0.131), ('import', 0.13), ('email', 0.113), ('handler', 0.097), ('entity', 0.096), ('datastore', 0.095), ('def', 0.087), ('pure', 0.087), ('nice', 0.083), ('mail', 0.078), ('response', 0.072), ('scalable', 0.071), ('second', 0.071), ('cpu', 0.07), ('services', 0.069), ('python', 0.067), ('signing', 0.067), ('property', 0.067), ('cat', 0.066), ('true', 0.063), ('get', 0.062), ('url', 0.06), ('per', 0.059), ('tied', 0.059), ('ror', 0.059), ('send', 0.059), ('nothing', 0.057), ('framework', 0.056), ('blog', 0.056), ('copying', 0.055), ('login', 0.054), ('cron', 0.052), ('service', 0.052), ('type', 0.052), ('multicore', 0.051), ('string', 0.051), ('transaction', 0.051), ('creating', 0.05), ('final', 0.05), ('documentation', 0.049)]
simIndex simValue blogId blogTitle
same-blog 1 0.9999994 301 high scalability-2008-04-08-Google AppEngine - A First Look
Introduction: I haven't developed an AppEngine application yet, I'm just taking a look around their documentation and seeing what stands out for me. It's not the much speculated super cluster VM . AppEngine is solidly grounded in code and structure. It reminds me a little of the guy who ran a website out of S3 with a splash of Heroku thrown in as a chaser. The idea is clearly to take advantage of our massive multi-core future by creating a shared nothing infrastructure based firmly on a core set of infinitely scalable database, storage and CPU services. Don't forget Google also has a few other services to leverage: email, login, blogs, video, search, ads, metrics, and apps. A shared nothing request is a simple beast. By its very nature shared nothing architectures must be composed of services which are themselves already scalable and Google is signing up to supply that scalable infrastructure. Google has been busy creating a platform of out-of-the-box scalable services to build
2 0.27956384 517 high scalability-2009-02-21-Google AppEngine - A Second Look
Introduction: Update 6: : Back to the Future for Data Storage . We are in the middle of a renaissance in data storage with the application of many new ideas and techniques; there's huge potential for breaking out of thinking about data storage in just one way. Update 5 : Building Scalable Web Applications with Google App Engine by Brett Slatkin. Update 4 : Why Google App Engine is broken and what Google must do to fix it by Aral Balkan. We don't care that it can scale. We care that it does scale. And that it scales when you need it the most. Issues: 1MB limit on data structures; 1MB limit on data structures; the short-term high CPU quota; quotas in general; Admin? What's that? Update 3 : BigTable Blues . Catherine Devlin couldn't port an application to GAE because it can't do basic filtering and can't search 5,000 records without timing out: "Querying from 5000 records - too much for the mighty BigTable, apparently." Followup: not the future database . "90% of the work of this proje
Introduction: When I was a child, I spake as a child, I understood as a child, I thought as a child: but when I became a man, I put away childish things . -- Corinthians With this new pricing, developments will be driven by the costs . I like to optimize my apps to make them better or faster, but to optimize them just to make them cheaper is a waste of time. -- Sylvain on Google Groups The dream is dead. Google App Engine's bold pay for what you use dream dies as it leaves childish things behind and becomes a real product . Pricing will change . Architectures will change. Customers will change. Hearts and minds will change. But Google App Engine will survive. Google is shutting down many of its projects . GAE is not among them. Do we have GAE's pricing change to thank for it surving the more wood behind more deadly arrows push? Without a radical and quick shift towards profitably GAE would no doubt be a historical footnote in the long scroll of good ideas. The urgency involve
4 0.21125148 1055 high scalability-2011-06-08-Stuff to Watch from Google IO 2011
Introduction: With the Google IO Developer Conference completed there are dozens and dozens of information packed videos now available. While you won't get any of the nifty free swag the attendees rake in, it's great of Google to make these videos available so quickly after the conference. Let's say you don't want to watch all the videos on the pretense you have a life, here are just a dozen scalability and architecture related videos you might find interesting: App Engine Backends by Justin Haugh, Greg Darke. One of this biggest complaints about GAE are the request deadlines. Those are now gone when you rent a new Backend node. Scaling App Engine Applications by Justin Haugh, Guido van Rossum. Two parts: how App Engine scales internally and how you as a programmer make it scale using the tools. Good discussion of scaling and why it's hard; 10,000 queries per second is a large app that needs good architecting; a good discussion of GAE's predictive scaling formula of how it decides w
5 0.1915094 327 high scalability-2008-05-27-How I Learned to Stop Worrying and Love Using a Lot of Disk Space to Scale
Introduction: Update 3 : ReadWriteWeb says Google App Engine Announces New Pricing Plans, APIs, Open Access . Pricing is specified but I'm not sure what to make of it yet. An image manipulation library is added (thus the need to pay for more CPU :-) and memcached support has been added. Memcached will help resolve the can't write for every read problem that pops up when keeping counters. Update 2 : onGWT.com threw a GAE load party and a lot of people came. The results at Load test : Google App Engine = 1, Community = 0 . GAE handled a peak of 35 requests/second and a sustained 10 requests/second. Some think performance was good, others not so good. My GMT watch broke and I was late to arrive. Maybe next time. Also added a few new design rules from the post. Update : Added a few new rules gleaned from the GAE Meetup : Design By Explicit Cost Model and Puts are Precious. How do you structure your database using a distributed hash table like BigTable ? The answer isn't what you might expect. If
6 0.18094583 687 high scalability-2009-08-24-How Google Serves Data from Multiple Datacenters
7 0.17438811 307 high scalability-2008-04-21-Using Google AppEngine for a Little Micro-Scalability
10 0.16484866 299 high scalability-2008-04-07-Rumors of Signs and Portents Concerning Freeish Google Cloud
11 0.16330095 972 high scalability-2011-01-11-Google Megastore - 3 Billion Writes and 20 Billion Read Transactions Daily
12 0.15302801 1084 high scalability-2011-07-22-Stuff The Internet Says On Scalability For July 22, 2011
13 0.14793815 279 high scalability-2008-03-17-Microsoft's New Database Cloud Ready to Rumble with Amazon
14 0.14495972 1501 high scalability-2013-08-13-In Memoriam: Lavabit Architecture - Creating a Scalable Email Service
15 0.14486417 1275 high scalability-2012-07-02-C is for Compute - Google Compute Engine (GCE)
16 0.1393306 765 high scalability-2010-01-25-Let's Welcome our Neo-Feudal Overlords
17 0.13730642 96 high scalability-2007-09-18-Amazon Architecture
18 0.13514903 853 high scalability-2010-07-08-Cloud AWS Infrastructure vs. Physical Infrastructure
19 0.13373797 787 high scalability-2010-03-03-Hot Scalability Links for March 3, 2010
20 0.13283731 1102 high scalability-2011-08-22-Strategy: Run a Scalable, Available, and Cheap Static Site on S3 or GitHub
topicId topicWeight
[(0, 0.281), (1, 0.126), (2, 0.01), (3, 0.005), (4, -0.027), (5, -0.052), (6, 0.029), (7, 0.017), (8, 0.035), (9, -0.005), (10, -0.018), (11, -0.009), (12, -0.007), (13, -0.039), (14, 0.016), (15, -0.106), (16, -0.128), (17, -0.077), (18, 0.158), (19, -0.082), (20, 0.08), (21, -0.07), (22, 0.011), (23, -0.107), (24, 0.083), (25, 0.039), (26, 0.041), (27, -0.052), (28, 0.005), (29, -0.021), (30, -0.025), (31, -0.12), (32, 0.054), (33, 0.007), (34, -0.035), (35, -0.018), (36, 0.008), (37, -0.047), (38, 0.031), (39, 0.019), (40, -0.013), (41, 0.01), (42, -0.007), (43, -0.035), (44, 0.056), (45, 0.019), (46, 0.031), (47, 0.065), (48, -0.043), (49, 0.019)]
simIndex simValue blogId blogTitle
same-blog 1 0.98275012 301 high scalability-2008-04-08-Google AppEngine - A First Look
Introduction: I haven't developed an AppEngine application yet, I'm just taking a look around their documentation and seeing what stands out for me. It's not the much speculated super cluster VM . AppEngine is solidly grounded in code and structure. It reminds me a little of the guy who ran a website out of S3 with a splash of Heroku thrown in as a chaser. The idea is clearly to take advantage of our massive multi-core future by creating a shared nothing infrastructure based firmly on a core set of infinitely scalable database, storage and CPU services. Don't forget Google also has a few other services to leverage: email, login, blogs, video, search, ads, metrics, and apps. A shared nothing request is a simple beast. By its very nature shared nothing architectures must be composed of services which are themselves already scalable and Google is signing up to supply that scalable infrastructure. Google has been busy creating a platform of out-of-the-box scalable services to build
2 0.91298836 517 high scalability-2009-02-21-Google AppEngine - A Second Look
Introduction: Update 6: : Back to the Future for Data Storage . We are in the middle of a renaissance in data storage with the application of many new ideas and techniques; there's huge potential for breaking out of thinking about data storage in just one way. Update 5 : Building Scalable Web Applications with Google App Engine by Brett Slatkin. Update 4 : Why Google App Engine is broken and what Google must do to fix it by Aral Balkan. We don't care that it can scale. We care that it does scale. And that it scales when you need it the most. Issues: 1MB limit on data structures; 1MB limit on data structures; the short-term high CPU quota; quotas in general; Admin? What's that? Update 3 : BigTable Blues . Catherine Devlin couldn't port an application to GAE because it can't do basic filtering and can't search 5,000 records without timing out: "Querying from 5000 records - too much for the mighty BigTable, apparently." Followup: not the future database . "90% of the work of this proje
3 0.83592343 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
Introduction: When I was a child, I spake as a child, I understood as a child, I thought as a child: but when I became a man, I put away childish things . -- Corinthians With this new pricing, developments will be driven by the costs . I like to optimize my apps to make them better or faster, but to optimize them just to make them cheaper is a waste of time. -- Sylvain on Google Groups The dream is dead. Google App Engine's bold pay for what you use dream dies as it leaves childish things behind and becomes a real product . Pricing will change . Architectures will change. Customers will change. Hearts and minds will change. But Google App Engine will survive. Google is shutting down many of its projects . GAE is not among them. Do we have GAE's pricing change to thank for it surving the more wood behind more deadly arrows push? Without a radical and quick shift towards profitably GAE would no doubt be a historical footnote in the long scroll of good ideas. The urgency involve
4 0.83209038 1055 high scalability-2011-06-08-Stuff to Watch from Google IO 2011
Introduction: With the Google IO Developer Conference completed there are dozens and dozens of information packed videos now available. While you won't get any of the nifty free swag the attendees rake in, it's great of Google to make these videos available so quickly after the conference. Let's say you don't want to watch all the videos on the pretense you have a life, here are just a dozen scalability and architecture related videos you might find interesting: App Engine Backends by Justin Haugh, Greg Darke. One of this biggest complaints about GAE are the request deadlines. Those are now gone when you rent a new Backend node. Scaling App Engine Applications by Justin Haugh, Guido van Rossum. Two parts: how App Engine scales internally and how you as a programmer make it scale using the tools. Good discussion of scaling and why it's hard; 10,000 queries per second is a large app that needs good architecting; a good discussion of GAE's predictive scaling formula of how it decides w
5 0.7917065 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 .
6 0.77843976 763 high scalability-2010-01-22-How BuddyPoke Scales on Facebook Using Google App Engine
7 0.76140666 1084 high scalability-2011-07-22-Stuff The Internet Says On Scalability For July 22, 2011
8 0.72774345 1275 high scalability-2012-07-02-C is for Compute - Google Compute Engine (GCE)
9 0.72732848 307 high scalability-2008-04-21-Using Google AppEngine for a Little Micro-Scalability
10 0.72402871 1143 high scalability-2011-11-16-Google+ Infrastructure Update - the JavaScript Story
11 0.72142458 641 high scalability-2009-06-29-Google App Engine plus Amazon AWS: Best of both worlds
13 0.70950115 949 high scalability-2010-11-29-Stuff the Internet Says on Scalability For November 29th, 2010
14 0.70142066 618 high scalability-2009-06-05-Google Wave Architecture
15 0.69992673 1117 high scalability-2011-09-16-Stuff The Internet Says On Scalability For September 16, 2011
16 0.69869596 1432 high scalability-2013-04-01-Khan Academy Checkbook Scaling to 6 Million Users a Month on GAE
17 0.69060522 765 high scalability-2010-01-25-Let's Welcome our Neo-Feudal Overlords
18 0.68930441 527 high scalability-2009-03-06-Cloud Programming Directly Feeds Cost Allocation Back into Software Design
19 0.68759739 1023 high scalability-2011-04-14-Strategy: Cache Application Start State to Reduce Spin-up Times
20 0.68266934 1540 high scalability-2013-10-30-Strategy: Use Your Quantum Computer Lab to Tell Intentional Blinks from Involuntary Blinks
topicId topicWeight
[(1, 0.116), (2, 0.182), (10, 0.053), (22, 0.124), (30, 0.028), (40, 0.028), (47, 0.036), (56, 0.018), (57, 0.01), (61, 0.102), (77, 0.014), (79, 0.122), (85, 0.014), (94, 0.091)]
simIndex simValue blogId blogTitle
Introduction: The story of driving the golden spike to symbolize the completion of the transcontinental railroad is famous in the US. What is not so well known is the story of how it also foreshadowed changes to come as an early version of both the Internet and the Internet of Things. But that was 1869, how can that possibly be? Telegraph as Internet First, let's establish the telegraph and cable systems was an early version of an Internet. As railroad tracks were being laid a transcontental telegraph system was also being constructed. Telegraph lines were installed parallel to the tracks making instant communication available across the continent, faster than any horse could ride. With the transalantic cable system information could quickly span continents in minutes: The miles of American telegraph grew from 40 in 1846 to 12,000 in 1850 to 23,000 in 1852. In Europe it increased from 2,000 in 1849 to 110,000 in 1869. The cost of sending 10 words was $1.55 in 1850, $1 in 1870, 40
same-blog 2 0.92495471 301 high scalability-2008-04-08-Google AppEngine - A First Look
Introduction: I haven't developed an AppEngine application yet, I'm just taking a look around their documentation and seeing what stands out for me. It's not the much speculated super cluster VM . AppEngine is solidly grounded in code and structure. It reminds me a little of the guy who ran a website out of S3 with a splash of Heroku thrown in as a chaser. The idea is clearly to take advantage of our massive multi-core future by creating a shared nothing infrastructure based firmly on a core set of infinitely scalable database, storage and CPU services. Don't forget Google also has a few other services to leverage: email, login, blogs, video, search, ads, metrics, and apps. A shared nothing request is a simple beast. By its very nature shared nothing architectures must be composed of services which are themselves already scalable and Google is signing up to supply that scalable infrastructure. Google has been busy creating a platform of out-of-the-box scalable services to build
3 0.91826534 1645 high scalability-2014-05-09-Stuff The Internet Says On Scalability For May 9th, 2014
Introduction: Hey, it's HighScalability time: NASA captures Guatemala volcano erupting from space 40,000 exabytes : from now until 2020, the digital universe will about double every two years; $650,000 : amount raised by the MaydayPAC in one week. Quotable Quotes: @BenedictEvans : Masayoshi Son: $20m initial investment in Alibaba, current stake worth $58bn. @iamdevloper : I sneezed earlier and Siri compiled it to valid Perl. @cdixon : "There is not enough competition in the last mile market to allow a true market to function" @PatrickMcFadin : Get ready for some serious server density. AMD is working on K12, brand-new x86 and ARM cores. This plus 8T SSD? With age comes changing priorities. Facebook is now 10 and has grown up . They are no longer moving fast and breaking things. They are now into the stability thing. Letting developers know they are a stable platform. The play is to get all that beautiful data from developers by bei
4 0.9142279 1621 high scalability-2014-03-28-Stuff The Internet Says On Scalability For March 28th, 2014
Introduction: Hey, it's HighScalability time: Looks like a multiverse , if you can keep it. Quotable Quotes: @abt_programming : "I am a Unix Creationist. I believe the world was created on January 1, 1970 and as prophesized, will end on January 19, 2038" - @teropa @demisbellot : Cloud prices are hitting attractive price points, one more 40-50% drop and there'd be little reason to go it alone. @scott4arrows : Dentist "Do you floss regularly?" Me "Do you back up your computer data regularly?" @avestal : "I Kickstarted the Oculus Rift, what do I get?" You get a lesson in how capitalism works. @mtabini : “$20 charger that cost $2 to make.” Not pictured here: the $14 you pay for the 10,000 charger iterations that never made it to production. @strlen : "I built the original assembler in JS, because it's what I prefer to use when I need to get down to bare metal." - Adm. Grace Hopper tedchs : I'd like to propose a new rule for Hacker News: only if you have b
5 0.90171075 1543 high scalability-2013-11-05-10 Things You Should Know About AWS
Introduction: Authored by Chris Fregly : Former Netflix Streaming Platform Engineer, AWS Certified Solution Architect and Purveyor of fluxcapacitor.com. Ahead of the upcoming 2nd annual re:Invent conference, inspired by Simone Brunozzi’s recent presentation at an AWS Meetup in San Francisco, and collected from a few of my recent Fluxcapacitor.com consulting engagements, I’ve compiled a list of 10 useful time and clock-tick saving tips about AWS. 1) Query AWS resource metadata Can’t remember the EBS-Optimized IO throughput of your c1.xlarge cluster? How about the size limit of an S3 object on a single PUT? awsnow.info is the answer to all of your AWS-resource metadata questions. Interested in integrating awsnow.info with your application? You’re in luck. There’s now a REST API , as well! Note: These are default soft limits and will vary by account. 2) Tame your S3 buckets Delete an entire S3 bucket with a single CLI command:
6 0.89642972 1090 high scalability-2011-08-01-Peecho Architecture - scalability on a shoestring
7 0.89595175 1402 high scalability-2013-02-07-Ask HighScalability: Web asset server concept - 3rd party software available?
8 0.89412653 1180 high scalability-2012-01-24-The State of NoSQL in 2012
9 0.89290494 1649 high scalability-2014-05-16-Stuff The Internet Says On Scalability For May 16th, 2014
10 0.89102137 517 high scalability-2009-02-21-Google AppEngine - A Second Look
11 0.88921589 851 high scalability-2010-07-02-Hot Scalability Links for July 2, 2010
12 0.88862532 706 high scalability-2009-09-16-The VeriScale Architecture - Elasticity and efficiency for private clouds
13 0.88787585 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
14 0.88712656 776 high scalability-2010-02-12-Hot Scalability Links for February 12, 2010
15 0.88607234 1382 high scalability-2013-01-07-Analyzing billions of credit card transactions and serving low-latency insights in the cloud
16 0.88524812 1516 high scalability-2013-09-13-Stuff The Internet Says On Scalability For September 13, 2013
17 0.88506979 976 high scalability-2011-01-20-75% Chance of Scale - Leveraging the New Scaleogenic Environment for Growth
18 0.88479811 1117 high scalability-2011-09-16-Stuff The Internet Says On Scalability For September 16, 2011
19 0.88424212 1559 high scalability-2013-12-06-Stuff The Internet Says On Scalability For December 6th, 2013
20 0.88413644 1148 high scalability-2011-11-29-DataSift Architecture: Realtime Datamining at 120,000 Tweets Per Second