high_scalability high_scalability-2012 high_scalability-2012-1256 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Ivan Pepelnjak (CCIE#1354 Emeritus) is Chief Technology Advisor at NIL Data Communications , author of numerous webinars and advanced networking books , and a prolific blogger . He’s focusing on data center and cloud networking, network virtualization, and scalable application design. OpenFlow is an interesting emerging networking technology appearing seemingly out of nowhere with much hype and fanfare in March 2011. More than a year later, there are two commercial products based on OpenFlow ( NEC’s Programmable Flow and Nicira’s Network Virtualization Platform ) and probably less than a dozen production-grade implementations (including Google’s G-Scale network and Indiana University’s campus network ). Is this an expected result for an emerging technology or another case of overhyped technology hitting limits imposed by reality? OpenFlow-based solutions have to overcome numerous problems every emerging technology is facing, in OpenFlow’s case ranging from compatibili
sentIndex sentText sentNum sentScore
1 OpenFlow is an interesting emerging networking technology appearing seemingly out of nowhere with much hype and fanfare in March 2011. [sent-3, score-0.26]
2 The forwarding tables are set up by software – the control plane – that is usually embedded in the same networking device. [sent-10, score-0.588]
3 There are a few notable exceptions, including wireless access points with central controllers and data center switch clusters using Borg architecture (no, that’s not an official term for a cluster of devices with a single control plane). [sent-11, score-0.528]
4 OpenFlow is a standardized protocol that can be used between control- and forwarding planes. [sent-12, score-0.237]
5 The architecture where the control plane is centralized and separate from the physical devices is called Software Defined Networking according to the definition promoted by the Open Networking Foundation . [sent-13, score-0.437]
6 Using OpenFlow, you could buy forwarding devices from any vendor (or multiple vendors) and program their forwarding tables with open-source control plane software running on low-cost commodity x86 hardware . [sent-14, score-0.741]
7 ” Scalable SDN Example Some solutions use OpenFlow to program a number of independent devices that don’t interact with each other. [sent-31, score-0.313]
8 Each hypervisor switch is totally independent from all other switches and does not interact with them directly; user (VM) traffic is encapsulated in IP datagrams and sent to the network , which is supposed to provide end-to-end IP transport. [sent-37, score-0.455]
9 NVP is focused exclusively on the hypervisor switches and does not interact with the physical networking devices at all; even server NIC bonding and failover is left to the Linux kernel. [sent-38, score-0.67]
10 In their planned solution, they would use OpenFlow to intercept initial user traffic (until the user passes authentication) and to download access policy (usually in form of Access Control List – ACL) to the edge device (wireless or Ethernet switch). [sent-45, score-0.228]
11 The only shared object in the system Indiana University is planning to build is the central policy database, which would be accessed by a cluster of OpenFlow controllers interacting with individual networking devices. [sent-46, score-0.324]
12 Scaling the controller cluster to cope with the growing number of controlled devices is thus a trivial exercise. [sent-47, score-0.345]
13 For example, NEC has implemented an OpenFlow controller that is supposed to control the whole data center network. [sent-52, score-0.234]
14 But even there, their implementation quickly hit real-life limits: The number of flows a physical device can handle in hardware is limited, and the software-based devices are still too slow. [sent-53, score-0.338]
15 A device using hardware-based packet forwarding can install only a limited number of flows in a time period (usually less than thousand flows per second), a fact that is well known to manufacturers and users of high-end routers . [sent-55, score-0.409]
16 There’s also the “slight” problem of network devices losing connectivity with the central controller if the primary uplink fails. [sent-59, score-0.427]
17 They use traditional routing protocols (BGP+IS-IS) between sites and further influence traffic flow with proprietary traffic engineering technology similar (in functionality) to MPLS-TP. [sent-63, score-0.316]
18 A single OpenFlow controller can control only a few dozens of top-of-rack switches without supporting “linecard protocols” like LACP or BFD, or running routing protocols or spanning tree protocol (STP) with the external devices. [sent-66, score-0.47]
19 Some of them focused on controlling a large number of independent edge devices, others decided to use the advantages of OpenFlow while retaining the distributed nature of the system that gives large-scale IP networks (example: the Internet) their resilience. [sent-70, score-0.24]
20 They use OpenFlow solely to control of a cluster of local devices and combine local controllers with centralized path computation and traditional time-proven technologies (routing protocols). [sent-72, score-0.485]
wordName wordTfidf (topN-words)
[('openflow', 0.733), ('devices', 0.184), ('forwarding', 0.183), ('networking', 0.159), ('nvp', 0.143), ('sdn', 0.121), ('controllers', 0.108), ('controller', 0.108), ('chipsets', 0.107), ('plane', 0.105), ('switches', 0.1), ('edge', 0.098), ('interact', 0.088), ('control', 0.086), ('device', 0.082), ('network', 0.078), ('flows', 0.072), ('protocols', 0.072), ('relied', 0.07), ('ip', 0.069), ('nec', 0.065), ('centralized', 0.062), ('wan', 0.062), ('summit', 0.058), ('networks', 0.057), ('central', 0.057), ('campus', 0.056), ('university', 0.055), ('usually', 0.055), ('limits', 0.054), ('protocol', 0.054), ('switch', 0.053), ('thus', 0.053), ('technology', 0.053), ('routing', 0.05), ('exclusively', 0.048), ('emerging', 0.048), ('example', 0.048), ('traffic', 0.048), ('alternate', 0.048), ('hypervisor', 0.047), ('defined', 0.045), ('traditional', 0.045), ('focused', 0.044), ('numerous', 0.044), ('compatibility', 0.042), ('independent', 0.041), ('march', 0.04), ('overcome', 0.04), ('center', 0.04)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000002 1256 high scalability-2012-06-04-OpenFlow-SDN is Not a Silver Bullet for Network Scalability
Introduction: Ivan Pepelnjak (CCIE#1354 Emeritus) is Chief Technology Advisor at NIL Data Communications , author of numerous webinars and advanced networking books , and a prolific blogger . He’s focusing on data center and cloud networking, network virtualization, and scalable application design. OpenFlow is an interesting emerging networking technology appearing seemingly out of nowhere with much hype and fanfare in March 2011. More than a year later, there are two commercial products based on OpenFlow ( NEC’s Programmable Flow and Nicira’s Network Virtualization Platform ) and probably less than a dozen production-grade implementations (including Google’s G-Scale network and Indiana University’s campus network ). Is this an expected result for an emerging technology or another case of overhyped technology hitting limits imposed by reality? OpenFlow-based solutions have to overcome numerous problems every emerging technology is facing, in OpenFlow’s case ranging from compatibili
2 0.15568779 1147 high scalability-2011-11-25-Stuff The Internet Says On Scalability For November 25, 2011
Introduction: A HighScalability a day keeps the fail whale away.: 46 million turkeys eaten at Thanksgiving ; Pinterest 421 million pageviews Quotable quotes: @al3xandr3 : scalability demands decoupling @startupandrew : "Yesterday I did some digestive system scalability testing" -- in reference to eating 140 chicken nuggets Peter Wayner : While the crazy dreamers can continue to craft NoSQL data stores, serious people will want to take a look at Oracle's version. @weblearning : Unitil we get scalability - or that wonderful word massification - in education, we will not get value for money Embrace and extend: @conor_omahony : IBM is Baking NoSQL Capabilities into DB2 and Informix. @GGopman : I look for scalability. That's what turns me on Supercomputing: An Industry in Need of a Revolution . Bartosz Milewski wants decently paying, interesting and meaningful jobs for all (supercomputer programmers). Get on that Santa. Caching a
Introduction: For years a war has been fought in the software architecture trenches between the ideal of decentralized services and the power and practicality of centralized services. Centralized architectures, at least at the management and control plane level, are winning. And Google not only agrees, they are enthusiastic adopters of this model, even in places you don't think it should work. Here's an excerpt from Google Lifts Veil On “Andromeda” Virtual Networking , an excellent article by Timothy Morgan, that includes a money quote from Amin Vahdat , distinguished engineer and technical lead for networking at Google: Like many of the massive services that Google has created, the Andromeda network has centralized control. By the way, so did the Google File System and the MapReduce scheduler that gave rise to Hadoop when it was mimicked, so did the BigTable NoSQL data store that has spawned a number of quasi-clones, and even the B4 WAN and the Spanner distributed file system that have yet
4 0.11505842 1157 high scalability-2011-12-14-Virtualization and Cloud Computing is Changing the Network to East-West Routing
Introduction: It’s called “east-west” networking, which when compared to its predecessor, “north-south” networking, evinces images of maelstroms and hurricane winds and tsunamis for some reason. It could be the subtle correlation between the transformative shift this change in networking patterns has on the data center with that of El Niño’s transformative power upon the weather patterns across the globe. Traditionally, data center networks have focused on North-South network traffic. The assumption is that clients on the edge would mainly communicate with servers at the core, rather than across the network to other clients. But server virtualization changes all this, with servers, virtual appliances and even virtual desktops scattered across the same physical infrastructure. These environments are also highly dynamic, with workloads moving to different physical locations on the network as virtual servers are migrated (in the case of data center networks) and clients move
5 0.10187452 1053 high scalability-2011-06-06-Apple iCloud: Syncing and Distributed Storage Over Streaming and Centralized Storage
Introduction: There has been a lot of speculation over how Apple's iCloud would work. With the Apple Worldwide Developers Conference keynotes having just completed, we finally learned the truth. We can handle it. They made some interesting and cost effective architecture choices that preserved the value of their devices and the basic model of how their existing services work. A lot of pundits foretold that with all the datacenters Apple was building we would get a streaming music solution. Only one copy of music would be stored and then streamed on demand to everyone. Or they could go the Google brute force method and copy up all a user's music and play it on demand. Apple did neither. The chose an interesting middle path that's not Google, Amazon, or even MobileMe. They key idea is you no longer need a PC. Device content is now synced over the air and is managed by the cloud, not your legacy computer. Your data may not even be stored in the cloud, but the whole management, syncing, and co
6 0.1016158 944 high scalability-2010-11-17-Some Services are More Equal than Others
7 0.095628947 1040 high scalability-2011-05-13-Stuff The Internet Says On Scalability For May 13, 2011
8 0.092505321 1017 high scalability-2011-04-06-Netflix: Run Consistency Checkers All the time to Fixup Transactions
9 0.089058131 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
10 0.0889882 960 high scalability-2010-12-20-Netflix: Use Less Chatty Protocols in the Cloud - Plus 26 Fixes
12 0.088281974 1506 high scalability-2013-08-23-Stuff The Internet Says On Scalability For August 23, 2013
13 0.087353699 1048 high scalability-2011-05-27-Stuff The Internet Says On Scalability For May 27, 2011
14 0.087332755 1456 high scalability-2013-05-13-The Secret to 10 Million Concurrent Connections -The Kernel is the Problem, Not the Solution
15 0.087315261 924 high scalability-2010-10-21-What is Network-based Application Virtualization and Why Do You Need It?
16 0.086946473 645 high scalability-2009-06-30-Hot New Trend: Linking Clouds Through Cheap IP VPNs Instead of Private Lines
17 0.086664759 1502 high scalability-2013-08-16-Stuff The Internet Says On Scalability For August 16, 2013
18 0.082765147 1435 high scalability-2013-04-04-Paper: A Web of Things Application Architecture - Integrating the Real-World into the Web
19 0.082728602 271 high scalability-2008-03-08-Product: DRBD - Distributed Replicated Block Device
20 0.082557343 446 high scalability-2008-11-18-Scalability Perspectives #2: Van Jacobson – Content-Centric Networking
topicId topicWeight
[(0, 0.15), (1, 0.061), (2, 0.023), (3, 0.024), (4, -0.031), (5, -0.024), (6, 0.021), (7, 0.008), (8, -0.059), (9, 0.026), (10, -0.006), (11, 0.031), (12, -0.021), (13, -0.018), (14, 0.023), (15, 0.05), (16, 0.036), (17, 0.024), (18, -0.024), (19, -0.019), (20, -0.011), (21, 0.051), (22, -0.021), (23, 0.021), (24, 0.011), (25, 0.035), (26, -0.035), (27, -0.021), (28, -0.014), (29, 0.013), (30, -0.001), (31, -0.012), (32, 0.014), (33, 0.025), (34, 0.008), (35, 0.034), (36, 0.001), (37, 0.004), (38, 0.008), (39, 0.047), (40, 0.025), (41, 0.008), (42, -0.007), (43, 0.02), (44, 0.003), (45, 0.041), (46, -0.046), (47, 0.018), (48, -0.106), (49, 0.031)]
simIndex simValue blogId blogTitle
same-blog 1 0.96189433 1256 high scalability-2012-06-04-OpenFlow-SDN is Not a Silver Bullet for Network Scalability
Introduction: Ivan Pepelnjak (CCIE#1354 Emeritus) is Chief Technology Advisor at NIL Data Communications , author of numerous webinars and advanced networking books , and a prolific blogger . He’s focusing on data center and cloud networking, network virtualization, and scalable application design. OpenFlow is an interesting emerging networking technology appearing seemingly out of nowhere with much hype and fanfare in March 2011. More than a year later, there are two commercial products based on OpenFlow ( NEC’s Programmable Flow and Nicira’s Network Virtualization Platform ) and probably less than a dozen production-grade implementations (including Google’s G-Scale network and Indiana University’s campus network ). Is this an expected result for an emerging technology or another case of overhyped technology hitting limits imposed by reality? OpenFlow-based solutions have to overcome numerous problems every emerging technology is facing, in OpenFlow’s case ranging from compatibili
2 0.87365639 446 high scalability-2008-11-18-Scalability Perspectives #2: Van Jacobson – Content-Centric Networking
Introduction: Scalability Perspectives is a series of posts that highlights the ideas that will shape the next decade of IT architecture. Each post is dedicated to a thought leader of the information age and his vision of the future. Be warned though – the journey into the minds and perspectives of these people requires an open mind. Van Jacobson Van Jacobson is a Research Fellow at PARC . Prior to that he was Chief Scientist and co-founder of Packet Design. Prior to that he was Chief Scientist at Cisco. Prior to that he was head of the Network Research group at Lawrence Berkeley National Laboratory. He's been studying networking since 1969. He still hopes that someday something will start to make sense. Scaling the Internet – Does the Net needs an upgrade? As the Internet is being overrun with video traffic, many wonder if it can survive. With challenges being thrown down over the imbalances that have been created and their impact on the viability of monopolistic business models, t
3 0.84255552 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
4 0.81457353 1651 high scalability-2014-05-20-It's Networking. In Space! Or How E.T. Will Phone Home.
Introduction: What will the version of the Internet that follows us to the stars look like? Yes, people are really thinking seriously about this sort of thing. Specifically the InterPlanetary Networking Special Interest Group (IPNSIG). Ansible-like faster-than-light communication it isn't. There's no magical warp drive. Nor is a network of telepaths acting as a 'verse spanning telegraph system. It's more mundane than that. And in many ways more interesting as it's sort of like the old Internet on steroids, the one that was based on on UUCP and dial-up connections, but over vastly longer distances and with much longer delays : The Interplanetary Internet (based on IPN, also called InterPlaNet) is a conceived computer network in space, consisting of a set of network nodes which can communicate with each other.[1][2] Communication would be greatly delayed by the great interplanetary distances, so the IPN needs a new set of protocols and technology that are tolerant to large delays and
5 0.80258399 371 high scalability-2008-08-24-A Scalable, Commodity Data Center Network Architecture
Introduction: Looks interesting... Abstract: Today’s data centers may contain tens of thousands of computers with significant aggregate bandwidth requirements. The network architecture typically consists of a tree of routing and switching elements with progressively more specialized and expensive equipment moving up the network hierarchy. Unfortunately, even when deploying the highest-end IP switches/routers, resulting topologies may only support 50% of the aggregate bandwidth available at the edge of the network, while still incurring tremendous cost. Nonuniform bandwidth among data center nodes complicates application design and limits overall system performance. In this paper, we show how to leverage largely commodity Ethernet switches to support the full aggregate bandwidth of clusters consisting of tens of thousands of elements. Similar to how clusters of commodity computers have largely replaced more specialized SMPs and MPPs, we argue that appropriately architected and interconnected commodi
7 0.77383643 1213 high scalability-2012-03-22-Paper: Revisiting Network I-O APIs: The netmap Framework
8 0.76770502 1316 high scalability-2012-09-04-Changing Architectures: New Datacenter Networks Will Set Your Code and Data Free
10 0.7395587 1051 high scalability-2011-06-01-Why is your network so slow? Your switch should tell you.
11 0.73715758 266 high scalability-2008-03-04-Manage Downtime Risk by Connecting Multiple Data Centers into a Secure Virtual LAN
12 0.72535282 1392 high scalability-2013-01-23-Building Redundant Datacenter Networks is Not For Sissies - Use an Outside WAN Backbone
13 0.72253489 1100 high scalability-2011-08-18-Paper: The Akamai Network - 61,000 servers, 1,000 networks, 70 countries
15 0.71511799 1091 high scalability-2011-08-02-How Will DIDO Wireless Networking Change Everything?
16 0.71469319 645 high scalability-2009-06-30-Hot New Trend: Linking Clouds Through Cheap IP VPNs Instead of Private Lines
17 0.71122479 1157 high scalability-2011-12-14-Virtualization and Cloud Computing is Changing the Network to East-West Routing
18 0.71084881 1526 high scalability-2013-10-02-RFC 1925 - The Twelve (Timeless) Networking Truths
19 0.69966745 374 high scalability-2008-08-30-Paper: GargantuanComputing—GRIDs and P2P
20 0.6896919 1105 high scalability-2011-08-25-The Cloud and The Consumer: The Impact on Bandwidth and Broadband
topicId topicWeight
[(1, 0.107), (2, 0.192), (10, 0.036), (30, 0.032), (40, 0.015), (43, 0.013), (47, 0.011), (56, 0.019), (61, 0.098), (70, 0.117), (77, 0.03), (79, 0.1), (85, 0.047), (93, 0.016), (94, 0.065)]
simIndex simValue blogId blogTitle
same-blog 1 0.95132881 1256 high scalability-2012-06-04-OpenFlow-SDN is Not a Silver Bullet for Network Scalability
Introduction: Ivan Pepelnjak (CCIE#1354 Emeritus) is Chief Technology Advisor at NIL Data Communications , author of numerous webinars and advanced networking books , and a prolific blogger . He’s focusing on data center and cloud networking, network virtualization, and scalable application design. OpenFlow is an interesting emerging networking technology appearing seemingly out of nowhere with much hype and fanfare in March 2011. More than a year later, there are two commercial products based on OpenFlow ( NEC’s Programmable Flow and Nicira’s Network Virtualization Platform ) and probably less than a dozen production-grade implementations (including Google’s G-Scale network and Indiana University’s campus network ). Is this an expected result for an emerging technology or another case of overhyped technology hitting limits imposed by reality? OpenFlow-based solutions have to overcome numerous problems every emerging technology is facing, in OpenFlow’s case ranging from compatibili
2 0.92686588 1127 high scalability-2011-09-28-Pursue robust indefinite scalability with the Movable Feast Machine
Introduction: And now for something completely different, brought to you by David Ackley and Daniel Cannon in their playfully thought provoking paper: Pursue robust indefinite scalability , wherein they try to take a fresh look at neural networks, starting from scratch. What is this strange thing called indefinite scalability ? They sound like words that don't really go together: Indefinite scalability is the property that the design can support open-ended computational growth without substantial re-engineering, in as strict as sense as can be managed. By comparison, many computer, algorithm, and network designs -- even those that address scalability -- are only finitely scalable because their scalability occurs within some finite space. For example, an in-core sorting algorithm for a 32 bit machine can only scale to billions of numbers before address space is exhausted and then that algorithm must be re-engineered. Our idea is to expose indefinitely scalable computational power to program
3 0.92086923 667 high scalability-2009-07-31-NSFW: Hilarious Fault-Tolerance Cartoon
Introduction: Another fun one... Should I be Worried About Scaling? What happens when the comfortable SQL world of yesterday changes out from under you? You feel like this (it uses some language picante so be advised): Here's a link to the source: http://browsertoolkit.com/fault-tolerance.png A great way to communicate the dislocation one feels when technology changes. It also gets you to wonder if those changes at the user level are completely necessary for carrying out the task? Lest you think this just an old guard reactionary sentiment, Boxed Ice chose MongoDB over CouchDB partly because "CouchDB requires map/reduce style queries which is much more complicated to work with." Related Articles It Must be Crap on Relational Dabases Week No to SQL? Anti-database movement gains steam Anti-RDBMS: A list of distributed key-value stores
4 0.92032093 295 high scalability-2008-04-02-Product: Supervisor - Monitor and Control Your Processes
Introduction: It's a sad fact of life, but processes die. I know, it's horrible. You start them, send them out into process space, and hope for the best. Yet sometimes, despite your best coding, they core dump, seg fault, or some other calamity befalls them. Unlike our messy biological world so cruelly ruled by entropy, in the digital world processes can be given another chance. They can be restarted. A greater destiny awaits. And hopefully this time the random lottery of unforeseen killing factors will be avoided and a long productive life will be had by all. This is fun code to write because it's a lot more complicated than you might think. And restarting processes is a highly effective high availability strategy. Most faults are transient, caused by an unexpected series of events. Rather than taking drastic action, like taking a node out of production or failing over, transients can be effectively masked by simply restarting failed processes. Though complexity makes it a fun problem, it's also
5 0.91718549 235 high scalability-2008-02-02-The case against ORM Frameworks in High Scalability Architectures
Introduction: Let me begin by saying that I have used and continue to use various ORM frameworks such as hibernate, ibatis, propel and activerecord in applications and websites that have a user base ranging from a couple hundred to 500k users. Especially for projects that have to be up and running in a short duration of time, ORM frameworks significantly reduce the effort required to manipulate and persist OOP objects by providing time saving facilities such as automatically generated model objects, integrated unit testing, secure variable substitution, etc. Hibernate even supports horizontal data partitioning via Hibernate Shards. However, the lay of the land is significantly different in the rarefied space occupied by applications needing to support millions of users. Profiling an application at this level and paying particular attention to the operations needed to move data to and from the database, it becomes evident that a significant portion of the operations are API related, whereby t
6 0.90720153 803 high scalability-2010-04-05-Intercloud: How Will We Scale Across Multiple Clouds?
7 0.90433288 378 high scalability-2008-09-03-Some Facebook Secrets to Better Operations
8 0.90162355 1389 high scalability-2013-01-18-Stuff The Internet Says On Scalability For January 18, 2013
9 0.90121371 1020 high scalability-2011-04-12-Caching and Processing 2TB Mozilla Crash Reports in memory with Hazelcast
10 0.90093035 1368 high scalability-2012-12-07-Stuff The Internet Says On Scalability For December 7, 2012
11 0.90073317 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
12 0.90035927 1117 high scalability-2011-09-16-Stuff The Internet Says On Scalability For September 16, 2011
13 0.90033627 1637 high scalability-2014-04-25-Stuff The Internet Says On Scalability For April 25th, 2014
15 0.89954352 1228 high scalability-2012-04-16-Instagram Architecture Update: What’s new with Instagram?
16 0.89953977 1233 high scalability-2012-04-25-The Anatomy of Search Technology: blekko’s NoSQL database
17 0.89930236 1428 high scalability-2013-03-22-Stuff The Internet Says On Scalability For March 22, 2013
18 0.89925468 1600 high scalability-2014-02-21-Stuff The Internet Says On Scalability For February 21st, 2014
19 0.8991338 517 high scalability-2009-02-21-Google AppEngine - A Second Look
20 0.89859807 301 high scalability-2008-04-08-Google AppEngine - A First Look