microservices

From: Tegiri Nenashi <TegiriNenashi_at_gmail.com>
Date: Wed, 25 May 2016 08:53:38 -0700 (PDT)
Message-ID: <6ddbb008-df79-4562-a274-4de9ab776c4b_at_googlegroups.com>

For those who are missing CORBA, here is new buzzword: "microservices"

http://arstechnica.com/information-technology/2016/05/blow-that-data-monolith-to-smithereens-with-microservices-and-database-swarms/

This is apparently the view of database non-specialist. A database person might think that having numerous database instances is a nuisance, and ideally there should be just one single source of truth. If all database instances in the world were consolidated into one, then the whole area of research -- data integration (in current form) would become irrelevant.

In practice, how do we make such, buzzword speaking, "superdatabase"? Clearly there are different owners of different parts of the schema so, how to design schema overlap?

There is another buzzword flying around for some time already -- "cloud". The conventional wisdom is that every customer buys a nice piece of database property and lives happily on their estate (paying rent to a vendor). However, wouldn't it make much more sense for those customers share the data? How this can be organized; what incentive for data sharing might be offered to a customer? Received on Wed May 25 2016 - 17:53:38 CEST