|
Deciding to take the leap from one technology to another is a difficult one. You face the risk of improper implementation of the technology, which can cause performance issues. You also face possible impact to business logic, which can produce disruption to your customers and partners. Many core business processes were written many years ago and live on legacy environments; although the developers who wrote them are long gone, and the support teams who run the operations likely are offshore and have a high resource turnover rate. Over time, the cost of maintaining these legacy systems will increase, and the knowledge of how they work will continue to dwindle.
Although change from legacy systems to more robust platforms and newer technologies is difficult, the rewards in the form of cheaper operations cost and increased customer loyalty, as well as avoidance of risks, likely setbacks, and wrong turns are worth the effort. Not only that, but your employees will stay around longer and your developers will be happier because they get exposure to and are working on the newest technologies.
After you decided to migrate for all those good reasons, you can move to the following section, which discusses some of the differences between ASP.NET, ASP.NET MVC, ADO.NET, and NHibernate. |
