- Developer Tools
Angie Hirata, January 3, 2012SHARE THIS:
For the past few months, as we've been talking to large enterprises about Stackato and their private PaaS plans, some interesting IT strategies have emerged around the role of languages like Python, Ruby, and PHP play in the mix with Java.
As most people know, Java applications dominate the landscape in large enterprise. But as corporate IT departments are planning private PaaS implementations, what strategy are they taking regarding languages and data services?
Option 1: Java First
On the one hand, some are focusing first on Java to support the primary language amongst their developers. In these companies, Java is the primary language for legacy mission-critical applications. Often, other languages like Python and Perl were not used as much in legacy applications, or not viewed to be strategic languages for mission-critical languages. So in some large organizations, even if up to 25% of their applications use another language like Python or Perl, these organizations are implementing a PaaS for Java first with the idea of getting the majority at the first stage.
Option 2: Next-Gen Languages to Get Buy-In
However, some companies are taking a different strategy in order to get greater internal buy-in and adoption of their private PaaS. Even though most current applications may be written in Java, they feel that the younger generation of developers are using, or prefer to use, other languages like Python, Ruby, and PHP, and are demanding that IT support these options. Since the younger developers are also the ones that are more likely to try a new internal service like a PaaS for deploying and managing their applications, corporate IT groups are focusing on getting their adoption first. And the Java crowd will follow. Likewise, in addition to supporting traditional databases like Oracle and DB2, these corporate IT groups want to be able to offer next-generation data services like MongoDB to show the flexibility and options that an internal PaaS can provide. This puts corporate IT in a position of giving the customer (internal developers) what they want in order to satisfy their demands today, get early buy-in, and set-up for success tomorrow.
So which strategy are you taking, and why? Share your comments!
Trackback URL for this post: