We have been repeatedly reminded that the requirements of hyper-scale cloud properties are different from those of the mainstream enterprise, but I am now beginning to suspect that the top strata of the traditional enterprise may be leaning in the same direction. This suspicion has been triggered by the combination of a recent day in NY visiting I&O groups in a handful of very large companies and a number of unrelated client interactions.
The pattern that I see developing is one of “haves” versus “have nots” in terms of their ability to execute on their technology vision with internal resources. The “haves” are the traditional large sophisticated corporations, with a high concentration in financial services. They have sophisticated IT groups, are capable fo writing extremely complex systems management and operations software, and typically own and manage 10,000 servers or more. The have nots are the ones with more modest skills and abilities, who may own 1000s of servers, but tend to be less advanced than the core FSI companies in terms of their ability to integrate and optimize their infrastructure.
The divergence in requirements comes from what they expect and want from their primary system vendors. The have nots are companies who understand their limitations and are looking for help form their vendors in the form of converged infrastructures, new virtualization management tools, and deeper integration of management software to automate operational tasks, These are people who buy HP c-Class, Cisco UCS, for example, and then add vendor-supplied and ISV management and automation tools on top of them in an attempt to control complexity and costs. They are willing to accept deeper vendor lock-in in exchange for the benefits of the advanced capabilities.
I don’t understand why firms spend millions of dollars on Java application servers like Oracle Weblogic or IBM WebSphere Application Server. I get why firms spend money on Red Hat JBoss -- they want to spend less on application servers. But, why spend anything at all? Apache Tomcat will satisfy the deployment requirements of most Java web applications.
Your Java Web Applications Need A Safe, Fast Place To Run
Most Java applications don’t need a fancy container that has umpteen features. Do you want to pay for a car that has windshield wipers on the headlights? (I wish I could afford it.) Most Java applications do not need these luxuriant features or can be designed not to need them. Many firms do, in fact, deploy enterprise-class Java web applications on Apache Tomcat. It works. It is cheap. It can save tons of dough.
Expensive Java Application Servers Sometimes Add Value
There is a need for luxury. But, you probably don’t need it to provide reliable, performant, and scalable Java web applications. Application server vendors will argue that:
You need an application container that supports EJBs. EJB3 fixed the original EJB debacle, but why bother? Use Spring, and you don’t need an EJB-compliant container. Many applications don’t even need Spring. EJBs are not needed to create scalable or reliable applications.
There has been turmoil and angst recently in the 0pen source community of late over Oracle’s decision to cancel OpenSolaris. Since this community can be expected to react violently anytime something is taken out of open source, the real question is whether this action has any impact on real-world IT and operations professionals. The short answer is no.
Enterprise Solaris users, be they small, medium or large, are using it to run critical applications; and as far as we can tell, the uptake of OpenSolaris as opposed to Solaris supplied and sold by Sun was very low in commercial accounts, other than possibly a surge in test and dev environments. The decision to take Solaris into the open source arena was, in my opinion, fundamentally flawed, and Oracle’s subsequent decision to change this is eminently rational – Oracle’s customers almost certainly are not going to run their companies on an OS that is built and maintained by any open source community (even the vast majority of corporate Linux use is via a distribution supported by a major vendor and under a paid subscription model), and Oracle cannot continue to develop Solaris unless they have absolute control over it, just as is the case with every other enterprise OS. In the same vein, unless Oracle can also have an expectation of being compensated for their investments in future Solaris development, there is little motivation for them to continue to invest heavily in Solaris.
Open source software (OSS) and business intelligence (BI) are two related market segments where Forrester sees continually increasing interest and adoption levels. BI specifically continues to be one of the top priorities on everyone's mind. The main reason? Enterprises that do not squeeze the last ounce of information out of their data stores and applications, and do not focus on getting strategic, tactical, and operational insight into their customers, products, and operations, risk falling behind competition. And when it comes to open source, 2009 could best be described as "the year IT professionals realized that open source runs their business." The reason is simple: Over the past few years, we've seen that developers adopt open source products tactically without the explicit approval of their managers. This has shown up in numerous surveys where the actual adoption of open source ranks higher than what IT managers report. Well no longer: Forrester's Enterprise And SMB Software Survey, North America And Europe, Q4 2009 shows that management has caught on to the fact that developers increasingly use open source to run key parts of their IT infrastructure. And management has grown increasingly comfortable with it. In fact, throughout 2009, most client inquiries Forrester received regarding open source were focused on how to move from tactical adoption to strategic exploitation.
Yet, when you put the 2 and 2 together (OSS and BI), you mostly get a mixed market, where one unfortunately has to compare apples to oranges. Why? Before plunging into a tool evaluation and selection process, ask yourself the following questions, and make sure you are doing a like-to-like comparison:
Sikka made two comments that indicate how he's thinking about the NetWeaver portfolio.
1. In response to my question about whether SAP is concerned that Oracle's ownership of Java will put it at a disadvantage, Sikka started by highlighting SAP's work on Java performance, but then noted the availability of good open-source Java software to support the requirements of SAP customers.
I want to develop a Web application - a really good Web app. The kind of Web app that will make me so rich that I can buy an $9.4 million co-op over looking Central Park, a Yacht registered in Monaco, and hire an architect to build my dream-house west of Boston that is a combo of Buckminster Fuller, FLW, and MTV cribs.
I just spent the day at Progress Software's annual analyst day. The highlight of the event is, always, to hear from their customers about how they are getting real things done. This year we heard from: EMC, Sallie Mae, TD Securities, Royal Dikzwager, BT Global Services, Lincoln Financial Group, Sabre Holdings, and Fiserv.
The theme: High velocity business demands high velocity technologies such as complex event processing, enterprise infrastructure, data infrastrcuture, and others.
But, this post is about Kenneth Rugg, VP and GM of Integration Infrastrcuture for Progress Software, comments on open source software.
Consistently rated as one of the most popular features of Forrester Events, one-on-one meetings give you the opportunity to discuss the unique technology issues facing your organization with Forrester analysts. Business & Technology Leadership Forum attendees may schedule up to two 20-minute one-on-one meetings with the Forrester analysts of their choice, depending on availability. Registered attendees will be able to schedule one-on-one meetings starting on Monday September 15, 2008. Book early!
The Dark Knight is chock full of memorable quotes and, dare I say, advice from none other than the Joker, a role played eerily, crazily, and fabulously by the late Heath Ledger. One of the many quotes that stuck with me is "If you are good at something, never do it for free." This is pretty good advice, especially when you are proposing to "Kill the Batman" in exchange for half of the mob's money. It worked for the Joker. He got the job.
But, is this advice good for software developers?
On the surface it seems silly to even ask the question. Why would anyone want to work for free? But plenty of people donate their time and talent to causes great and small in an effort to help people and to benefit humanity. That is a good thing. But, is this in fact good advice for open source software developers? To answer this question we need to know what motivates them and what they hope to gain.
Software developers contribute to open source projects for many different reasons.