high_scalability high_scalability-2011 high_scalability-2011-1025 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Matt Aslett from the 451 group created a term called “NewSQL ”. On the definition of NewSQL, Aslett writes: “NewSQL” is our shorthand for the various new scalable/high performance SQL database vendors. We have previously referred to these products as ‘ScalableSQL’ to differentiate them from the incumbent relational database products. Since this implies horizontal scalability, which is not necessarily a feature of all the products, we adopted the term ‘NewSQL’ in the new report. And to clarify, like NoSQL, NewSQL is not to be taken too literally: the new thing about the NewSQL vendors is the vendor, not the SQL. As with NoSQL, under the NewSQL umbrella you can see various providers, with various solutions. I think these can be divided into several sub-types: New MySQL storage engines . These give MySQL users the same programming interface, but scale very well. You can Xeround or Akiban in this field. The good part is that you still use MySQL, but on the downside it’s n
sentIndex sentText sentNum sentScore
1 Matt Aslett from the 451 group created a term called “NewSQL ”. [sent-1, score-0.113]
2 On the definition of NewSQL, Aslett writes: “NewSQL” is our shorthand for the various new scalable/high performance SQL database vendors. [sent-2, score-0.464]
3 We have previously referred to these products as ‘ScalableSQL’ to differentiate them from the incumbent relational database products. [sent-3, score-0.5]
4 Since this implies horizontal scalability, which is not necessarily a feature of all the products, we adopted the term ‘NewSQL’ in the new report. [sent-4, score-0.474]
5 And to clarify, like NoSQL, NewSQL is not to be taken too literally: the new thing about the NewSQL vendors is the vendor, not the SQL. [sent-5, score-0.191]
6 As with NoSQL, under the NewSQL umbrella you can see various providers, with various solutions. [sent-6, score-0.25]
7 I think these can be divided into several sub-types: New MySQL storage engines . [sent-7, score-0.083]
8 The good part is that you still use MySQL, but on the downside it’s not supporting other databases (at least not easily) and even MySQL users need to migrate their data to these new databases. [sent-10, score-0.267]
9 These completely new solutions can support your scalability requirements. [sent-12, score-0.21]
10 Of course, some (hopefully minor) changes to the code will be required, and data migration is still needed. [sent-13, score-0.135]
11 ScaleBase , which offers such a solution, lets you get the scalability you need from the database, but instead of rewriting the database, you can use your existing one. [sent-16, score-0.28]
12 This allows you to reuse your existing skill set and eco-system, and you don’t need to rewrite your code or perform any data migration – everything is simple and quick. [sent-17, score-0.452]
13 Other solutions in the field are dbShards for instance. [sent-18, score-0.134]
14 As in NoSQL, I believe each NewSQL solution has its own spot, answering specific needs. [sent-19, score-0.148]
wordName wordTfidf (topN-words)
[('newsql', 0.731), ('aslett', 0.241), ('migration', 0.135), ('shorthand', 0.128), ('xeround', 0.128), ('various', 0.125), ('incumbent', 0.115), ('dbshards', 0.115), ('clarify', 0.115), ('akiban', 0.115), ('term', 0.113), ('mysql', 0.112), ('nosql', 0.105), ('differentiate', 0.098), ('answering', 0.091), ('referred', 0.089), ('minor', 0.086), ('adopted', 0.086), ('skill', 0.085), ('divided', 0.083), ('matt', 0.083), ('reuse', 0.083), ('voltdb', 0.083), ('rewriting', 0.08), ('literally', 0.08), ('existing', 0.079), ('new', 0.076), ('solutions', 0.074), ('implies', 0.074), ('downside', 0.073), ('products', 0.072), ('definition', 0.072), ('rewrite', 0.07), ('vendor', 0.067), ('necessarily', 0.065), ('migrate', 0.065), ('hopefully', 0.064), ('vendors', 0.064), ('spot', 0.063), ('previously', 0.063), ('database', 0.063), ('lets', 0.061), ('providers', 0.061), ('field', 0.06), ('scalability', 0.06), ('horizontal', 0.06), ('solution', 0.057), ('supporting', 0.053), ('taken', 0.051), ('examples', 0.051)]
simIndex simValue blogId blogTitle
same-blog 1 1.0 1025 high scalability-2011-04-16-The NewSQL Market Breakdown
Introduction: Matt Aslett from the 451 group created a term called “NewSQL ”. On the definition of NewSQL, Aslett writes: “NewSQL” is our shorthand for the various new scalable/high performance SQL database vendors. We have previously referred to these products as ‘ScalableSQL’ to differentiate them from the incumbent relational database products. Since this implies horizontal scalability, which is not necessarily a feature of all the products, we adopted the term ‘NewSQL’ in the new report. And to clarify, like NoSQL, NewSQL is not to be taken too literally: the new thing about the NewSQL vendors is the vendor, not the SQL. As with NoSQL, under the NewSQL umbrella you can see various providers, with various solutions. I think these can be divided into several sub-types: New MySQL storage engines . These give MySQL users the same programming interface, but scale very well. You can Xeround or Akiban in this field. The good part is that you still use MySQL, but on the downside it’s n
Introduction: Michael Stonebraker sure knows how to stir up a storm. Unlike for others, that doesn't make him a troll in my mind, he's way too accomplished in the field to be that, but he does have a bit of Barnum & Bailey in him, which serves to get the discussion flowing, and that's a good thing. A lot of previously hidden wisdom and passion unlocks, which we'll try to capture here. This disturbance in the force is over OldSQL vs NoSQL vs NewSQL . Warning, these are not crisp categories, there's leakage all over the place, watch your step: OldSQL (Oracle, MySQL, etc) refers to what some want to term as legacy relational database like MySQL, that don't scale out horizontally with aplomb. NoSQL (CouchDB, Redis, Cassandra, HBase, MongoDB, Riak, Neo4j, etc) refers to, well, a collection of technologies that aren't OldSQL, these often are designed to scale out horizontally, aren't on ACID, and use schemaless non-relational datamodels. NewSQL (Xeround, Clustrix, NimbusDB, GenieDB, Sc
3 0.13123015 847 high scalability-2010-06-23-Product: dbShards - Share Nothing. Shard Everything.
Introduction: I met the CodeFutures folks, makers of dbShards , at Gluecon . They occupy an interesting niche in the database space, somewhere between NoSQL , which jettisons everything SQL, and high end analytics platforms that completely rewrite the backend while keeping a SQL facade. High concept: I think of dbShards as a sort of commercial OLTP mashup of features from HSCALE (partitioning) + MySQL Proxy (transparent intermediate layer) + Memcached (client side sharding) + Gigaspaces (parallel query) + MySQL (transactions). You may find dbShards interesting if you are looking to keep SQL, need scale out writes and reads, need out of the box parallel query capabilities, and would prefer to use a standard platform like MySQL as a base. To learn more about dbShards I asked Cory Isaacson (CEO and CTO) a few devastatingly difficult questions (not really). Who are you, what is dbShards, and what problem was dbShards created to solve? I’m Cory Isaacson, CEO/CTO of CodeFutures Corp
4 0.11955539 1092 high scalability-2011-08-04-Jim Starkey is Creating a Brave New World by Rethinking Databases for the Cloud
Introduction: Jim Starkey , founder of NuoDB , in this thread on the Cloud Computing group, delivers a masterful post on why he thinks the relational model is the best overall compromise amongst the different options, why NewSQL can free itself from the limitations of legacy SQL architectures, and how this creates a brave new lock free world.... I'll [Jim Starkey] go into more detail later in the post for those who care, but the executive summary goes like this: Network latency is relatively high and human attention span is relatively low. So human facing computer systems have to perform their work in a small number of trips between the client and the database server. But the human condition leads inexorably to data complexity. There are really only two strategies to manage this problem. One is to use coarse granularity storage, glombing together related data into a single blob and letting intelligence on the client make sense of it. The other is storing fine granularity data on the s
5 0.11788496 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
Introduction: It's a truism that we should choose the right tool for the job . Everyone says that. And who can disagree? The problem is this is not helpful advice without being able to answer more specific questions like: What jobs are the tools good at? Will they work on jobs like mine? Is it worth the risk to try something new when all my people know something else and we have a deadline to meet? How can I make all the tools work together? In the NoSQL space this kind of real-world data is still a bit vague. When asked, vendors tend to give very general answers like NoSQL is good for BigData or key-value access. What does that mean for for the developer in the trenches faced with the task of solving a specific problem and there are a dozen confusing choices and no obvious winner? Not a lot. It's often hard to take that next step and imagine how their specific problems could be solved in a way that's worth taking the trouble and risk. Let's change that. What problems are you using NoSQL to sol
6 0.11510958 857 high scalability-2010-07-13-DbShards Part Deux - The Internals
8 0.10508935 931 high scalability-2010-10-28-Notes from A NOSQL Evening in Palo Alto
9 0.097329497 1080 high scalability-2011-07-15-Stuff The Internet Says On Scalability For July 15, 2011
10 0.085751519 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
11 0.08371976 1529 high scalability-2013-10-08-F1 and Spanner Holistically Compared
12 0.079570353 1345 high scalability-2012-10-22-Spanner - It's About Programmers Building Apps Using SQL Semantics at NoSQL Scale
13 0.075647458 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
14 0.072829485 891 high scalability-2010-09-01-Scale-out vs Scale-up
15 0.072341964 1649 high scalability-2014-05-16-Stuff The Internet Says On Scalability For May 16th, 2014
16 0.070881933 196 high scalability-2007-12-30-MySQL clustering strategies and comparisions
17 0.069351912 935 high scalability-2010-11-05-Hot Scalability Links For November 5th, 2010
18 0.068133526 858 high scalability-2010-07-13-Sponsored Post: VoltDB and Digg are Hiring
19 0.067705959 739 high scalability-2009-11-09-10 NoSQL Systems Reviewed
20 0.067665309 1054 high scalability-2011-06-06-NoSQL Pain? Learn How to Read-write Scale Without a Complete Re-write
topicId topicWeight
[(0, 0.109), (1, 0.036), (2, -0.007), (3, 0.007), (4, 0.041), (5, 0.09), (6, -0.072), (7, -0.083), (8, 0.02), (9, -0.043), (10, -0.024), (11, 0.005), (12, -0.027), (13, 0.036), (14, 0.019), (15, -0.008), (16, 0.023), (17, -0.015), (18, -0.042), (19, -0.008), (20, 0.02), (21, -0.01), (22, -0.005), (23, -0.02), (24, 0.075), (25, 0.041), (26, -0.03), (27, -0.032), (28, -0.001), (29, -0.024), (30, -0.0), (31, 0.042), (32, -0.018), (33, 0.009), (34, 0.007), (35, -0.004), (36, -0.034), (37, -0.013), (38, -0.011), (39, 0.001), (40, 0.042), (41, -0.001), (42, 0.014), (43, -0.014), (44, -0.008), (45, -0.008), (46, 0.027), (47, 0.012), (48, -0.023), (49, 0.017)]
simIndex simValue blogId blogTitle
same-blog 1 0.95251751 1025 high scalability-2011-04-16-The NewSQL Market Breakdown
Introduction: Matt Aslett from the 451 group created a term called “NewSQL ”. On the definition of NewSQL, Aslett writes: “NewSQL” is our shorthand for the various new scalable/high performance SQL database vendors. We have previously referred to these products as ‘ScalableSQL’ to differentiate them from the incumbent relational database products. Since this implies horizontal scalability, which is not necessarily a feature of all the products, we adopted the term ‘NewSQL’ in the new report. And to clarify, like NoSQL, NewSQL is not to be taken too literally: the new thing about the NewSQL vendors is the vendor, not the SQL. As with NoSQL, under the NewSQL umbrella you can see various providers, with various solutions. I think these can be divided into several sub-types: New MySQL storage engines . These give MySQL users the same programming interface, but scale very well. You can Xeround or Akiban in this field. The good part is that you still use MySQL, but on the downside it’s n
2 0.80680549 770 high scalability-2010-02-03-NoSQL Means Never Having to Store Blobs Again
Introduction: Morgan Tocker has an awesome article and comment thread in the MySQL Performance Blog about When should you store serialized objects in the database? Before the NoSQL age is was very common to simulate schemalessness by storing blobs in MySQL. Sharding was implemented by running multiple MySQL instances and spreading writes across them. While not ideal for the purpose, developers felt comfortable with MySQL. They knew how to install it, back it up, replicate it, in short:Â they knew how to make it work. Yet they also needed to store objects without the penalty of joins. Searches and aggregate queries were handled by indexes kept in separate tables, this offloaded the fast path to objects. This all made perfect sense. Usually we just want stuff to work and going with what you know is often the best path to that goal. And what we have known is MySQL. All the different pros and cons of this approach are covered wonderfully in the post. But the world has changed. With the same goal
3 0.7980336 867 high scalability-2010-07-27-YeSQL: An Overview of the Various Query Semantics in the Post Only-SQL World
Introduction: The NoSQL movement faults the SQL query language as the source of many of the scalability issues that we face today with traditional database approach. I think that the main reason so many people have come to see SQL as the source of all evil is the fact that, traditionally, the query language was burned into the database implementation. So by saying NoSQL you basically say "No" to the traditional non-scalable RDBMS implementations. This view has brought on a flood of alternative query languages, each aiming to solve a different aspect that is missing in the traditional SQL query approach, such as a document model, or that provides a simpler approach, such as Key/Value query. Most of the people I speak with seem fairly confused on this subject, and tend to use query semantics and architecture interchangeably. In Part I of this post i tried to provide quick overview of what each query term stands for in the context of the NoSQL world . Part II illustrates those ide
4 0.78489292 885 high scalability-2010-08-23-Building a Scalable Key-Value Database: Project Hydracus
Introduction: The world of NoSQL and alternative database implementations (i.e. non-relational) is deeply fascinating to me. I can’t help but be swept up in the whirl of planet-scale web development scalability techniques and the evolution of how developers think about building their applications knowing that with success comes the inevitable need to scale to levels almost unimaginable just five or ten years ago. I’m going to make a prediction: Developers will be expected to understand the fundamentals of how different database systems can be applied within a singular application; their strengths and weaknesses, and when it is appropriate to leverage them. There’s a lot out there about scaling relational databases. Partitioning your data over application-managed shards is a topic that has seen its fair share of attention. But I think there’s a whole slew over NoSQL databases that have been built and designed by some very smart people that are new enough that their internals aren’t we
5 0.78181911 793 high scalability-2010-03-10-Saying Yes to NoSQL; Going Steady with Cassandra at Digg
Introduction: The last six months have been exciting for Digg's engineering team. We're working on a soup-to-nuts rewrite. Not only are we rewriting all our application code, but we're also rolling out a new client and server architecture. And if that doesn't sound like a big enough challenge, we're replacing most of our infrastructure components and moving away from LAMP. Perhaps our most significant infrastructure change is abandoning MySQL in favor of a NoSQL alternative. To someone like me who's been building systems almost exclusively on relational databases for almost 20 years, this feels like a bold move. What's Wrong with MySQL? Our primary motivation for moving away from MySQL is the increasing difficulty of building a high performance, write intensive, application on a data set that is growing quickly, with no end in sight. This growth has forced us into horizontal and vertical partitioning strategies that have eliminated most of the value of a relational database, while still incurr
6 0.77512592 648 high scalability-2009-07-02-It Must be Crap on Relational Dabases Week
7 0.75396872 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
8 0.75293332 785 high scalability-2010-02-26-MySQL and Memcached: End of an Era?
9 0.7511003 935 high scalability-2010-11-05-Hot Scalability Links For November 5th, 2010
10 0.75072199 670 high scalability-2009-08-05-Anti-RDBMS: A list of distributed key-value stores
11 0.74613279 931 high scalability-2010-10-28-Notes from A NOSQL Evening in Palo Alto
12 0.73910809 1054 high scalability-2011-06-06-NoSQL Pain? Learn How to Read-write Scale Without a Complete Re-write
14 0.73233449 849 high scalability-2010-06-28-VoltDB Decapitates Six SQL Urban Myths and Delivers Internet Scale OLTP in the Process
15 0.72427249 779 high scalability-2010-02-16-Seven Signs You May Need a NoSQL Database
16 0.71529341 872 high scalability-2010-08-05-Pairing NoSQL and Relational Data Storage: MySQL with MongoDB
17 0.71416724 995 high scalability-2011-02-24-Strategy: Eliminate Unnecessary SQL
18 0.70130074 930 high scalability-2010-10-28-NoSQL Took Away the Relational Model and Gave Nothing Back
20 0.69897634 607 high scalability-2009-05-26-Database Optimize patterns
topicId topicWeight
[(1, 0.067), (2, 0.153), (61, 0.068), (79, 0.129), (94, 0.456)]
simIndex simValue blogId blogTitle
1 0.97082162 1601 high scalability-2014-02-25-Peter Norvig's 9 Master Steps to Improving a Program
Introduction: Inspired by a xkcd comic , Peter Norvig , Director of Research at Google and all around interesting and nice guy, has created an above par code kata involving a regex program that demonstrates the core inner loop of many successful systems profiled on HighScalability. The original code is at xkcd 1313: Regex Golf , which comes up with an algorithm to find a short regex that matches the winners and not the losers from two arbitrary lists. The Python code is readable, the process is TDDish, and the problem, which sounds simple, but soon explodes into regex weirdness, as does most regex code. If you find regular expressions confusing you'll definitely benefit from Peter's deliberate strategy for finding a regex. The post demonstrating the iterated improvement of the program is at xkcd 1313: Regex Golf (Part 2: Infinite Problems) . As with most first solutions it wasn't optimal. To improve the program Peter recommends the following steps: Profiling : Figure out wher
2 0.96171069 605 high scalability-2009-05-22-Distributed content system with bandwidth balancing
Introduction: I am looking for a way to distribute files over servers in different physical locations. My main concern is that I have bandwidth limitations on each location, and wish to spread the bandwidth load evenly. Atm. I just have 1:1 copies of the files on all servers, and have the application pick a random server to serve the file as a temp fix... It's a small video streaming service. I want to spoonfeed the stream to the client with a max bandwidth output, and support seek. At present I use php to limit the network stream, and read the file at a given offset sendt as a get parameter from the player for seek. It's psuedo streaming, but it works. I have been looking at MogileFS, which would solve the storage part. With MogileFS I can make use of my current php solution as it supports lighttpd and apache (with mod_rewrite or similar). However I don't see how I can apply MogileFS to check for bandwidth % usage? Any reccomendations for how I can solve this?
3 0.95421231 559 high scalability-2009-04-07-Six Lessons Learned Deploying a Large-scale Infrastructure in Amazon EC2
Introduction: Lessons learned from OpenX's large-scale deployment to Amazon EC2: Expect failures; what's more, embrace them Fully automate your infrastructure deployments Design your infrastructure so that it scales horizontally Establish clear measurable goals Be prepared to quickly identify and eliminate bottlenecks Play wack-a-mole for a while, until things get stable
4 0.94705176 115 high scalability-2007-10-07-Using ThreadLocal to pass context information around in web applications
Introduction: Hi, In java web servers, each http request is handled by a thread in thread pool. So for a Servlet handling the request, a thread is assigned. It is tempting (and very convinient) to keep context information in the threadlocal variable. I recently had a requirement where we need to assign logged in user id and timestamp to request sent to web services. Because we already had the code in place, it was extremely difficult to change the method signatures to pass user id everywhere. The solution I thought is class ReferenceIdGenerator { public static setReferenceId(String login) { threadLocal.set(login + System.currentMillis()); } public static String getReferenceId() { return threadLocal.get(); } private static ThreadLocal threadLocal = new ThreadLocal(); } class MySevlet { void service(.....) { HttpSession session = request.getSession(false); String userId = session.get("userId"); ReferenceIdGenerator.setRefernceId(userId
Introduction: The reference configurations described in this blueprint are starting points for building Sun Customer Ready HPC Clusters configured with Sun Fire X2100 M2 and X2200 M2 servers. The configurations define how Sun Systems Group products can be configured in a typical grid rack deployment. This document describes configurations in detail using Sun Fire X2100 M2 and X2200 M2 servers with a Gigabit Ethernet data fabric, as well as configurations using Sun Fire X2200 M2 servers with a high-speed InfiniBand fabric. These configurations focus on single rack solutions, with external connections through uplink ports of the switches. These reference configurations have been architected using Sun's expertise gained in actual, real-world installations. Within certain constraints, as described in the later sections, the system can be tailored to the customer needs. Certain system components described in this document are only available through Sun's factory integration. Although the information
6 0.91392469 1305 high scalability-2012-08-16-Paper: A Provably Correct Scalable Concurrent Skip List
8 0.88350338 91 high scalability-2007-09-13-Design Preparations for Scaling
9 0.86135197 834 high scalability-2010-06-01-Web Speed Can Push You Off of Google Search Rankings! What Can You Do?
same-blog 10 0.85571378 1025 high scalability-2011-04-16-The NewSQL Market Breakdown
11 0.84271413 1223 high scalability-2012-04-06-Stuff The Internet Says On Scalability For April 6, 2012
12 0.82909065 1412 high scalability-2013-02-25-SongPop Scales to 1 Million Active Users on GAE, Showing PaaS is not Passé
13 0.82526082 970 high scalability-2011-01-06-BankSimple Mini-Architecture - Using a Next Generation Toolchain
14 0.81729639 1084 high scalability-2011-07-22-Stuff The Internet Says On Scalability For July 22, 2011
15 0.80631208 78 high scalability-2007-09-01-2 tier switch selection for colocation
16 0.79814023 241 high scalability-2008-02-05-SLA monitoring
17 0.79682887 1023 high scalability-2011-04-14-Strategy: Cache Application Start State to Reduce Spin-up Times
18 0.79573071 827 high scalability-2010-05-14-Hot Scalability Links for May 14, 2010
19 0.79140353 266 high scalability-2008-03-04-Manage Downtime Risk by Connecting Multiple Data Centers into a Secure Virtual LAN
20 0.79007095 863 high scalability-2010-07-22-How can we spark the movement of research out of the Ivory Tower and into production?