<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Java-Ee Dead on Rowanto Luo</title><link>https://log.rowanto.com/categories/java-ee-dead/</link><description>Recent content in Java-Ee Dead on Rowanto Luo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 16 Sep 2014 09:00:00 +0000</lastBuildDate><atom:link href="https://log.rowanto.com/categories/java-ee-dead/index.xml" rel="self" type="application/rss+xml"/><item><title>Java Application Server is dead, so is Docker?</title><link>https://log.rowanto.com/posts/java-application-server-is-dead-so-is-docker/</link><pubDate>Tue, 16 Sep 2014 09:00:00 +0000</pubDate><guid>https://log.rowanto.com/posts/java-application-server-is-dead-so-is-docker/</guid><description>
&lt;p&gt;So lately, a lot of people in my circle is talking about why java application server is dead. The reason why is explained in the slides &lt;a href="http://de.slideshare.net/ewolff/java-application-servers-are-dead"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Basically what I get is that because nowdays people only deploy one artifact in one application server, it beats the point of the application server. It&amp;rsquo;s more like that the application server is already part of the application. So, it would be better to treat the application server as part of the application and ship them together as a package.&lt;/p&gt;</description></item></channel></rss>