Sunday, September 6, 2009 at 11:34PM Key-Value System Benchmarks
Articles
Presentation
Random
Thursday, September 3, 2009 at 9:18PM The High Scalable Systems (i.e. Websites) such as: Google, Facebook, Amazon, etc. need high scalable storage system that can deal with huge amount of data with high availability and reliability. Building large systems on top of a traditional RDBMS data storage layer is no longer good enough. This presentation explores the landscape of new technologies available today to augment your data layer to improve performance and reliability.
Remember: All of my presentations contents is open source, please feel free to use it, copy it, and re-distribute it as you want.
Download the presentation
Friday, July 17, 2009 at 3:18AM First let's describe what means by odds: In my social network, I found 93% of the mainstream developers sanctify the database, or at least consider it in any data persistence challenge as the ultimate, superhero, and undefeatable solution.
I think this problem come from the education, personally, and some companies also I think it's involved in this.
To start to fix this bad thinking, we all should agree in the following points:
I hope if you agreed with me in the previous points. So the question do we really need Database in every application?
There are many scenario shouldn't use Database resisters, such as: Web search engine, Caching, File sharing system, DNS system, etc. In the other hand there many of scenarios should use Database, such as: Customer database, Address book, ERP, etc.
Tiny URL services for example, shouldn't use Database at all because it's require very simple needs, just map a small/tiny URL to the real/big URL. If you start agreed with me, you likely want ask: But what we can use beside or instead of Databases?
There are a lot of tools that fallowing CAP, BASE model, instead of ACID model. But first let's describe ACID:
In other hand CAP model is about:
For example in any in-memory or in-disk caching system you will never need all the Database features. You just need CAP like system. Today there are a lot of: column oriented, and key-value oriented systems. But first let's describe Column oriented:
A column-oriented is a database management system (DBMS) which stores its content by column rather than by row. This has advantages for databases such as data warehouses and library catalogues, where aggregates are computed over large numbers of similar data items. This approach is contrasted with row-oriented databases and with correlation databases, which use a value-based storage structure. For more information check Wikipedia page.
Distributed key-value stores:
Distributed column stores (Bigtable-like systems):
Something a little different:
Resource:
Wednesday, July 8, 2009 at 11:19PM There are a lot of questions about how the server components, and how to build perfect server with consider the power consumption. Today I will discuss the Server components, and how we can choice better server components with consider the power consumption, efficacy, performance, and price.
Key points:
Wednesday, July 8, 2009 at 11:12PM This presentation about parallel computing, and it’s discover the following topic:
Note: All of my presentation is open source, so feel free to copy it, use it, and re-distribute it.
Download
Sunday, May 31, 2009 at 3:42PM What is the parallel Computing ? and what the different between Multi-Threading and Concurrency and Parallelism ? and what is differences between task and data parallel ? and how we can use it ?
Fundamental article into Parallel Programming...
Wednesday, May 27, 2009 at 6:53PM Tuesday, May 26, 2009 at 1:17AM Wednesday, May 6, 2009 at 8:24PM Wednesday, April 29, 2009 at 7:07PM There are a lot of questions about the server components, and how to choice and/or build perfect server with consider the power consumption. So I decide to write about this topic.
Key Points:
