Right now we are working with a classic ASP.NET WebForms project with a Model-View-Presenter (MVP) architecture. Our company wants to move towards a common way to share data between applications based on RESTful APIs. Therefore we are looking for ways to transform our MVP architecture to a WebAPI project. There is quite a lot of code in the presenters and it will take a long time to move the code to another layer. We are looking for a good way to transform to an architecture based on WebAPI's.
Right now there is a strong binding between the .aspx pages with code behind and the presenter layer. One idea is to place one more layer in between the Presenter and View. That way we can replace the old .aspx with a more modern page. E.g.,
Old view | WebAPI layer
Is this a good idea? We hope to hear your input regarding this plan. What are the pitfalls? Are there better ideas? Any experiences?
Perhaps this question is not suitable for stackoverflow since it is more a request for discussion. Suggestions for a better place to ask are welcome if so.