Showing posts from April, 2008

Hadoop Summit and Data-Intensive Computing Symposium Videos and Slides

I couldn't go there; I received official notice from the ministry of defense that I was summoned to a army reserve forces on March 25th.

Sherpa: Cloud computing of the third kind

Raghu (former professor at Madison Wisconsin, now at Yahoo!) is leading a very interesting project on largely scale storage (Sherpa). Here you can find some of my unconnected notes. Software as a service requires to CPU and data. Cloud computing using assimilated to Map-Reduce grids, but they decouple computation and data. For instance Condor is great for high-throughput computing, but on the data side you run into SSDS, Hadoop, etc. But there is a third one, transactional storage. Moreover SQL is the most largely used parallel programming language. Raghu wonder why can’t we build on the lesson learned on RDBMS for OLTP. Sherpa is aiming not to support ACID models, but massively scalable via relaxation. Updates: creation, or simple object updates. Queries: selection with filtering. The vision is to start in a box, if it needs to scale, that should be transparent. PNUTS is part of Sherpa, and it is the technology for: geographic replication, uniform updates, queries, and flexible schem…

SQL Server Data Services (SSDS)

SQL Server Data Services (SSDS) are highly scalable, on-demand data storage and query processing utility services. Built on robust SQL Server database and Windows Server technologies, these services provide high availability, security and support standards-based web interfaces for easy programming and quick provisioning. SSDS homepage :

It's a Highly Scalable web facing data storage. and SSDS data model really takes after google's BigTable.

* Container: Set of entities
* Entity : Flat scalar property bags
* Property name/value pairs

My Identity

I had a very rough time recently, It was a difficult choice for me to leave one thing i loved to go to another thing i loved. However, I learned most important thing. It's really important, I should keep my identity.

Now i'm working hard to make my dream.

Bean ID overlap-addition

I have some problem of bean ID overlap-addition by many developers on one project. If overlap-addition occur, Spring returns the bean which is defined at last without any exceptions. Isn't problematic?

Here's the Q&A page for this issue :