让我们来看一个典型的桌面应用程序问题。
要回答这些问题，我们需要看看应用程序代码本身。
To answer those questions, we have to take a look at the application code itself.
对于某些应用程序，这可能是一个主要问题。
每次在应用程序中出现问题时，都需要重复此过程。
The process had to be repeated every time any problem occurred in an application.
sdo避免了这个问题；使用SDO编写的应用程序不必改变。
SDO avoids this problem; an application written with SDO need not change.
对于某些应用程序，这可能是一个大问题。
如果他们报告了问题，您知道他们正在使用您的应用程序。
If they have reported a problem, you know they are using your application.
对于应用程序的每个实例来说，这个问题更加重要。
With every instance of the application, this issue becomes more important.
和上面描述的场景一样，假定您在尝试解决应用程序挂起的问题。
As in the scenario described above, suppose you are trying to resolve an application hang.
对于这类情况，需要重新设计应用程序才能避免问题。
For such cases, you want to redesign the application to avoid the problem.
即使做了很好的前期规划，应用程序仍可能出现重大的性能问题。
Even with good up-front planning, any application is likely to have some significant performance issues.
当然，在您的整个应用程序套件中解决此问题的次数越多，效果就越好。
Of course, the more times this problem is solved across your application suites, the better.
这可以使您了解自己的应用程序设计中存在的潜在安全问题。
It will let you see any potential security issues in your own application design.
在软件开发方面，大部分软件应用程序是用来解决特殊问题的。
In terms of software development, most software applications are written to solve a particular problem.
在您尝试伸缩应用程序时，常遇见的问题是数据库中的写入争用。
A common problem as you try to scale applications is write contention in the database.
这对于大多数应用程序来说没有多大问题。
尽管如此，将其运用到其他启用CDI的应用程序服务器应该也没有问题。
However, you should have no trouble getting it to run in another CDI-enabled application server.
在应用程序中，执行可以触发性能问题的操作。
In the application, perform the steps required to trigger the performance problem.
开发人员只需关注应用程序本身，而不需要关注部署和IT问题。
Developers can focus on the application itself, as opposed to deployment and it issues.
在设计应用程序时，有一些常见问题需要注意。
When designing your application, there are a few common problem areas to look out for.
部署一个服务器端的应用程序时，问题就更为严峻。
This problem is especially serious when deploying server-side applications.
请参见应用程序设计问题。
是什么原因导致我的应用程序产生性能问题？
数据源和应用程序之间的网络问题。
Network problems between the data source and the application.
在已有的生产服务器上运行Grails应用程序也没有问题。
Running a Grails application on your existing production server is no problem either.
所以设计一个REST风格的客户端服务器应用程序的主要问题有。
So the key questions for an architect of a REST-style, client-server application are.
本文不讨论应用程序开发问题和DeveloperWorkbench。
This article does not discuss application development issues or the development Studio.
当然，Rails应用程序具有性能问题的原因可能有很多。
Of course, there are many more possible reasons why a Rails application has performance issues.
跟踪有问题的应用程序或守护进程。
另一个问题是这个应用程序太一般了。
应用推荐