Limitations of APEX for WebApp

I have a currently joined a project and the customer the team supports gave a layout of requirements. To my idea these requirements are very demanding to be on a Web Application level. It needs to handle daily transactions, list upda开发者_运维技巧te alerts, etc. I pursue the idea of using .NET webapplication. The ideas have come up to use APEX. I am not familar at all with. Reading up on it I found that it is basically a Oracle front end application that runs off a Oracle DB. The front end is limited to html/css modification and only report generating? So I really dont know the real limitations I would have as a developer by using APEX

Have you looked on apex.oracle.com? Lots of resources there for getting to know the capabilities of Apex.

Apex is a tool for creating web-based applications that run on top of an Oracle database. Since it works using HTML and Javascript it can do pretty much whatever can be done with any other web-based application platform - more or less easily than others depending on what it is you want to do.

Your question is quite vague about the "demanding requirements". Perhaps pick one you think would be a problem for Apex and describe it in more detail?

I'm an advocate of Apex and know little about .Net: but the choice of development platform and architecture must include consideration not only of the requirements and capabilities (although these are very important, of course) but also the skills and experience of most of the developers and maintainers of the system.

There's not much you can't do in both Apex and .Net - but if the team is not skilled in Apex but is experienced in .Net that would be a major factor in choosing .Net instead.

Other considerations are cost and simplicity - Apex, I suspect, is a lot simpler than .Net (less moving parts, tighter integration with the database) and cheaper (i.e. free with the Oracle licence).

(plus: what Tony said.)