Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jonathan Allen on Feb 28, 2007
Microsoft has released a new tool for bulk converting MS Office files from the older binary format to the Office 2007 format OpenXML. The question is, should you use it?
The tool, called the 2007 Microsoft Office System Migration Guidance: Microsoft Office Migration Planning Manager, is now available from Microsoft.
Some companies may choose to bulk migrate to OpenXML so that they have the confidence that comes from using an open standard rather than the older proprietary format. It should also reduce the duration of the chaotic period where a companies internal documentation is split between multiple formats.
Other companies may choose to stay with the binary format because, despite is proprietary nature, it is widely supported by both Microsoft and non- Microsoft tools including OpenOffice and WordPerfect. Also, a bulk conversion requires the entire company to upgrade to Office 2007 all at once, a boon to Microsoft and the bane of IT departments worldwide.
Not offered by Microsoft is a way to bulk convert to the other new international standard, ODF.
InfoQ Asks: Where are your company's migration plans?
RDBMS to NoSQL: Managing the Transition
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Troubleshoot Java/.NET performance while getting full visibility in production
Automating Error Reporting for .NET Applications
The WebSphere Liberty Profile for Developers: An Introduction
It should be mentioned that in theory, it's not necessary to migrate the whole company to Office 2007 in order to use Open XML files, a free add-in for Office XP and 2003 is available for free download. Whether it'd be wise to upgrade all document but not the software is another question though. Open XML files can contain stuff not supported by older versions (although that's unlikely with documents converted from those version), and open/save performance is lower.
Funny that you should mention bulk migration to ODF. Who in their right mind would consider a lossy bulk-migration? Migration to ODF should always be followed by manual reviews for every individual file. (Unless you convert only text files and don't care much about formatting.)
Surely any bulk migration should be followed by manual reviews, at least of key documents, regardless of the target format?
to a degree, of course. i would not throw away the original documents in any case, and yes, key documents always need reviewing (especially spreadsheets).
that said, i would risk migrating a whole server share to OpenXML, and manually deal with problems reported by users. i have yet to find a document that doesn't convert nicely, so there shouldn't be many of them. and after all, there's a risk with upgrading even if you don't convert the files. given the nasty nature of those old binary formats, some documents might not open at all (I had one of those cases, at least they would be reported by a migration tool up-front and you can fix them from a PC with an older version of office installed).
if you ever looked at files migrated from binary MS office to ODF (no matter which tool you used for conversion), there are just too many differences as to even try it. it makes no sense to wait for problem reports if you know that, say, 50% of your documents are affected (depending on the kinds of documents you have).
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
3 comments
Watch Thread Reply