简体   繁体   English

Google App Engine灵活部署WAR或JAR应用程序?

[英]Google App Engine Flexible-Deploy WAR or JAR application?

I see in a lot of sample projects for GAE Flexible starting to embrace the notion of a "fat" JAR (using an embedded web server like Jetty, Springboot, SparkJava or Tomcat) vs. the traditional WAR deploy. 我在GAE Flexible的许多示例项目中看到,开始采用“胖” JAR(使用嵌入式网络服务器,如Jetty,Springboot,SparkJava或Tomcat)相对于传统WAR部署的概念。 Both methods involve a single JVM process (ie no matter how many WARs are deployed to Tomcat, it's all the same JVM process). 两种方法都涉及一个JVM进程(即,无论将多少WAR部署到Tomcat,都是相同的JVM进程)。

Under what circumstances is either deployment method preferable over the other in Google App Engine Flexible? 在什么情况下,Google App Engine Flexible中哪种部署方法优于其他部署方法?

GAE has 2 types of environments for Java, one is docker-based (new) and another is what they called 'scalable'. GAE有两种Java环境,一种是基于docker的(新)环境,另一种是所谓的“可扩展”环境。 For first type, there is almost no limits for frameworks or libraries, for second - very restrictive set of supported libs. 对于第一种类型,对于框架或库几乎没有限制,对于第二种-受支持的库的限制非常严格。 Second type of environment requires WAR package, first one does not have any requirements for packaging, simply because this is docker image. 第二种环境需要WAR软件包,第一种环境对打包没有任何要求,仅因为这是docker映像。

Check this for more: https://cloud.google.com/appengine/docs/java/ 进一步检查: https : //cloud.google.com/appengine/docs/java/

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM