Mobile Cloud Services
ToddKaplinger 2700000G7N 1,383 Visits
ToddKaplinger 2700000G7N 1,561 Visits
One of the great things about working at IBM is the how the company continues to evolve and adopt the latest standards especially in the realm of software. When I first started at IBM, I was introduced to the concept of Java in the enterprise as a developer on IBM WebSphere Application Server (WebSphere). WebSphere quickly became one of the market leaders in the industry by driving a set of standards around Java to gave rise to Java Enterprise Edition (JEE). At the same time, we started to see an increased ramp up and adoption of Linux, which quickly became the most popular operating system in terms of install base of WebSphere. To help accelerate Linux, IBM also provided key resources both in terms of technology as well as developer resources to continue to help drive standardizations around Linux. In doing a quick Google search on both “ibm java” and “ibm linux” we find that IBM is considered a leader in both of these technologies with over 60 million and 110 million search results respectively.
Since transitioning from the WebSphere development team, I have shifted my focus to key technology incubation areas around mobile and cloud. In each of these areas we have seen both technologies continue to drive innovation. However, we are now starting to see other technologies emerge in this space. One of the key disruptors forcing these new technologies to emerge in the industry is mobile. Mobile when coupled with cloud starts to create new business models and introduces a whole new class of business opportunities that may not have been realized without mobile. We have seen this first hand with our IBM Mobile Services Technology Preview.
In previous blog entries we went into great detail into our first cloud service IBM Passes. IBM Passes is a traditional JEE Application with a Database persistence tier running in the cloud on Linux. As we started to develop this service, we started to think about how a startup may approach this problem and contrast it with how a traditional IBM development project would.
We are still evaluating the best use cases for these technologies and determining when it makes sense to go to the Java Enterprise Edition route or this lighter weight script driven development model. The industry is aggressively adopting these technologies and we as IBM want to continue to show leadership and help drive standardization in these emerging technologies. In the coming weeks, we will be publishing some of their findings in the form of developerWorks articles as well as new blog entries.