Dynamic change

Schemas

All database objects can be dynamically changed, where any changes take immediate effect. Hence, schemas and objects are agile and can be changed at will to meet the demands of evolving requirements as and when they occur. There is no need to "see around the corner" or make decisions with unfortunate long-term consequences.

tables.jpg

 

Agility

Objects such as indexes, partitions and shards are the root of performance issues for most relational and non-relation database systems - either because one or more structures are missing or incorrect; and changes to these structures are notoriously difficult to implement because of the resources and time consumed by such changes.

Edge Intelligence entirely removes any need to design, deploy or manage these structures and this is crucially important for dynamic change - especially when managing petabytes of data distributed across a population of widely geographically distributed servers.

stopwatch.jpg 

 

Topology

The depth and shape of a network can be dynamically changed, with all changes to the network structure taking immediate effect. Hence, the network can always reflect the current perception of geographies and regions and how geo-distributed data is categorised or located.

topology.jpg

 

Have more questions? Submit a request

Comments

Article is closed for comments.

Powered by Zendesk