Interesting article and discussion btw :-) Including this new Data Model is a clear and great enhancement to the product imho. I wonder if performance considerations are being taking into account in design and implementation decisions. Are there any numbers about it? How do we compare with our own SQL over relational structures? How do we compare against competitors?

That's great! All major companies have twitter accounts even to give some basic support. Will we provide also that kind of service through twitter?

Great article Alexander! One question. Why is there such difference in performance of $order? How could this affect to the general performance of an application using not Caché Standard for globals and mainly using SQL access to deal with data?

I've tested your ordering routing with Spanish2, 4 and 5 collations and are >4 times slower in inserts and order... !!!

Many thanks!

Great article! I see there is no scenario where the failover members are in different locations. I guess latency factor is the one to blame here, isn't it? Are there any numbers based on your experience that allow others to get an idea about what scenario is more appropiate for them to choose based on expected # of transactions, total volumen of data, required response time, network latency and/or other criteria