WebApp 的 APEX 限制
我目前加入了一个项目，团队支持的客户给出了需求布局。在我看来，这些要求对于 Web 应用程序级别来说非常苛刻。它需要处理日常交易、列表更新警报等。我追求使用.NET Web应用程序的想法。想到了使用APEX。我一点也不熟悉。阅读它后，我发现它基本上是一个在 Oracle DB 上运行的 Oracle 前端应用程序。前端仅限于html/css修改并且只能生成报告？所以我真的不知道作为开发人员使用 APEX 会遇到什么真正的限制
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 update 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
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您是否查看过apex.oracle.com？有大量资源可用于了解 Apex 的功能。
Apex 是一个用于创建在 Oracle 数据库之上运行的基于 Web 的应用程序的工具。由于它使用 HTML 和 Javascript 工作，因此它几乎可以完成任何其他基于 Web 的应用程序平台可以完成的工作 - 比其他平台或多或少容易，具体取决于您想要做什么。
你的问题对于“苛刻的要求”相当模糊。也许选择一个您认为会对 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?
我是Apex的拥护者，对.Net知之甚少：但是开发平台和架构的选择不仅要考虑需求和能力（当然这些很重要），还要考虑大多数人的技能和经验。系统的开发者和维护者。
在 Apex 和 .Net 中没有什么是你不能做的 - 但如果团队不熟悉 Apex，但在 .Net 方面经验丰富，那么这将是选择 .Net 的一个主要因素。
其他考虑因素是成本和简单性 - 我怀疑 Apex 比 .Net 简单得多（移动部件更少，与数据库集成更紧密）并且更便宜（即通过 Oracle 许可证免费）。
（加上：托尼说的话。）
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.)