What are the problems we are trying to solve?

Do you recognize yourself in either of the following scenarios:

1. You have huge web based application written over the years in a in-house framework.

You are finding following problems coming to haunt you over and over again:

  • You cannot "buy-in" the experience. Every now and then you find yourself educating persons for your own framework
  • Lack of community. You cannot "google for solution", you have to write one by yourself.
  • None or invalid documentation. As there is always significat lack of time there has either never been time to write proper documentation or the documentation is out of date.
  • Lack of innovation. Software industry moves on very quickly and the solutions good enough in the 199x (or whenever your architects wrote the solution) are now considered stone-age.
  • Problems with development and maintenance of the application itself. Original authors have already left the company and nobody actually dares to change framework code.

So you have considered migrating to the framework X you find most suitable for your needs and amount of expertise within region. Maybe you have already tried but failed ... simply because you just cannot rewrite this amount of code within reasonable time.

But what if you could migrate from your in-house MVC framework step-by-step? What if you could leave those really scary business processes into the old codebase by encapsulating them properly and then start adding new functionality with your favourite MVC framework? Now it is possible using Aranea Integration platform.

2. You have several web applications in house written using different web frameworks and even different programming languages (Java, PHP, .NET).

You are exploring new business areas and you need new applications but you simply cannot understand why developers are writing yet another customer search component*.

What if you could reuse the functionality already written into your different applications? What if you do not have to do it decreasing your requirements for usability/look and feel?** What if you can leverage existing investments done handling stateful applications?**

* note that we are talking about the MVC view and controller code here, we truly believe that your service layer is already written in a really disciplined manner allowing reusage.

** as opposed to the typical portal solution