With my first post of 2016, I’d like to wish you a happy new year. After a bit of a shutdown for the holidays, I am back at work on some project activities that I had been working in the last quarter of 2015. Specifically, one of our long-standing federal customers has been directed by their customer to migrate their application platform to an open-source stack. The application in question is a mature analysis and visualization application that has been built on a Microsoft (with a little bit of Esri) stack. A migration will be no small effort.

Image by Daniel Rosengren [CC BY 4.0], via Wikimedia Commons

The migration has brought me back in touch with all of the potential issues that must be considered in a migration from any platform to another. (I’ll set aside the proprietary-to-open-source considerations because they are really side issues in this case.) The target platform is a grab-bag of open-source tools of varying provenance. The source platform is built using Microsoft SQL Server, .Net-based APIs, and Silverlight. The GIS/location requirements are mostly handled by Esri tools, but they represent less than 20% of the overall system function.

Read full article here.