high_scalability high_scalability-2010 high_scalability-2010-782 knowledge-graph by maker-knowledge-mining

782 high scalability-2010-02-23-When to migrate your database?


meta infos for this blog

Source: html

Introduction: Why migrate your database? Efficiency and availability problems are harming your business – reports are out of date, your batch processing window is nearing its limits, outages (unplanned/planned) frequently halt work. Database consolidation – remove the costs that result from a heterogeneous database environment (DBAs time, database vendor pricing, database versions, hardware, OSs, patches, upgrades etc.). OK, so the driving forces for migration are clear,  what now? Read more on BigDataMatters.com


Summary: the most important sentenses genereted by tfidf model

sentIndex sentText sentNum sentScore

1 Efficiency and availability problems are harming your business – reports are out of date, your batch processing window is nearing its limits, outages (unplanned/planned) frequently halt work. [sent-2, score-1.915]

2 Database consolidation – remove the costs that result from a heterogeneous database environment (DBAs time, database vendor pricing, database versions, hardware, OSs, patches, upgrades etc. [sent-3, score-1.661]

3 OK, so the driving forces for migration are clear,  what now? [sent-5, score-0.47]


similar blogs computed by tfidf model

tfidf for this blog:

wordName wordTfidf (topN-words)

[('harming', 0.3), ('nearing', 0.3), ('halt', 0.281), ('oss', 0.281), ('patches', 0.216), ('consolidation', 0.213), ('dbas', 0.213), ('heterogeneous', 0.191), ('database', 0.183), ('outages', 0.182), ('window', 0.168), ('upgrades', 0.167), ('date', 0.161), ('migration', 0.157), ('driving', 0.157), ('forces', 0.156), ('vendor', 0.155), ('ok', 0.153), ('migrate', 0.151), ('reports', 0.142), ('versions', 0.142), ('frequently', 0.14), ('efficiency', 0.14), ('remove', 0.128), ('limits', 0.125), ('batch', 0.121), ('pricing', 0.1), ('clear', 0.097), ('environment', 0.092), ('result', 0.09), ('processing', 0.077), ('costs', 0.076), ('business', 0.074), ('availability', 0.073), ('hardware', 0.065), ('problems', 0.057), ('read', 0.055), ('time', 0.03)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 1.0 782 high scalability-2010-02-23-When to migrate your database?

Introduction: Why migrate your database? Efficiency and availability problems are harming your business – reports are out of date, your batch processing window is nearing its limits, outages (unplanned/planned) frequently halt work. Database consolidation – remove the costs that result from a heterogeneous database environment (DBAs time, database vendor pricing, database versions, hardware, OSs, patches, upgrades etc.). OK, so the driving forces for migration are clear,  what now? Read more on BigDataMatters.com

2 0.10001524 1313 high scalability-2012-08-28-Making Hadoop Run Faster

Introduction: Making Hadoop Run Faster One of the challenges in processing data is that the speed at which we can input data is quite often much faster than the speed at which we can process it. This problem becomes even more pronounced in the context of Big Data, where the volume of data keeps on growing, along with a corresponding need for more insights, and thus the need for more complex processing also increases. Batch Processing to the Rescue Hadoop was designed to deal with this challenge in the following ways: 1. Use a distributed file system: This enables us to spread the load and grow our system as needed. 2. Optimize for write speed: To enable fast writes the Hadoop architecture was designed so that writes are first logged, and then processed. This enables fairly fast write speeds. 3. Use batch processing (Map/Reduce) to balance the speed for the data feeds with the processing speed. Batch Processing Challenges The challenge with batch-processing is that it assumes

3 0.090517193 557 high scalability-2009-04-06-A picture is realy worth a thousand word, and also a window in time...

Introduction: Photograpic picture to me is window, an address to that specific moment what do your think about that?

4 0.080349132 500 high scalability-2009-01-22-Heterogeneous vs. Homogeneous System Architectures

Introduction: I follow a certain philosophy when developing system architectures. I assume that very few systems will ever exist in a consistent form for more than a short period of time. What constitutes a “short period of time” differs depending on the specifics of each system, but in an effort to quantify it, I generally find that it falls somewhere between a week and a month. The driving forces behind the need for an ever changing architecture are largely business requirement based. This is a side effect of the reality that software development, in most cases, is used as a supporting role within the business unit it serves. As business requirements (i.e. additional features, new products, etc.) pour forth, it is the developer’s job to evolve their software system to accommodate these requirements and provide a software based solution to whatever problems lay ahead. Given that many businesses can be identified as having the above characteristics, I can now begin to explain why I believe t

5 0.080103025 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

6 0.079519615 822 high scalability-2010-05-04-Business continuity with real-time data integration

7 0.0761097 894 high scalability-2010-09-03-Six guiding principles to Consolidate your IT

8 0.075694352 458 high scalability-2008-12-01-Web Consolidation on the Sun Fire T1000 using Solaris Containers

9 0.069332086 544 high scalability-2009-03-18-QCon London 2009: Upgrading Twitter without service disruptions

10 0.069267876 627 high scalability-2009-06-11-Yahoo! Distribution of Hadoop

11 0.06857685 304 high scalability-2008-04-19-How to build a real-time analytics system?

12 0.067565888 813 high scalability-2010-04-19-The cost of High Availability (HA) with Oracle

13 0.066137597 208 high scalability-2008-01-11-FTP Sanity: Redundancy, archiving, consolidation.

14 0.06414929 247 high scalability-2008-02-12-We want to cache a lot :) How do we go about it ?

15 0.063738048 1568 high scalability-2013-12-23-What Happens While Your Brain Sleeps is Surprisingly Like How Computers Stay Sane

16 0.058887362 1020 high scalability-2011-04-12-Caching and Processing 2TB Mozilla Crash Reports in memory with Hazelcast

17 0.057335611 576 high scalability-2009-04-21-What CDN would you recommend?

18 0.054120686 1077 high scalability-2011-07-11-ATMCash Exploits Virtualization for Security - Immutability and Reversion

19 0.053526282 151 high scalability-2007-11-12-a8cjdbc - Database Clustering via JDBC

20 0.052697685 1025 high scalability-2011-04-16-The NewSQL Market Breakdown


similar blogs computed by lsi model

lsi for this blog:

topicId topicWeight

[(0, 0.068), (1, 0.025), (2, -0.007), (3, -0.012), (4, -0.008), (5, 0.029), (6, 0.005), (7, -0.043), (8, 0.007), (9, -0.027), (10, 0.001), (11, 0.007), (12, -0.005), (13, 0.011), (14, 0.028), (15, -0.006), (16, 0.002), (17, -0.004), (18, -0.005), (19, 0.021), (20, -0.004), (21, 0.012), (22, 0.012), (23, -0.024), (24, 0.011), (25, 0.006), (26, -0.014), (27, -0.02), (28, 0.018), (29, 0.042), (30, -0.005), (31, 0.029), (32, 0.006), (33, 0.013), (34, -0.038), (35, 0.039), (36, -0.037), (37, 0.034), (38, 0.055), (39, 0.011), (40, 0.006), (41, -0.007), (42, -0.03), (43, 0.032), (44, 0.029), (45, -0.037), (46, -0.002), (47, -0.013), (48, -0.0), (49, 0.03)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.89541525 782 high scalability-2010-02-23-When to migrate your database?

Introduction: Why migrate your database? Efficiency and availability problems are harming your business – reports are out of date, your batch processing window is nearing its limits, outages (unplanned/planned) frequently halt work. Database consolidation – remove the costs that result from a heterogeneous database environment (DBAs time, database vendor pricing, database versions, hardware, OSs, patches, upgrades etc.). OK, so the driving forces for migration are clear,  what now? Read more on BigDataMatters.com

2 0.72616589 151 high scalability-2007-11-12-a8cjdbc - Database Clustering via JDBC

Introduction: Practically any software project nowadays could not survive without a database (DBMS) backend storing all the business data that is vital to you and/or your customers. When projects grow larger, the amount of data usually grows larger exponentially. So you start moving the DBMS to a separate server to gain more speed and capacity. Which is all good and healthy but you do not gain any extra safety for this business data. You might be backing up your database once a day so in case the database server crashes you don't lose EVERYTHING, but how much can you really afford to lose?  Well clearly this depends on what kind of data you are storing. In our case the users of our solutions use our software products to do their everyday (all day) work. They have "everything" they need for their business stored in the database we are providing. So is 24 hours of data loss acceptable? No, not really. One hour? Maybe. But what we really want is a second database running with the EXACT same data. We

3 0.68584782 698 high scalability-2009-09-10-Building Scalable Databases: Denormalization, the NoSQL Movement and Digg

Introduction: Database normalization is a technique for designing relational database schemas that ensures that the data is optimal for ad-hoc querying and that modifications such as deletion or insertion of data does not lead to data inconsistency. Database denormalization is the process of optimizing your database for reads by creating redundant data. A consequence of denormalization is that insertions or deletions could cause data inconsistency if not uniformly applied to all redundant copies of the data within the database. Read more on Carnage4life blog...

4 0.66280264 813 high scalability-2010-04-19-The cost of High Availability (HA) with Oracle

Introduction: What's the cost of downtime to your business?  $100,000 per hour, $1,000,000 or more? The recent Volcanic ash that has grounded European flights is estimated to be costing the airlines $200M a day. In the IT world, High Availability (HA) architectures allow for disaster recovery as well as uninterrupted business continuity during system failure. This post focuses on a customer’s backend, comprised of a business application stack supported by a dozen Oracle databases. They wish to equip this infrastructure with HA features and ensure that outages do not cost business. How do we address the challenge of pricing the complete solution, with hardware, software, services and annual support? Read more on BigDataMatters.com

5 0.6608867 65 high scalability-2007-08-16-Scaling Secret #2: Denormalizing Your Way to Speed and Profit

Introduction: Alan Watts once observed how after we accepted Descartes' separation of the mind and body we've been trying to smash them back together again ever since when really they were never separate to begin with. The database normalization-denormalization dualism has the same mobius shaped reverberations as Descartes' error. We separate data into a million jagged little pieces and then spend all our time stooping over, picking them and up, and joining them back together again. Normalization has been standard practice now for decades. But times are changing. Many mega-website architects are concluding Watts was right: the data was never separate to begin with. And even more radical, we may even need to store multiple copies of data. Information Sources Normalization Is for Sissies by Pat Helland Data normalization, is it really that good? by Arnon Rotem-Gal-Oz When Not to Normalize your SQL Database by Dare Obasanjo MegaData by Joe Gregorio Audio

6 0.65943813 1110 high scalability-2011-09-06-Big Data Application Platform

7 0.65753078 351 high scalability-2008-07-16-The Mother of All Database Normalization Debates on Coding Horror

8 0.64842135 1276 high scalability-2012-07-04-Top Features of a Scalable Database

9 0.63486564 733 high scalability-2009-10-29-Paper: No Relation: The Mixed Blessings of Non-Relational Databases

10 0.62622714 537 high scalability-2009-03-12-QCon London 2009: Database projects to watch closely

11 0.62205905 607 high scalability-2009-05-26-Database Optimize patterns

12 0.62182856 822 high scalability-2010-05-04-Business continuity with real-time data integration

13 0.61265624 671 high scalability-2009-08-05-Stack Overflow Architecture

14 0.61019963 250 high scalability-2008-02-17-Web Accelerators - snake oil or miracle remedy?

15 0.60859966 235 high scalability-2008-02-02-The case against ORM Frameworks in High Scalability Architectures

16 0.60403579 1553 high scalability-2013-11-25-How To Make an Infinitely Scalable Relational Database Management System (RDBMS)

17 0.60384858 398 high scalability-2008-09-30-Scalability Worst Practices

18 0.60324502 1546 high scalability-2013-11-11-Ask HS: What is a good OLAP database choice with node.js?

19 0.60157132 137 high scalability-2007-10-30-Database parallelism choices greatly impact scalability

20 0.60144424 809 high scalability-2010-04-13-Strategy: Saving Your Butt With Deferred Deletes


similar blogs computed by lda model

lda for this blog:

topicId topicWeight

[(2, 0.033), (79, 0.819)]

similar blogs list:

simIndex simValue blogId blogTitle

1 0.99919802 692 high scalability-2009-09-01-Cheap storage: how backblaze takes matters in hand

Introduction: Blackblaze blogs about how they built their own storage infrastructure on the cheap to run their cloud backup service. This episode: the hardware. Sorry, just a link this time.

2 0.99919802 1119 high scalability-2011-09-20-HighScalability is old news. Step your scaling game way up... (NSFW cartoon)

Introduction: Jeremy Raines tweeted a link to this cartoon  my new filing technique is unstoppable , showing how scotch tape can be used to create a new super-database. Very funny in a Dilbert sort of way, but definitely not NSFW...   For more on Twisted Tuesday, you may enjoy: Hilarious Video: Relational Database Vs NoSQL Fanbois NSFW: Hilarious Fault-Tolerance Cartoon

3 0.98927164 8 high scalability-2007-07-12-Should I use LAMP or Windows?

Introduction: Hi, I stumb l ed on your s i te and I am th i nking about start i ng a website. I haven't rece i ved a good answer about what I shou l d use to bui l d i t, so I thought I wou l d give it a shot. I am a w i ndows guy. I know .Net and ASP and how to bu i ld web s i tes using that stack. But I not i ce most sites use LAMP and that's what most people ta l k about using. What's wrong w i th using Windows? .Net Programmer

4 0.98900145 743 high scalability-2009-11-23-Big Data on Grids or on Clouds?

Introduction: Contributed by Wolfgang Gentzsch: Now that we have a new computing paradigm, Cloud Computing, how can Clouds help our data? Replace our internal data vaults as we hoped Grids would? Are Grids dead now that we have Clouds? Despite all the promising developments in the Grid and Cloud computing space, and the avalanche of publications and talks on this subject, many people still seem to be confused about internal data and compute resources, versus Grids versus Clouds, and they are hesitant to take the next step. I think there are a number of issues driving this uncertainty. read more at: BigDataMatters.com

same-blog 5 0.98210675 782 high scalability-2010-02-23-When to migrate your database?

Introduction: Why migrate your database? Efficiency and availability problems are harming your business – reports are out of date, your batch processing window is nearing its limits, outages (unplanned/planned) frequently halt work. Database consolidation – remove the costs that result from a heterogeneous database environment (DBAs time, database vendor pricing, database versions, hardware, OSs, patches, upgrades etc.). OK, so the driving forces for migration are clear,  what now? Read more on BigDataMatters.com

6 0.98096967 443 high scalability-2008-11-14-Paper: Pig Latin: A Not-So-Foreign Language for Data Processing

7 0.97326803 401 high scalability-2008-10-04-Is MapReduce going mainstream?

8 0.95908272 372 high scalability-2008-08-27-Updating distributed web applications

9 0.955172 107 high scalability-2007-10-02-Some Real Financial Numbers for Your Startup

10 0.94110709 1100 high scalability-2011-08-18-Paper: The Akamai Network - 61,000 servers, 1,000 networks, 70 countries

11 0.91770476 1169 high scalability-2012-01-05-Shutterfly Saw a Speedup of 500% With Flashcache

12 0.91436565 1277 high scalability-2012-07-05-10 Golden Principles For Building Successful Mobile-Web Applications

13 0.8960889 323 high scalability-2008-05-19-Twitter as a scalability case study

14 0.88544327 784 high scalability-2010-02-25-Paper: High Performance Scalable Data Stores

15 0.84486055 75 high scalability-2007-08-28-Google Utilities : An online google guide,tools and Utilities.

16 0.83430934 871 high scalability-2010-08-04-Dremel: Interactive Analysis of Web-Scale Datasets - Data as a Programming Paradigm

17 0.8230722 1162 high scalability-2011-12-23-Funny: A Cautionary Tale About Storage and Backup

18 0.79974854 1403 high scalability-2013-02-08-Stuff The Internet Says On Scalability For February 8, 2013

19 0.79522729 680 high scalability-2009-08-13-Reconnoiter - Large-Scale Trending and Fault-Detection

20 0.79459691 1181 high scalability-2012-01-25-Google Goes MoreSQL with Tenzing - SQL Over MapReduce