This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Beantown.NET Tonight - Phil Stanhope on OCC
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
The Downtown Boston.NET User Group is proud to present Phil Stanhope of Addesso Systems speaking about Occasionally Connected Computing Architectures.
There have been 3 distinct application architectures over the past 30 years -- and, despite conventional wisdom, these architectures have NOT been driven by the evolution OO technologies or the latest buzzword of SOA. Rather, application architectures have been driven at a fundamental level based on networking technologies. A 4th application architecture is emerging and the phrase that we use to describe it is Occasionally Connecting Computing (OCC). OCC programs and services display many of the (best) attributes and design patterns of both client/server, web-centric, and service-oriented architectures.
This talk will take us through a history of the evolutions that have occured over the past 30 years and highlight some of the critical decisions architects, designers, engineers, and administrators need to consider when deploying the next-generation of software applications.
Phil Stanhope is vice president of Technology and Alliances for Adesso. Before joining Adesso, he served in several capacities for Perot Systems since 1996. While at Perot Systems, he advised clients such as Groove Networks, KPMG, and BoardWare. He was a founder and executive vice president of TimeØ, a company acquired by Perot Systems. While at Perot Systems he also was acting Chief Technology Officer for Transportation Zone International (“TZI”), and Chief Executive Officer of TXZ Holding Corporation Limited. Prior to joining Perot Systems, he was co-founder of Cambridge Object Technologies Inc. Before that, he co-founded Lotus Development Corporation’s Next Generation Product Group (NextGen), and was Chief Architect with responsibilities including the strategic planning, design and development of Lotus Components. Earlier, he worked in knowledge representation,expert systems, and other areas for companies including Palladian Software, Gold Hill Computers Software Productivity Research and the Experimental Knowledge Systems Laboratory.
Previous Topic
