Architecting For The Client


Published on

Slide deck from the Austin/Houston/Dallas ArcReady events.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Clientvs CloudTrajectoriesWhy?Diversity of needs.What’s next?
  • We’ve talked a LOT about the cloud and the services part of Software Plus Services.But something’s got to interface with that cloud.By definition that’s the client.But unfortunately it’s not that clear cut.
  • Picture is the House of the Future exhibit in the Redmond Executive Briefing center. This was the proofing ground for a lot of the concepts in the video.
  •’s Veal stock, BTW)So let’s reduce it down just a bit.
  • – when general systems started out, all you had was storage. No processor, no interface, just your data and instructions.Architecture was based on “Systems” and included such factors as floor loading and chilled water capacity. Systems talked asynchronously through “Batches” (stacks of cards) and runtimes could measure in weeks.
  • next generation, we had flipped the equation. All you had was (limited) processor and display/keyboard. All your instructions and data were kept elsewhere (where you generally couldn’t get to it except with greenbar.) Architecture moved out of the power and water space and into how systems talked with each other. EBCIDC is the interoperability standard of the day.
  • the personal computer revolution happened and everything changed. You could have all three resources together, processing power, display/IO, and storage. Connectivity started appearing for users as well.ASCII became dominant in the new area, Architecture evolved into the interface between how hardware and software worked together as well as how systems connected and operated together.
  • first started to glimmer – you had everything local, remember? (well except for power)
  • the world changed and the GUI came into public use. (The wild late 80’s.) Processors got faster – with a high end of 7.14Mhz and improvements that rapidly made that the low end. Memory expanded explosively - most systems started at 1MB and memory expansions were some of the hottest selling peripherals. Most people are still working with some form of this paradigm. Storage swelled explosively with the introduction of 5, 10, and 20 MB hard drives for less than $1K.
  • the mainframe came back as the Server side of Client/Server. Clients could perform functionality but were generally tightly coupled to specific servers.
  • And then the web happened – and we were back into the world of CICS – and semi-dumb terminals. HTML provided formatting, but little local functionality.
  • But pages and applications got better and we started moving forward again with local code – mostly script and dynamic again.
  • mobile happened – remember that first “laptop?” Mobility comes into it’s own, but again, the experience changed dramatically.
  • (SxSW lounge)But today things are changing further. Devices are moving from multi-touch to multi-user. Interfaces are becoming multi-dimensional. All this requires resources, and more importantly requires hardware level access. Sensors and I/O are critical.
  • (Office Labs photo)And the change is accelerating rapidly. The WIMP interface won’t be extinct, but it is in the process of being augmented by a wealth of interfaces to supplement it, all enabled by hardware advances in power and cost.
  • the interface race doesn’t stop with the
  • Manufacturing Vision video. Note the different ways people are using their local environment to access and work with their data.
  • Clientvs CloudTrajectoriesWhy?Diversity of needs.What’s next?
  • client has been declared dead since before it really existed. But as we can see today, it’s still around and learning new tricks. Desktop Mashups with Gadgets, search connectors, jump lists, edge snapping. Architecturally show that all this is simple to consume or base your own apps on.
  • is still relevantDrivers require the clientWho doesn’t have wires? Really?External storage, custom mice or I/O
  • the realtors say, Location, Location, Location.GPS, network awareness, Video recognition, etc. All require client software. Sensors are high value – accelerometers, thermometers, RFID readers, etc.
  • – Who has enough?Key factors in client is managing and working with files. Storage has increased from 10MB to 2TB in less than 20 years. It isn’t going to stop increasing.Could show BumpTop or WinBlinds here – easier demo is to show tagging, libraries, views, and searches in Win7.
  • Let’s start with Graphics.DirectX is HUGELY powerful. A greatly underappreciated framework.Is the primary reason why PC’s are still the top tier gaming platform.Used not just for graphics, but for sound and I/O. Makes huge amounts of functionality possible.
  • Master Chief wants to remind you that DirectX was instrumental in defeating the Covenant.
  • Bumptop.comBumpTop uses DirectX and the Windows 7 foundations to provide advanced experiences and functionality for users.Completely different user experiences can use the foundation and change things up. Installer is in the mesh, demo on the TouchSmart if you have it at your event.
  • working with Direct X has a LOT of moving parts. With great power comes great complexity.
  • WPF was the response to the growing stack of functionality Simplifying layout and graphics.Take advantage of deep hardware integration.Divide the “How” from the “What” (ie, designer from developer)
  • install.Auto updatesEasily skinnableAsynchronous functionality.Uninstall after each talk to show the XBAP.Alternate demo could be any XBAP app – WittyTwitter is another that is useful to show.
  • Silverlight is that next step – bringing the client to the browser and to Mesh.Show the Mesh Dev Client – same application installed on the Mesh client as installed in the browser. Data synched everywhere.
  • Architecting For The Client

    1. 1. ArcReady: Architecting for the client
    2. 2. And now a word from our Sponsor….
    3. 3. Are you a technology start-up? BizSpark is an innovative new program that unites Startups with entrepreneurial and technology resources in a global community with a common goal of supporting and accelerating the success of a new generation of high-potential Startups.
    4. 4. Microsoft Developer Tools Promotions …ending June 30th, 2009 Contact your local Microsoft Developer Tools Representative for more details… Midwest and North Central Jerry Flynn (314) 872-5919 Heartland and South Central Rachel McKane (469) 775-6125
    5. 5. ArcReady: Architecting for the client
    6. 6. About Me Phil Wheat Architect Evangelist blog:
    7. 7. About ArcReady… • A forum for aspiring and practicing architects to discuss industry trends • An overview of Microsoft’s roadmap as it relates to software architecture • A mechanism to solicit your feedback • An opportunity to showcase the work you do!
    8. 8. Discussion Encouraged
    9. 9. Client Tier Processors and memory and storage, Oh My!
    10. 10. Break Return in 10
    11. 11. Session 2 The Differentiators of the Client
    12. 12. WPF Vision • Unified approach to UI, Documents, and Media – Integration as part of development and experience • Integrated, vector-based composition engine – Utilizing the power of the PC throughout the graphics stack • Declarative programming – Bringing designers directly into application development • Ease of deployment – Allowing administrators to deploy and manage applications securely
    13. 13. What is Silverlight? <MediaElement x:Name=‘myMediaPl ayBack' Canvas.Left='532' Canvas.Top='184' AutoPlay='false' Height='185' Width='350' Opacity='0'> Plug-in with cross < 2Mb Download (1.0) Extends browser browser & capability with OS support XAML
    14. 14. About Me Phil Wheat Architect Evangelist blog: