Link Details

I have focused a lot of time optimizing a system very much like Google maps, except for the exact opposite data set, extremely volatile data. Without focusing on the details of the project, this data could change every 6 hours, to ever 15 minutes. Being service oriented and the difficulty to visualize this dataset had us utilizing the OGC Web Mapping Service (WMS). However for large, extraordinary volatile data, using standard WMS requests just wont cut it for a high performance, highly active web applications. What was the next step?

Posted by nicholastuck  |   Submitted: Mar 02 2011 / 06:00

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Recommended Links

Upvoters (3)

Downvoters (0)

    Written by: Ryan Knight
    Featured Refcardz: Top Refcardz:
    1. Apache Hadoop
    2. Play
    3. Akka
    4. Debugging JavaScript
    5. Design Patterns
    1. Apache Hadoop
    2. REST
    3. Java
    4. Git
    5. Java Performance
    Connect with DZone