As a transitional step, this site will temporarily be made Read-Only from July 8th until the new community launch. During this time, you can still search and read articles and discussions.

While the community is read-only, if you have questions or issues requiring TIBCO review/response, please access the new TIBCO Community and select "Ask A Question."

You will need to register or log in or register to engage in the new community.

TIBCO Graph Database - Performance Q&A! (Answers by the Chief Architect TIBCO)

1. How does TIBCO Graph Database support HA and redundancy?
Answer Current version supports NFSV3+, SAN based storage which supports shared file lock. 
    So TGDB server can be configured for hot standby. The client has to reconnect today manually.
    A Future version will support fault-tolerant client, with Clustered TGDB Servers with N-Readers,and FT-Writers.

2. Backup and recovery? Do we take periodic full backup without incremental backup?
Current version provides Fast Import/Export to CSV files and that can be used for Backup and recovery. Admin can also issue checkpoints command which can be scripted.
Transaction logs are of extension “.shm”. For high performance Transaction Logs are built using shared memory mapped files.
As of now - yes. A Future version will include incremental backups using Change Data Control Interface.  

3. Please tell me more about Product Scalabilituy
Answer: Assume you are referring to the Product’s scability.
   TGDB Servers scale up vertically in the current version. They can address 256TB of physical storage, and 64TB of memory. 
   It support multiple net listeners, for throughput, and is efficient (both in power and performance) to utilize all the core’s. 
   It leverages the SIMD/SSE4 and Advance Vector Extensions of Intel/AMD instruction set.
   Future version we will have a Clustured TGDB Servers with N-Readers and FT-Writers which will address throughput.
   We are creating webinars to be available soon!

    The next service pack should be good enough for customer’s to take it into small productions.

4. Any tools for performance tuning?
Answer: Admin provides “info” command that can provide with monitoring information. The info command provides detailed info on txn writes, query, database size, cache hits/miss. Current version utilizes the index to efficient get to data. Future version will provide:
       a.> Database Storage tuning
       b.> Explain Query, and optimize query
       c.> We are looking for inputs.
5. When will it support Rest API or Golang client that could be integrated with Flogo and TCI?
Answer: TGDB has open-sourced the client API, the source code is in GitHub.
      Java Rest API is also built and will be available on Github soon. GoLang: We expect collaboration.

6. Do we have full Query Language document?
Answer: The current Query Language is the Extended SQL-92 filter clause similar to the where clause. Future versions we will add support to Cypher,and/or Gremlin.
       We are also looking at  DGraph JSON spec, and others.