Exchange 2010 goes into General Availability today. If you want to follow announcements and the technology check out the TechEd Europe 2009 press room for sessions and keynotes.
Microsoft Announces Exchange Server 2010 Availability and Wave of Innovations at Tech•Ed Europe 2009: Exchange 2010, Windows 7 and Windows Server 2008 R2 help customers realize better productivity, efficiency and potential cost savings up to 70 percent.
Nov 9, 2009
Nov 5, 2009
Judge jettisons lawsuit challenging Gartner's Magic Quadrant | NetworkWorld.com Community
It's all a matter of opinion, even when the opinion is very influential.
Judge jettisons lawsuit challenging Gartner's Magic Quadrant | NetworkWorld.com Community
In essence, this case boiled down to a question of whether the Magic Quadrant is an objective presentation of quantifiable facts, or -- as Gartner argued and should be obvious to all -- simply Gartner's opinion based on its research.
Judge jettisons lawsuit challenging Gartner's Magic Quadrant | NetworkWorld.com Community
Nov 4, 2009
Design Criteria Defaults: SaaS
Yesterday I wrote about vendors making mobility a primary design criteria when developing collaboration platform interfaces, today I want to focus on the SaaS.
Still in it's 20o9 rage, the Cloud continues to pose issues for customers and vendors alike. Since late 2006 we've seen traditional software vendors, including IBM, Microsoft, Oracle, and Cisco, throw their hat and products into the Cloud and offering SaaS-based delivery of many of their popular solutions. Spurred on by Google's ambitions in the the enterprise market, each vendor has come up with their own approach to SaaS and the Cloud. Some have made it out of beta to deliver ready for prime time offerings (Microsoft Online, LotusLive), some have pulled back to only providing private offerings (Oracle), others are emerging through building on top of consumer-based acquisitions (IBM Lotus and Cisco), and others are working on configuring the right architecture (Cicso).
Bottom line, updating existing products and systems and building a hosting operation is not simple. It's not easy to transform an installed, on-premise system - like e-mail or collaboration - into a multi-tenant, scalable, and secure SaaS offering. The migration of back-end servers to support larger loads and parsing out multiple domains can take time. Once that's in place modifying other supporting services like Directory or Search to support the complex security and permissions also takes time. Finally, designing the presentation layer to provide secure functionality also requires a change in attitude and development assumptions.
As with mobility, vendors need to consider hosting capabilities as an primary design criteria for all new system software. Microsoft has done well in coming closer to this goal in its SharePoint and Office 2010 designs, but still some of their forthcoming BI servers are still treating the hosting part as a follow-on job. IBM Lotus on the other hand appears to be approaching things differently, developing on-premise solutions separately from it's LotusLive offerings, many of which consist of acquired hosted products like Outblaze's e-mail or the Unyte hosted meetings.
It's not a foregone conclusion that all on-premise platforms need to be retro-fitted or upgraded for SaaS delivery. Designing for hosting will likely help in the integration department and make hybrid on-premise/Cloud delivery easier for both the vendor and the customer.
Still in it's 20o9 rage, the Cloud continues to pose issues for customers and vendors alike. Since late 2006 we've seen traditional software vendors, including IBM, Microsoft, Oracle, and Cisco, throw their hat and products into the Cloud and offering SaaS-based delivery of many of their popular solutions. Spurred on by Google's ambitions in the the enterprise market, each vendor has come up with their own approach to SaaS and the Cloud. Some have made it out of beta to deliver ready for prime time offerings (Microsoft Online, LotusLive), some have pulled back to only providing private offerings (Oracle), others are emerging through building on top of consumer-based acquisitions (IBM Lotus and Cisco), and others are working on configuring the right architecture (Cicso).
Bottom line, updating existing products and systems and building a hosting operation is not simple. It's not easy to transform an installed, on-premise system - like e-mail or collaboration - into a multi-tenant, scalable, and secure SaaS offering. The migration of back-end servers to support larger loads and parsing out multiple domains can take time. Once that's in place modifying other supporting services like Directory or Search to support the complex security and permissions also takes time. Finally, designing the presentation layer to provide secure functionality also requires a change in attitude and development assumptions.
As with mobility, vendors need to consider hosting capabilities as an primary design criteria for all new system software. Microsoft has done well in coming closer to this goal in its SharePoint and Office 2010 designs, but still some of their forthcoming BI servers are still treating the hosting part as a follow-on job. IBM Lotus on the other hand appears to be approaching things differently, developing on-premise solutions separately from it's LotusLive offerings, many of which consist of acquired hosted products like Outblaze's e-mail or the Unyte hosted meetings.
It's not a foregone conclusion that all on-premise platforms need to be retro-fitted or upgraded for SaaS delivery. Designing for hosting will likely help in the integration department and make hybrid on-premise/Cloud delivery easier for both the vendor and the customer.
Design Criteria Defaults: Mobility
A few weeks ago I wrote and article for SearchDomino on IBM Lotus' continued expansion into mobility. One of my predictions was that we'd "see increased dedication from IBM Lotus and other vendors to make designing for mobility a primary consideration when building future versions of software tools." As my article points out, the current state of the mobile device OS market means that are lots of moving parts for vendors to keep track of and strategic partnerships appear to be the preferred approach for vendors when tackling mobility. Recent smartphone developments are swaying the market to the downloaded, device-specific application model (which vendors have to address on a platform-by-platform basis) rather than web-based software interfaces optimized mobile browser support (which vendors have more control over).
While IBM Lotus is doubling down on mobility it appears that Microsoft is not, at least not in the collaboration arena. Having just returned from Microsoft's SharePoint Conference, little focus was spent on mobility. The one session I attended on mobility consisted of an advert for the latest Windows Mobile version and a look at .NET APIs for making mobile applications. Using SharePoint on a mobile device is still, even in the 2010 release, relegated to adding a "/m" to the end of a SharePoint URL. Considering the promise of SharePoint 2010 as a content management and reach collaborative solution, it is likely that many users will find typing long URLs into mobile browsers sub-optimal.
Dedication to designing for mobility is one thing, execution is another. Mobility should be part of the design process in the earliest stages these days. IBM Lotus has revealed their mobility intentions and now it remains to be seen how they will execute. Microsoft has yet to take a stand on mobility for it's next generation of productivity and collaboration tools.
While IBM Lotus is doubling down on mobility it appears that Microsoft is not, at least not in the collaboration arena. Having just returned from Microsoft's SharePoint Conference, little focus was spent on mobility. The one session I attended on mobility consisted of an advert for the latest Windows Mobile version and a look at .NET APIs for making mobile applications. Using SharePoint on a mobile device is still, even in the 2010 release, relegated to adding a "/m" to the end of a SharePoint URL. Considering the promise of SharePoint 2010 as a content management and reach collaborative solution, it is likely that many users will find typing long URLs into mobile browsers sub-optimal.
Dedication to designing for mobility is one thing, execution is another. Mobility should be part of the design process in the earliest stages these days. IBM Lotus has revealed their mobility intentions and now it remains to be seen how they will execute. Microsoft has yet to take a stand on mobility for it's next generation of productivity and collaboration tools.
Oct 22, 2009
Mobility in Domino article
Just published: Lotus makes mobile partnership and Notes Traveler top priorities
Another SearchDomino article by your narrator.
Subscribe to:
Posts (Atom)