How do I signin?
To signup, simply navigate to our Dashboard and click the "Sign In" button.
How do I get in touch with you?
Where is Orchestrate hosted?
At present, Orchestrate is hosted on both CenturyLink Cloud and Amazon Web Services in regions around the world. Orchestrate is deployed to the following data centers:
- CenturyLink Cloud VA1 (Northern Viriginia)
- CenturyLink Cloud UC1 (Santa Clara, California)
- CenturyLink Cloud NY1 (New York)
- CenturyLink Cloud GB3 (Great Britain)
- CenturyLink Cloud SG1 (Singapore)
- Amazon Web Services US East (Northern Viriginia)
- Amazon Web Services EU West (Ireland)
What sort of performance can I expect? Do you have benchmarks demonstrating latency and throughput?
We performed a series of benchmarks on the production Orchestrate system that have been documented in a blog post here. Assuming your application is deployed similarly to our benchmarking service, you can expect similar performance.
What types of applications is Orchestrate intended for?
Orchestrate can be used by a broad range of applications. CMS, social networks, game backends, storage services, product catalogs, and blogging engines are all good use cases. Orchestrate is meant for server-side applications as all clients with an API Key can read, write, and delete any record in an application. As such, Orchestrate is a perfect database backend for SaaS applications.
What types of applications is Orchestrate not good for?
Orchestrate does not provide transactions. If your applications rely on ACID semantics for coordinating the updates of multiple fields in different objects, then Orchestrate may not be a good fit.
Orchestrate is not good for client-side web or mobile applications where there is no server-side intermediary. This is due to the fact that API Keys impart full access to applications. Applications using Orchestrate should protect their API Keys by embedding them in server-side applications.
How can I import/upload an existing dataset?
At present, the best way to import data is using the
HTTP API's bulk functionality. We have a simple
bash-based tool that uses the bulk API available on
Github. If you have a large dataset (>1 million records), please open a
support request and we will help you with your data import.
How safe is my data?
Orchestrate is built on top of distributed storage engines for data resilience. Every piece of data stored is replicated a minimum of 3 times.
In addition to distributing data for resilience, Orchestrate backs up all data stored by all users a minimum of once per day.
If you require additional backups, you can use Orchestrate's export feature to perform on demand backups. You can read about that feature here.
What databases does Orchestrate run?
Our goal is provide a service that eliminates the need for developers to worry about databases. We also realize that developers want to know what systems we use, so that they can make informed decisions about whether our system meets their requirements. To that end, we maintain a list of tools and services, including databases, that back Orchestrate. You can find that list in our Knowledge Base here.
Where should I deploy my applications?
For best performance, applications should be deployed in the same data center as your Orchestrate application.
How does Orchestrate differ from Backend as a Service (BaaS)?
Orchestrate has one main similarity with BaaS, they both provide a way to persist data. Where they differ is in their range of offerings.
BaaS tend to focus on providing a common set of backend services including authentication, data synchronization, and data storage.
Orchestrate when compared to particular BaaS will tend to have both a broader and deeper data storage and querying feature set.
Since BaaS have a broader feature set, they tend to offer less depth with each particular feature. Users often find that BaaS offerings lack the ability to do highly specialized things like graph queries or full-text search.
Where can I check the status of Orchestrate?
Orchestrate maintains a status twitter account, Orchestatus.
Does Orchestrate impose rate limits?
While Orchestrate does not limit the number of requests per second that a user can perform, Orchestrate does throttle users under particular conditions.
If a user is interacting with our API in a way that could seriously affect the performance of other users, we may throttle them. We may also throttle users in the free tier who are nearing their operations allotment for the month.
Orchestrate does not apply a throughput ceiling. Our throttling is meant to ensure smooth and predictable performance for all users.
What software and services is Orchestrate built with?
We maintain a knowledgebase article with this information here.