The most challenging aspect of developing mobile applications is developing the mobile middleware and synchronization technology. Some companies, like Sybase, have spent decades and vast resources developing and perfecting mobile databases and synchronization technologies. To be sure, this component of a mobile solution is much more complex than most people can imagine.
- How do you resolve a synchronization conflict between several mobile users that are simultaneously synchronizing different data with the same enterprise database field? What data is the most valid?
- What happens when data from the enterprise database is synchronized to the mobile smartphone database, but quickly changes or is edited in the enterprise? The mobile device is now using old database structures or outdated data. How can the mobile device synchronize data now? How does the mobile device application know the enterprise database has changed?
- How do you optimize a synchronization engine to handle 400 mobile devices synchronizing large quantities of data wirelessly at 8 AM and 5 PM every day?
These common issues explain the underlying complexity inherent in Sybase’s approach to mobile middleware. Sybase’s approach requires an intermediary or staging database to accommodate a connected or disconnected working environment. This is needed in many rugged working environments where internet connectivity is not always available. However, many smartphone users are now finding themselves always connected. For these users the need for heavy mobile middleware, with complex synchronization and staging databases, is no longer warranted. Smartphone users that work in always connected environments can use a much simpler and real time strategy for connecting with back office ERPS and business applications. The TCO (total cost of ownership) for these simple and real time connections is far less than those requiring staging databases.
This said, SAP’s announced intent to acquire Sybase and their Sybase Unwired Platform (mobile middleware and synchronization technology) comes as a relief to many enterprise mobility vendors that had previously developed their own mobile middleware. Why? Because they can now focus their attention on those mobile applications that provide tangible value, rather than reinventing mobile middleware that so many people take for granted.
Without the need to build their own mobile middleware, enterprise mobility companies will be able to provide a lower TCO for mobile applications. There will be fewer bugs, less risk and more efficient implementations due to SAP’s standardization around the Sybase Unwired Platform.
For enterprises looking to take advantage of enterprise mobility, especially those with significant SAP footprints, this simplifies the decision-making process, for now the choice of a mobile application vendor is not a choice of applications and yet another platform, but one of applications that will be compatible with the SAP-Sybase combination. In the near future, it is fair to expect a significant upsurge in the number and quality of mobile applications available to enterprises that will satisfy this requirement. Let the games begin!



