Home > Blogs > VMware vFabric Blog


JavaOne Architect Viewpoint: The Inexorable March toward Simplicity

Here is a quick field report from JavaOne!

We’ve talked to dozens of people, and the theme we keep hearing is simplicity, simplicity, simplicity.

Many amazingly bright application architects have stopped by to understand and learn more about the vFabric application architecture, and these folks hail from a number of industries – giant telecom manufacturers, government ministries of defense, and multi-industry service companies to name a few.

 

These conversations with architects have tended to fall into one of the falling categories:

Learn More

Register for VMworld!
Click Here

Register for Session APP-CAP1644 – The Changing Nature of Applications and the VMware vFabric Cloud Application Platform:
Click Here

Follow all vFabric updates at VMworld on Twitter:
Click Here

1. Simpler application servers: One of the most common scenarios we are hearing is where people are running Spring workloads on WebLogic or WebSphere. They’re asking themselves why they’re spending so much in licensing costs to run these workloads, and torturing themselves with high levels of complexity. They’re looking for a more cost-effective and simple way to run Spring Java and are intrigued by how tc Server can help.  One company told us they are running over 1000 unique custom apps, and even simplifying a percentage of those applications would have enormous value.

2. Simpler ways to reduce Java memory. Another common scenario is that developers frequently request insanely large VMs to run Java applications. Here we are finding that architects are skeptical of such requests and need to know whether so much memory is required, but don’t have the tools to do so. They’re curious about Elastic Memory for Java (EM4J) and how EM4J’s sizing tools help reduce Java memory on vSphere. The EM4J screenshot below shows an example virtual machine with a great deal of wasted memory. First, not all the VM memory (vRAM) is used, even when maximum Java heap and native OS and JVM memory is taken into account. Second, only a fraction of the allocated Java heap is used. EM4J shows that two simple ways to reduce Java memory here would be to reduce the vRAM allocation and the max heap size (-Xmx).

3. Simpler ways to manage Tomcat: Teams who run Apache Tomcat want a more enterprise-ready way to manage and monitor Tomcat.  Rather than a long trial-and-error process of checking out various tools, they want an application server that preserves the best features of Tomcat, but works out of the box and lets them be instantly productive.  As a result, they’re interested in tc Server, with Spring Insight for application code monitoring, both in development and production, vFabric Admin Server for management, and more.

4. Simpler ways to provision: Architects are very interested in automatic provisioning of application infrastructure, but there is a challenge: vSphere admins want and need a certain amount of control over VMs – they cannot allow an application operations team to just spin up VMs whenever they chose and risk using up all the capacity on their vSphere hosts.  At the same time, application teams need the ability to add VMs on demand to scale, add failover, and so on.  Thankfully, Application Director provides a way out of this dilemma: it simplifies app provisioning for application teams, yet allows vSphere admins to constrain what those team can do via role-based privileges.

5. Simpler web services: At JavaOne shows a decade ago, we’d often talk about what could be now called traditional SOA, which focused on XML, SOAP, WSDL, UDDI, etc.  Today, the architects we talk to are opting for simple SOA: requests created in JSON, not XML, and sent to RESTful endpoints (not WSDL) backed by Spring MVC or Spring Data REST. And the discoverability promised by UDDI is now increasingly being implemented with HATEAOS. In fact, the one piece of traditional SOA that remains is HTTP – itself a relatively simple protocol.

