[wildfly-dev] smaller footprints

[Brian Stansberry]

This will move things in the right direction, but not all the way there 
yet. Note the set of capabilities Bill mention: web, CDI, JAX-RS, JPA. 
That sounds like our "Web" variant, plus some stuff. It's the easy "plus 
some stuff" part that needs sorting at some point.

On 2/21/14, 9:08 AM, Tomaž Cerar wrote:
> Bill,
>
> that is exactly idea we have in mind of 9.
> We already started with producing WildFly core distribution in that is
> WildFly with no subsystems, upon which you can build you own wildfly.
> It is only 15mb and contains whole mgmt capabilites (CLI, standalone,
> domain,...) you can grab it at:
> http://download.jboss.org/wildfly/8.0.0.Final/core/wildfly-core-8.0.0.Final.zip
>
> For 9 we have plans to move things bit further and have decided that we
> will also do split codebase for core, ee, web, .. and other distributions.
>
> Current idea on code split up is here
> https://community.jboss.org/wiki/SplittingUpTheWildflyCodeBase
>
> --
> tomaz
>
>
>
> On Fri, Feb 21, 2014 at 3:00 PM, Bill Burke <bburke at redhat.com
> <mailto:bburke at redhat.com>> wrote:
>
>     On Resteasy list I have a few people "rolling their own app server"
>     using Netty, Weld, Resteasy and JPA.  I asked one of them "I don't
>     understand why you are rolling your own app server"  response:
>
>     "It's actually a lot more lightweight.  The minimum I can run the
>     equivalent on AS7 on is ~ 180 mb in binaries, but throwing this
>     together is about 32 mb (and compresses further when its packaged).
>     I'm able to start the JVM on the bare minimum (~100mb on my linux VM)
>     but AS7 with all I need is about 756mb.  When rolling out in the
>     cloud, where all of my REST APIs are stateless, running with this
>     configuration helps us get a lot more per node."
>
>     I'm not complaining :), just something to think about.  It might be
>     really valuable to focus a bit in Wildfly 9 to make it easier to create
>     custom profiles or even different packaging options for the app server
>     instead of the exploded style we currently have.
>     --
>     Bill Burke
>     JBoss, a division of Red Hat
>     http://bill.burkecentral.com
>     _______________________________________________
>     wildfly-dev mailing list
>     wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


-- 
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat