Post

1 follower Follow
0
Avatar

Does Apprenda platform support ASP.NET MVC 4 and workflows

Hello,

   I am architecting a web application using .NET 4.5 in VS 2012. We need to implement workflows in the web application and we would like to use Windows Workflow Foundation to implement the workflows.

  We currently have Apprenda as the PaaS platform in the organization.  I would like to know if I could architect the web application using the following technologies:

  1. ASP.NET MVC 4

  2. Entity Framework

  3. SQL Server 2012

  4. Windows Workflow Foundation.  

  5. WCF/Web API Services

 Please let me know if it is possible to  develop and host the workflows and the web application on Apprenda platform.

 Also, please let me know if we architect the web application for Apprenda, would it be portable on other cloud platforms like Windows Azure or AWS.

  Please let me know if you need more information.

  Appreciate your support.

Thanks,

Arvind

 

chikkalavalasa arvind Answered

Please sign in to leave a comment.

2 comments

0
Avatar

Hi Arvind,

Thanks for posting in the forums.  Since you stated "We currently have Apprenda as the PaaS platform in the organization", could you please submit a support ticket here: https://support.apprenda.com/tickets/new and we'll be happy to answer your questions in detail.  Be sure to include your organization name in the ticket.

Cheers,

Matt

Matt 0 votes
0
Avatar

Hi Arvind,

After our conversation through the support tickets, I though the information would be beneficial to other developers.

Those technologies are definitely supported and we have developers utilizing them.

In regards to your second question, when you develop an application for deployment to Apprenda, you can most likely deploy your application with almost none (or no) code changes assuming your application follows some basic cloud architecture patterns. In fact we have moved existing customer applications to Apprenda with no code changes at all.

That being said, you can choose to tie into some of our APIs (like caching, logging, multi-tenancy, etc.) which does come at a cost in terms of migrating to a different platform. The cost comes from your expectation and reliance on those particular components so you would have to build them yourself if you move somewhere else, so for most developers this ends up being a build now vs build later decision.

Hopefully this answers your questions and please feel free to respond if you want to talk more in depth or have additional concerns.

Regards,

Erik L

Erik Lustgarten 0 votes