The Web on Windows
Download as PPTX, PDF0 likes461 views
This document discusses the past, present, and future of server-side web development on Windows. It describes how server-side scripting was initially used to generate markup on the server. Frameworks like ASP.NET were introduced to bridge differences between web and application development, though they remained focused on server-side rendering. More recently, frameworks have embraced approaches like separating data, logic, and presentation inspired by Ruby on Rails. The document argues that Microsoft's new Helios project represents the future of ASP.NET by adopting an asynchronous, middleware-based approach like Node.js while retaining integration with IIS and existing .NET programming models.
More Related Content
What's hot (9)
Similar to The Web on Windows (20)
More from Josh Lane (7)
Recently uploaded (20)
![Pixologic ZBrush Crack Plus Activation Key [Latest 2025] New Version](https://cdn.slidesharecdn.com/ss_thumbnails/fashionevolution2-250322112409-f76abaa7-250428124909-b51264ff-250504160528-fc2bb1c5-thumbnail.jpg?width=560&fit=bounds)
The Web on Windows
- 1. Consulting/Training The Past, Present, and Future of Server-Side Web on Windows
- 4. Consulting/Training Server-side scripting (VBScript, JScript), XML/XSLT, etc. Generate markup on the server, push to client Relatively little work happening in the browser
- 5. Consulting/Training Skillset mismatch between application dev and web dev (languages, statefulness, etc.) Interpreted execution, synchronous I/O… bad perf and scale “Your markup chocolate got in my app logic peanut butter”
- 8. Consulting/Training Page-based forms over data metaphor “unified” application and web development Still generating markup on the server Still not much happening in the browser
- 9. Consulting/Training Increasing web app sophistication pushed boundaries of the framework Forms over data metaphor not always desirable Law of Leaky Abstractions
- 10. Consulting/Training And so we got a few modest improvements
- 12. Consulting/Training And some slightly more ambitious ones
- 14. Consulting/Training Utilize latent CPU cycles on the client Improve the user experience Maintain a developer upgrade path
- 15. Consulting/Training Plug-in based app model died on the vine Canned AJAX behaviors performed poorly, unattractive relative to newer options Microsoft zigged, the world zagged
- 16. Consulting/Training Then, a bit of a reset
- 18. Consulting/Training Borrowed from Rails (and Smalltalk, etc.) to achieve formal separation of data, logic, and presentation Back to generating “real” HTML Still integrated with core ASP.NET pipeline
- 19. Consulting/Training Still (mostly) about server-side markup generation Still drags around legacy ASP.NET (Web Forms is still in your AppDomain!) Heavyweight, prescriptive model
- 20. Consulting/Training Meanwhile, the world moved on
- 22. Consulting/Training So more recently… a few nods to reality
- 25. Consulting/Training Modern web stack is static HTML + JS + CSS + JSON Web API is great, but by default I get System.Web.dll too <sadTrombone />
- 26. Consulting/Training Do I Really Need ASP.NET Anymore?
- 29. Consulting/Training Fast, scalable network server - hosts V8 JavaScript engine Simple model: lite EXE host + JS libs you choose + your code
- 30. Consulting/Training Vibrant ecosystem: routing, view engines, security, data access, etc. Multi-core concurrency is achieved via multiple processes, not multiple threads
- 31. Consulting/Training All I/O is non-blocking, uses internal thread pool Non I/O-based request processing occurs on a single threaded event loop, with minimal per-request allocation
- 34. Consulting/Training So, node is great for two main reasons: Async I/O ensures high scale Event loop model helps ensure minimal memory allocation per request
- 35. Consulting/Training So it’s settled, then? Node wins?
- 36. Consulting/Training The <ahem>Empire</ahem> Is Striking Back
- 37. Consulting/Training Host Server Middleware Application OWIN and Katana owinhost.exe IIS YourApp.exe System.Web WCF HttpListener Web API SignalR YourWare Task Invoke(IDictionary<string, object>) Task Invoke(IDictionary<string, object>) Task Invoke(IDictionary<string, object>) IDictionary<string, object>
- 40. Consulting/Training Helios is an OWIN-compatible network server Helios requires IIS, but does not run in the context of System.Web* Helios can run outside of OWIN proper
- 41. Consulting/Training Take the good parts of ASP.NET (pluggable programming models, async, IIS integration, etc.) Leave behind the bad parts (System.Web monolith, weird stuff like 401 302, etc.)
- 42. Consulting/Training Borrow liberally from node (async by default, extension via middleware, minimal ceremony, etc.) Still utilizes thread-based concurrency vs. node’s event loop model
- 43. Consulting/Training Doesn’t support higher-order models like MVC (may or may not ever support these) Cannot reference ASP.NET pipeline intrinsics… HttpRuntime, HostingEnvironment, etc.
- 44. Consulting/Training In several important ways, Helios is “node.net” Almost certainly represents the future of ASP.NET
- 45. Consulting/Training Introducing… the HAIR stack (?) Helios – AngularJS – IIS - RavenDB
- 46. Consulting/Training How to satisfy two core constituencies? How to foster node’s third-party module community for Helios? Node’s appeal: simple, opt-in dev model? Or is it JS on the server? Implications for ASP.NET?