Microsoft Way

A place

A framework of products

The way you get work done in a Micro Soft shop (contrast Unix Way)


Often Microsoft Way is to build, modify and hopefully improve on what is there. Some examples of their advice taken from their articles are listed here.

For Business Strategies Microsoft Way advocate

don't "Boil The Ocean" - allow architecture to flex and accommodate needs to harness investment requirements and opportunities. (same article above)

"encourage" customers to buy new software by letting them sway in the breeze for a while when the older software needs fixing. Reference at www.eweek.com

They must subscribe to Brains Asa Cheap Commodity theory, they are rounding up talents in mid 2004. see www.eweek.com

Microsoft views on their primary business focus, compared to Big Blue

...A software company first, (compared) ...IBM first and foremost a consulting company...Our focus is how to provide more out-of-the-box solutions that don't require those consulting services....IBM is our single biggest competitor. See www.builderau.com.au

Microsoft is expected to have a make-over, during their next round (Feb05) of meeting with DOJ on anti-trust matters. See www.cio-today.com

In Nov05, months after Ray Ozzie joined MS, the firm is looking seriously into the Business Model of Utility Computing via Microsoft Live. An example of a "free service" can be seen at computerworld.co.nz

See Middle Ware ("Battleground..." section) where Microsoft Way is attempting to drill into the Big Blue money tree, and the response.


Comments on Microsoft's view of Service Oriented Architecture

Sep05 blog by an analyst who had Yankee Group / Aberdeen group experiences, after MS PDC 2005, at blogs.zdnet.com made comments to these effects:

MS focus on the term "Connected Systems" (and its lack of commitment to the general Enterprise Service Bus and opting for Windows Communication Foundation) actually meant the firm is tightening up available interfaces into the Windows platform and locking in customers

MS clients with "deep commitments" will have to pay separately for enterprise wide SOA capabilities

SOA is the art of modeling .. business processes. Went on to say "Business ... processes are .. volatile, ... subject to the judgment and whims of the human actors ..."

My interpretation is that they are arguing for an adaptive (evolving architecture), whereas commonly people equate architecture with blueprint, and one does not generally change blueprint once construction starts. Comments Please

Interoperability between services guided by the implementation of WS-* protocols

Sends Web Services implemented before Dot Net 1.1 to scrapheap??


From the Opposition

MS interoperability being queried at www.theregister.co.uk

(MS2005Feb) security initiatives lacking consideration for heterogenous networks at www.pcworld.com

Get Real.. Upgrade OS to meet security changes not practical at searchwin2000.techtarget.com


Kim Cameron - Security and Identity Management Don Box - Microsoft Indigo Pat Helland - Service Architecture Bob Muglia - Server platform


Also the address of the main Microsoft complex: One Microsoft Way Redmond, WA



See original on c2.com