brand names and trademarks are the properties of their respective companies. Introduction ▪ Drillinginfo’s Platform - Highlights from the past year ▪ Managing cost in “The Cloud” ▪ Architecture related to performance tuning ▪ Where do we go next? - Productizing, Managed API, Technology Choices
brand names and trademarks are the properties of their respective companies. Quick Recap: Where were we this time last year? ▪ 1 year into completely new OGC driven architecture ▪ 2 browser (JavaScript) apps (U.S. and Int’l) ▪ U.S. - One data set, very limited functionality ▪ International - several data sets, limited functionality ▪ GeoData services in beta
brand names and trademarks are the properties of their respective companies. Drillinginfo’s Platform - Highlights from the past year ▪ DI Browser Map Apps: ▪ ~250 U.S. layers supported by GeoServer ▪ Vary from searchable and exportable to base layers that never change ▪ 7 Int’l layers supported in separate app ▪ All searchable and exportable ▪ Continuing to build daily
brand names and trademarks are the properties of their respective companies. Drillinginfo’s Platform - Highlights from the past year ▪ GeoServer now supporting many different applications/functions: ▪ GeoData Services - stand alone WMS/WFS utilitzed by clients in 3rd party applications ▪ Transform Software ▪ DI Rigs Mobile App ▪ DI web browser domestic and international map applications
brand names and trademarks are the properties of their respective companies. Managing Cost in “The Cloud” ▪ DI Recently moved to reserved instances ▪ Pay up-front fee to get a better hourly rate ▪ 64 bit, 8 CPU, 15GB RAM, 2 x 80GB SSD running 24/7 = ~$4,000/Year per server ▪ Need good auto-scaling architecture for on-demand instance set up ▪ We’ve built a complex architecture including: ▪ GeoServer, PostGIS Server, App Server, Services (Export, Entitlements, Other) Server ▪ Involves a large stack of servers ▪ Moving to Open Stack to replace AWS costs for development ▪ Implementing Piwik to collect usage analytics ▪ No software licensing fees but more spent in development hours: ~ 30 dev’s working on this ▪ As we build, it should get cheaper…..
brand names and trademarks are the properties of their respective companies. Benchmarking & optimization ▪ Benchmarking ▪ worked with GeoSolutions (Italy) ▪ ControlFlow module for Geoserver ▪ Allows for control of number of concurrent requests executed, by request type ▪ Resource control ▪ Limiting users
brand names and trademarks are the properties of their respective companies. Customer Needs & Challenges ▪ Connect directly with WMS/WFS Clients ▪ Integrate our services into their existing applications ▪ Data ingestion
brand names and trademarks are the properties of their respective companies. Productization is a multi-step & multi-year process! 2nd Quarter - 2013 (Standalone GeoData Services) 3rd / 4th Quarter - 2013 (Beta Mode for GeoData Services during this time last year.) 1st Quarter - 2014 2nd / 3rd Quarter - 2014 Now and Into 2015! (Planning for next step up in deliverables now - “Premium” GeoData Services.) GEODATA SERVICES
brand names and trademarks are the properties of their respective companies. Product Roadmap - Where are we now? Where do we go next? GeoData Services (Standalone WMS/WFS) ▪ 65 Top-Paying Customers ▪ 15 layers ▪ 101 styles (symbologies) Javascript Application (aka “DI 2.0”) ▪ 250+ U.S. Layers ▪ 7 International Layers Managed API (developers.drillinginfo.com) ▪ Beta - End of Year Goal is to have API in front of GeoServer and ESRI Map & Feature Services
brand names and trademarks are the properties of their respective companies. Cloud Current Technology Choices Manufacturing GeoPortal (Internal) On Premise Presentation (External) Migration Process
brand names and trademarks are the properties of their respective companies. Cloud Future Technology Choices? Manufacturing GeoPortal (Internal) On Premise Presentation (External) OGC Migration ESRI Migration Prototype Underway Now!
brand names and trademarks are the properties of their respective companies. ▪ Diverse client base has led to more flexible offering utilizing a managed api ▪ Both internal and external clients have many needs ▪ Certain clients must have esri services ▪ Don’t be afraid to ask for help - GeoSolutions ▪ Need great documentation on how to use ogc services ▪ A broad client base will always have a lot of questions - we underestimated this ▪ Almost one FT position to support geodata services Lessons Learned