If you haven’t, please stop by our sessions or the booth (#5302) at JavaOne.

This entry was posted in Application Director, EM4J, Spring, tc Server, vFabric and tagged , , , , , , , , , , , , , , , , , on by .

About Al Sargent

Al Sargent leads vFabric Suite product marketing at VMware. A VMware employee since 2010, Al has helped make the vFabric Cloud Application Platform become one of the fastest-growing application infrastructure suites in the industry. Prior to joining VMware, Al was co-founder of cloud computing startup Sauce Labs, a software testing platform as a service (PaaS). Previously, Al held product roles at Oracle, Mercury Interactive (acquired by HP) and Wily Technology (acquired by CA), and holds one patent (#7730193). He holds a B.S. Symbolic Systems from Stanford University, and an MBA from UCLA Anderson.

29 thoughts on “JavaOne Architect Viewpoint: The Inexorable March toward Simplicity

  1. Pingback: Escape JEE Bloat: Implement a Lightweight App Server Architecture | VMware vFabric Blog - VMware Blogs

  2. Pingback: Free Event in London on Dec 6th: Automate Provisioning of Spring Apps to EC2 & VMware vCloud | VMware vFabric Blog - VMware Blogs

  3. marketing manager salary

    Hi, Neat post. There is a problem with your site in
    web explorer, might test this? IE nonetheless is the marketplace chief and
    a large component of other people will pass over your wonderful
    writing due to this problem.

    Feel free to surf to my page … marketing manager salary

    Reply
  4. paper.li

    Please let me know if you’re looking for a author for your site.
    You have some really great posts and I think I would be a good asset.

    If you ever want to take some of the load off, I’d really like to
    write some articles for your blog in exchange for a link back to mine.

    Please shoot me an email if interested. Kudos!

    My homepage; concrete pool builders brisbane – paper.li

    Reply
  5. طراحی سایت

    very nice
    سئو

    Reply
  6. مد لباس

    Here is a quick field report from JavaOne!

    Reply
  7. موزیک

    add VMs on demand to scale, add failover, and so on. Thankfully, Appli

    Reply
  8. گرافیک و کاریکاتور

    Here is a quick field report from JavaOne

    Reply
  9. اقتصاد

    Server for management, and more.

    4. Simpler ways to provision: Architects are very interested in automatic prov

    Reply
  10. دانستنی ها

    er VMs – they cannot allow an application operations team to just spin up VMs whenever they chose and risk using up all the capacity on their vSphere hosts. At the same time, application teams need the ability to add VMs on demand to scale, add failover, and so on. Thankfully, Application Director provides a way out of this dilemma: it simplifies app provisioning fo

    Reply
  11. اخبار خودرو

    y chose and risk using up all the capacity on their vSphere hosts. At the same time, application teams need the ability to add VMs on demand to scale, add failover, and so on. Thankfu

    Reply
  12. تجارت

    eams, yet allows vSphere admins to constrain what those team can do via role-based privileges.

    Reply
  13. فضای مجازی

    This entry was posted in Application Director, EM4J, Spring, tc Server, vFabric and tagged application, automation, cache, cloud, development, EM4J, HATEOAS, Insight, JavaOne, JSON, memory, monitoring, operations, provisioning, RESTful, Spring, tc Server, tomcat on October 3, 2012 by Al Sargent.

    Reply
  14. تبلیغات

    4. Simpler ways to provision: Architects are very interested in automatic provisioning of application infrastructure, but there is a challenge: vSphere admins want and need a certain amount of control over VMs – they cannot allow an application operations team to just spin up VMs whenever they chose and risk using up all the capacity on their vSphere hosts. At the same time, application teams need the ability to add VMs on demand to scale, add failover, and so on. Thankfully, Application Director provides a way out of this dilemma: it simplifies app provisioning for application teams, yet allows vSphere admins to constrain what those team can do via role-based privileges.

    Reply
  15. اخبار اجتماعی

    2. Simpler ways to reduce Java memory. Another common scenario is that developers frequently request insanely large VMs to run Java applications. Here we are finding that architects are skeptical of such requests and need to know whether so much memory is required, but don’t have the tools to do so. They’re curious about Elastic Memory for Java (EM4J) and how EM4J’s sizing tools help reduce Java memory on vSphere. The EM4J screenshot below shows an example virtual machine with a great deal of wasted memory. First, not all the VM memory (vRAM) is used, even when maximum Java heap and native OS and JVM memory is taken into account. Second, only a fraction of the allocated Java heap is used. EM4J shows that two simple ways to reduce Java memory here would be to reduce the vRAM allocation and the max heap size (-Xmx).

    Reply
  16. نرم افزار

    prise-ready way to manage and monitor Tomcat. Rather than a long trial-and-error process of checking out various tools, they want an application server that preserves the best features of Tomcat, but works out of the box and lets them be instantly productive. As a result, they’re interested in tc Server, with Spring Insight for application code monitoring, both in development and production, vFabric Admin Server for management, and more.

    Reply
  17. اخبار حوادث

    ture, and these folks hail from a number of industries – giant telecom manufacturers, government ministries of defense, and multi-industry service companies to name a few.

    Reply
  18. اخبار روز موبایل

    cation Director provides a way out of this dilemma: it simplifies app provisioning for application teams, yet allows vSphere admins to constrain what those team can do via role-based privileges.

    5. Simpler web services: At JavaOne shows a decade ago, we’d often talk about what could be now called traditional SOA, which focused on XML, SOAP, WSDL, UDDI, etc. Today, the ar

    Reply
  19. اخبار ورزشی

    5. Simpler web services: At JavaOne shows a decade ago, we’d often talk about what could be now called traditional SOA, which focused on XML, SOAP, WSDL, UDDI, etc. Today, the architects we talk to are opting for simple SOA: requests created in JSON, not XML, and sent to RESTful endpoints (not WSDL) backed by Spring MVC or Spring Data REST. And the discoverability promised by UDDI is now increasingly being implemented with HATEAOS. In fact, the one piece of traditional SOA that remains is HTTP

    Reply
  20. فناوری اطلاعات

    ver VMs – they cannot allow an application operations team to just spin up VMs whenever they chose and risk using up all the capacity on their vSphere hosts. At the same time, application teams need the ability to add VMs on demand to scale, add failover, and so on. Thankfully, Application Director provides a way out of this dilemma: it simplifies app provisioning for application teams, yet allows vSphere admins to constrain what those team can do via role-based privileges.

    5. Simpler web services: At JavaOne shows a decade ago

    Reply
  21. انتشارات و تحقیقات

    s need the ability to add VMs on demand to scale, add failover, and so on. Thankfully, Application Director provides a way out of this dilemma: it simplifies app provisioning for application teams, yet allows vSphere admins to constrain what those team can do via role-based privileges.

    Reply
  22. اخبار سیاسی

    erver, with Spring Insight for application code monitoring, both in development and production, vFabric Admin Server for management, and more.

    4. Simpler ways to provision: Architects are very interested in automatic provisioning of application infrastructure, but there is a challenge: vSphere admins want and need a certain amount of control over VMs – they cannot allow an application operations team to jus

    Reply
  23. بازی های رایانه ای

    4. Simpler ways to provision: Architects are very interested in automatic provisioning of application infrastructure, but there is a challenge: vSphere admins want and need a certain amount of control over VMs – they cannot allow an application operations team to just spin up VMs whenever they chose and risk using up all the capacity on their vSphere hosts. At the same tim

    Reply
  24. اخبار بین المللی

    1. Simpler application servers: One of the most common scenarios we are hearing is where people are running Spring workloads on WebLogic or WebSphere. They’re asking themselves why they’re spending so much in licensing costs to run these workloads, and torturing themselves with high levels of complexity. They’re looking for a more cost-effective and simple way to run Spring Java and are intrigued by how tc Server can help. One company told us they are running over 1000 unique custom apps, and even simplifying a percentage of those applications would have enormous value.

    Reply
  25. مجله خبری ویدئویی

    5. Simpler web services: At JavaOne shows a decade ago, we’d often talk about what could be now called traditional SOA, which focused on XML, SOAP, WSDL, UDDI, etc. Today, the architects we talk to are opting for simple SOA: requests created in JSON, not XML, and sent to RESTful endpoints (not WSDL) backed by Spring MVC or Spring Data REST. And the discoverability promised by UDDI is now increasingly being implemented with HATEAOS. In fact, the one piece of traditional SOA that remains is HTTP – itself a relatively simple protocol.

    Reply
  26. اموزش برنامه نویسی

    4. Simpler ways to provision: Architects are very interested in automatic provisioning of application infrastructure, but there is a challenge: vSphere admins want and need a certain amount of con

    Reply
  27. گاد سرور

    1. Simpler application servers: One of the most common scenarios we are hearing is where people are running Spring workloads on WebLogic or WebSphere. They’re asking themselves why

    Reply
  28. تابلو سفالی

    woooooooow think well good

    Reply
  29. زناشویی

    Bookmark this page and come back to it later to automatically re-ping.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

*