在Google App Engine上使用Jax-RS代替Cloud Endpoints有什么问题 [英] What are the problems with using Jax-RS instead of Cloud Endpoints on Google App Engine

问题描述

我正在Google App Engine/数据存储上开发一个Java Web项目作为移动应用程序后端.

I'm developing a java web project on Google App Engine/Datastore as a mobile app backend.

要求是仅使用免费提供的服务(对于Google Cloud中的低使用率是免费的)，这样我就可以便宜地上手，并且(理论上)不必做太多工作即可扩展规模以容纳更多用户.

The requirement is to only use services available for free for low usage in Google Cloud so that I can get started cheaply and (theoretically) have to do much less work to scale up to handle more users.

我是JavaEE开发人员，正在考虑在Google App Engine而非Google Cloud Endpoints中使用Jax-RS.

I am a JavaEE developer and am considering using Jax-RS inside Google App Engine instead of Google Cloud Endpoints.

已阅读 Google App Engine中的JAX-RS服务和其他一些答案，我对以下问题的答案很感兴趣，尤其是在2018年，因为大多数答案都非常老了:

Having read JAX-RS services in Google App Engine and some other answers, I am interested in answers to the following questions, especially in 2018 as most answers are very old:

• 就以下方面而言，我将使用Jax-RS而不是Cloud Endpoints放弃什么:
  • 与Google的auth sdk集成时，Cloud Endpoints是否更易于使用?
  • 我会在日志记录和指标方面放弃任何东西吗?
  • 当我出于任何原因将App Engine运行时与Jax-RS结合使用时，使用Arquillian进行测试是否更加困难?
  • Jax-RS servlet是否需要自定义管道以启用SSL?
  • 我没想到的任何事情...
  • What would I give up by using Jax-RS instead of Cloud Endpoints in terms of:
    • Are Cloud Endpoints easier to use when integrated with Google's auth sdk?
    • Would I be giving up anything in terms of logging and metrics?
    • Is testing with Arquillian more difficult when I combine App Engine runtime with Jax-RS for any reason?
    • Would the Jax-RS servlet require custom plumbing to enable SSL?
    • Anything I haven't thought of...

    对我来说，Jax-RS的明显优点是易于开发(Cloud Endpoints需要更多样板)以及我已经非常熟悉它的事实.

    To me, the obvious advantages of Jax-RS are it's ease of development (Cloud Endpoints appears to require more boilerplate) and the fact that I am already very familiar with it.

    非常感谢有经验的建议.

    Experienced advice is greatly appreciated.

    推荐答案

    您应该可以使用JAX-RS，但是您会失去一些Cloud Endpoints功能，例如:

    You should be able to use JAX-RS, but you loose some of Cloud Endpoints features like:

    • 身份验证
    • 监视-尽管每个请求都会获得正常堆栈驱动程序跟踪
    • Arquliliam应该与任何一个一起工作.
    • 无论哪种方式，SSL都应该可用. (请注意，它终止于我们的负载均衡器而不是应用程序)
    • Authentication
    • Monitoring -- Though each request will get the normal Stackdriver trace
    • Arquliliam should work with either.
    • SSL should be available either way. (note it terminates at our load balancer not the app)

    通过使用Jax-RS而不是Cloud Endpoints放松的关键功能是服务控制.

    The key feature you loose by using Jax-RS instead of Cloud Endpoints is Service Control.

    这篇关于在Google App Engine上使用Jax-RS代替Cloud Endpoints有什么问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！