Difference between revisions of "AMI Realtime Database"
Jump to navigation
Jump to search
(Created blank page) |
Tag: visualeditor |
||
| Line 1: | Line 1: | ||
| + | = Goals = | ||
| + | The 3Forge Realtime database builds on all of the features available in the '''AMI SQL''' language. The real-time datamodeling | ||
| + | * '''High Speed''' - 100k+ inserts per second, with 1 billion+ rows | ||
| + | * '''Persistent''' - Tables can be configured for long-term persistence | ||
| + | * '''Data Virtualization''' - Access external sources seamlessly | ||
| + | * '''Realtime Streaming''' - Chaining streams of updates into aggregations and other projections | ||
| + | * '''Source Synchronizing -''' Synchronizing in-memory tables based on external datasources | ||
| + | * '''Extendable''' - Create custom triggers, procedures, etc. | ||
| + | |||
| + | Broadly speaking, the logic steps involved in data-visualization are: | ||
| + | |||
| + | # Data is "streamed" into the AMI real-time database through a combination of methods | ||
| + | #* High Speed Messaging | ||
| + | #* JDBC | ||
| + | #* Synchronizing from External Datasources | ||
| + | #* User updates, from the front end visualization layer | ||
| + | # Data is fed through logical components which can aggregate, etc. | ||
| + | # Visualizations are built on the real-time tables and streams. | ||
| + | |||
| + | == About Realtime (PUBLIC) tables == | ||
| + | For the AMI Center, by default tables that are created are only visible to the current session and will be cleaned up when the connection is terminated. When a table is created with the PUBLIC directive (ex CREATE PUBLIC TABLE ...) the table will now be accessible to all sessions (external connections, triggers, etc) and front ends for real-time viewing. Public tables will continue to exist until they are explicitly dropped. Please see the '''''reserved columns on public tables''''' section for details on specialized columns that can be added. | ||
| + | |||
| + | = Realtime Tables = | ||
| + | |||
| + | = Realtime Indexes = | ||
| + | |||
| + | = Realtime Triggers = | ||
| + | |||
| + | = Realtime Timers = | ||
| + | |||
| + | = Realtime Procedures = | ||
| + | |||
| + | = Realtime Tools = | ||
| + | |||
| + | = Capacity Planning = | ||
Revision as of 07:02, 9 March 2021
Goals
The 3Forge Realtime database builds on all of the features available in the AMI SQL language. The real-time datamodeling
- High Speed - 100k+ inserts per second, with 1 billion+ rows
- Persistent - Tables can be configured for long-term persistence
- Data Virtualization - Access external sources seamlessly
- Realtime Streaming - Chaining streams of updates into aggregations and other projections
- Source Synchronizing - Synchronizing in-memory tables based on external datasources
- Extendable - Create custom triggers, procedures, etc.
Broadly speaking, the logic steps involved in data-visualization are:
- Data is "streamed" into the AMI real-time database through a combination of methods
- High Speed Messaging
- JDBC
- Synchronizing from External Datasources
- User updates, from the front end visualization layer
- Data is fed through logical components which can aggregate, etc.
- Visualizations are built on the real-time tables and streams.
About Realtime (PUBLIC) tables
For the AMI Center, by default tables that are created are only visible to the current session and will be cleaned up when the connection is terminated. When a table is created with the PUBLIC directive (ex CREATE PUBLIC TABLE ...) the table will now be accessible to all sessions (external connections, triggers, etc) and front ends for real-time viewing. Public tables will continue to exist until they are explicitly dropped. Please see the reserved columns on public tables section for details on specialized columns that can be added.