Orchestrate Adds Geospatial Search to its All-in-One Database Service

Orchestrate, a leading database-as-a-service (DBaaS) company, has just announced the addition of geospatial search to its database service. Late last month, the company announced significant enhancements to its Search API, made in preparation for the new geospatial search feature. The enhancements include the addition of field sorting and flexible data indexing. The Orchestrate Platform makes it possible to manage multiple databases using the Orchestrate.io API and a single interface.

The addition of geospatial search allows the Orchestrate platform to provide developers with a complete database and data processing solution that can be used to build Web, mobile and Internet of Things applications. The Orchestrate.io API unifies multiple databases, allowing developers to include database functionality in applications without the need to set up and manage the databases. The API also allows developers to run queries such as ad hoc, full-text search, time-ordered, graph, key/value and now geospatial search.


ProgrammableWeb reached out to CTO Ian Plosker, who explained that Orchestrate is designed to make complicated database technologies such as Hadoop, Elasticsearch and Apache Lucene accessible to developers and easy to use. Orchestrate makes it possible for developers to use these complicated database technologies without the very steep learning curve associated with them. Plosker also explained to ProgrammableWeb that applications and databases are becoming more diverse, causing many developers to move away from traditional relational databases and toward using NoSQL, in-memory and cloud databases. "Relational databases are becoming less important," Plosker said.

ProgrammableWeb recently published an article about the increasing use of graph databases and graph analysis by companies to gain insights from IoT-generated interconnected data. ProgrammableWeb asked Plosker if Orchestrate is seeing an increase in the use of graphing and graph analysis by its customers and users. He said the company is seeing a lot of people using graph databases because they are more flexible in nature and "they allow more diverse, interesting questions to be asked and determined from data." He also said that social networks are the most popular use cases for graph databases and that e-commerce applications are using them as well.

The Orchestrate platform not only allows developers to run graph data queries, but when combined with geospatial search, full-text search and time-series events, developers can build complete database-driven apps. In the >press release, Plosker said:

By combining geospatial with full-text search, time-series events and graph data queries, Orchestrate now delivers a truly turnkey service for developers building complete apps, or simply adding new features without having to spin up new databases. We're excited to offer our customers a truly one-stop shop for all of their database requirements.

Orchestrate's geospatial search functionality includes the ability to do the following:

  • Automatically discover geographic coordinates within data
  • Constrain results to geographic areas defined by radius or map boundaries
  • Compound queries to further filter by any fields within the same data set (i.e., categories, keywords)
  • Sort results by distance in kilometers, miles, meters or feet

Orchestrate’s geolocation feature allows developers to add new dimensions to their data and add context to the end- User Experience without adding a new database to their Stack. There are an infinite number of use cases for geospatial search functionality as nearly all mobile devices and a great many Internet-connected devices include geolocation features.

Plosker told ProgrammableWeb:

For example, IoT developers can geotag their sensors, allowing them to do things like retrieve a list of all of the sensors and their readings for a particular area. Let’s say you have a network of air pressure sensors around Portland. You might store a document with the metadata about each sensor, including its geolocation. Then you could use Orchestrate’s time-ordered events functionality to store the periodic readings from each device. When it comes time to check the readings for a particular area, you can apply a bounding box or point and radius search, get a list of sensors for that area and then retrieve their readings.

For more information about the Orchestrate platform and geospatial search, visit Orchestrate.io.

See other ProgrammableWeb articles about Orchestrate, including an article about the beta version release of the Orchestrate.io API, an article about the public release of the Orchestrate.io API, and an article that provides an overview and walkthrough to demonstrate how Orchestrate works.

Be sure to read the next Database-as-a-Service article: Orchestrate Announces New Enterprise Multimodel Database Service and Updated Pricing