We recently attended Amdocs' customer event in Singapore. Amdocs is gradually adjusting its strategy to reflect one of the most fundamental changes in the ICT industry today: Increasingly, business line managers, think the marketing or sales officer, are the ones influencing sourcing decisions. Traditional decision-makers, CTOs and CIOs, are no longer the sole ICT decision-makers. Amdocs is addressing this shift by:
Strengthening its customer experience portfolio.Successful telcos will try to regain lost relevance through improved customer experience. Marketing, portfolio product development, and sales are therefore growing in importance for telcos. Amdocs’ integrated customer experience offering, CES 9, provides telcos with a multichannel experience; proactive care; and self-service tools.
Betting big on big data/analytics.Amdocs is leveraging big data/analytics to provide real-time, predictive, and prescriptive insights to telcos about their customers’ behaviour. Communications-industry-specific converged charging and billing solutions as well as other catalogue solutions give Amdocs the opportunity to provide more value to telcos than some of the other players.
Ten years ago, open source software (OSS) was more like a toy for independent software vendors (ISVs) in China: Only the geeks in R&D played around with it. However, the software industry has been developing quickly in China throughout the past decade, and technology trends such as service-oriented architecture (SOA), business process management (BPM), cloud computing, the mobile Internet, and big data are driving much broader adoption of OSS.
OSS has become a widely used element of firms’ enterprise architecture. For front-end application architecture on the client side, various open source frameworks, such as jQuery and ExtJS, have been incorporated into many ISVs’ front-end frameworks. On the server side, OSS like Node.js is becoming popular for ISVs in China for high Web throughput capabilities. From an infrastructure and information architecture perspective, open source offerings like Openstack, Cloudstack, and Eucalyptus have been piloted by major telecom carriers including China Telecom and China Unicom, as well as information and communication solution providers like Huawei and IT service providers like CIeNET. To round this out, many startup companies are developing solutions based on MongoDB, an open source NoSQL database.
Familiarity with OSS is becoming a necessary qualification for software developers and product strategy professionals. Because of the wide usage of OSS among both vendors and end users, working experience and extensive knowledge with OSS is becoming a necessary qualification not only for software engineers, but also an important factors for product strategy professionals to establish appropriate product road maps and support their business initiatives.
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.