What's a container class?

It's a class which is used to hold objects in memory or external storage to clumping variables of the same type to make the sorting, searching, … easier. A container could store many entities and provide direct access to them like string class.  Needless to say, The size of the container depends on the number of the objects it contains. A Container usually defined as a class that gives you the power to store any type of data. A container class acts as a generic holder.

a container class is in two kinds: Heterogeneous and homo

Just a few hours ago I read some cool stuff about another JS library called Meteor. The story of Meteor doesn't stop on a simple library or framework. There are some claims in documentation of Meteor web site which seems interesting:

  1. Meteor makes it an order of magnitude simpler
  2. You can build a complete application in a weekend via Meteor
  3. No longer do you need to provision server resources
  4. You don’t need to manage database, ORM or broadcast data invalid

I was looking for NoSQL databases in Wikipedia, in Graph databases section I saw an open source data storage written in Dot Net. After exploring the source code I found that it would be so cool. This library seems to be more easier than Neo4J to getting started. I don't know exactly how graph database work and also how BrightstarDB works.

 

BrightstartDB

 

 

In the

Recently I'm tackling with a problem which has some dependencies with SOA architecture. It's where a question about SOA architecture comes out: "Does each service has its own data in SOAs?" After searching on the web I found different answers to this question.  It seems that it depends on conditions!

Suppose if something happen in a point everything in the whole system, the process should be back to the earlier point because each task is independent of the others, right? In this case if every service has its own data, it will be easier to deal with the scena

"In a SOA each functionality is separated as a service. So, a certain application may use many services to provide a defined functionality. The principles of SOA define services as separate platform- and system-independent entities - each capable of functioning on their own, thus providing reusability and interoperability across disparate platforms."

There are various lifetimes of transaction in SOA architecture (Transaction lifetime is the minimum of time that a transaction is kept open).  A transaction could be end in a few second or a couple o