GeoBase Server
GeoBase is designed for scalability in high-transaction count environments.   
  • Stable - GeoBase servers have run through tens of millions of transactions without a fault.
  • Compact - The GeoBase file system compresses over 20 GB of street data for the US & Canada down to ~1.8GB allowing the entire data set to be loaded into local memory.
  • Fast - The data indexes and function calls are all designed for fast response times.
  • Adaptive - GeoBase is able to utilize as much available resource as possible, but can just as easily operate in resource-constrained environments.
 
GeoBase is designed for flexibility in various system architectures.  Below are a couple of examples of how GeoBase can be used in a system. 
 
GeoBase Appliance
 
 
 
GeoBase geosptial appliance

 

 

 

 

 

 

 

 

 

Overview

In this model, GeoBase is used as an appliance; all spatial transactions occur on the singleserver. The spatial functions are accessed through a web service or a remoting interface.

GeoBase can also be installed through VMware.

Advantages

  • Stateless - GeoBase always starts with the exact same starting point and is not subject to the changes that other processes may make to the system registry, etc. This enhances overall appliance stability.
  • Platform Independent
  • Easier Update Management

Disadvantages

  • Requires a more powerful machine
  • Slower spatial access across the remoting interface
  • Single point of system failure

 

 

Distributed GeoBase Processes

 

 

 GeoBase distributed geospatial processes

 

 

 

 

 

 

 

 

 

Overview

In this model, GeoBase is installed on a number of machines that serve different functions. Servers can be partitioned by geographic region to reduce memory required.

Alternatively, server can serve dedicated functions. A web server can handle all user initiated transaction such as map rendering and geocoding. A function server can handle processor-intensive functions such as route optimization. The database server can handle communications and rule processing related to GPS-based units deployed in the field.

Advantages

  • Resources are dedicated to the function and the system can be architected to optimize performance
  • Each machine can be a lower specification
  • GeoBase runs in-process with other applications, so the performance is greatly enhanced

 

Disadvantages

  • More machines to maintain and update
  • GeoBase may occupy resource that would otherwise be available to other processes on the server
  • GeoBase performance is subject to the other processes on the server
 
(c) 2007 Telogis, Inc.
Joomla Templates by JoomlaShack Joomla Templates
Home arrow Platforms arrow GeoBase Server