|
|
 |
|
|
|
Coming Events |
| Tuesday, August 03, 2010 |
| Oxford - Making an Exception |
| Monday, August 09, 2010 |
| Hereford - Azure Table Service - NoSQL |
| Monday, August 09, 2010 |
| Coventry - Entity Framework 4 |
| Tuesday, August 17, 2010 |
| Birmingham - I've Got A Little jQuery ... |
| Wednesday, August 18, 2010 |
| Manchester - An Introduction to F# |
|
|
|
|
Member Quotes |
| Richard Costall |
| Good session from Alex, not sure where the tool is going, but makes you consider how you should be building applications and implement health monitoring. |
| Colin Newell |
| The only real problem with the talk was demonstrating something that won't be around for long. |
| Raymond Starkey |
| This guy is great - you would pay top dollar in the City to hear him - no small wonder Microsoft grabbed him. |
| Dan Maharry |
| My first NxtGenUG meeting. A pleasant surprise and I look forward to attending more |
|
|
|
Event Resources |
|
|
| |
|
|
|
Conferences |
|
|
Mix10 |
|
Partner Showcase |
|
|
ORCSWeb is one of the premier ASP.NET 2.0 and SQL 2005 hosting companies, and also the home of the NxtGenUG Site. |
|
|
|
|
|
|
 |
|
|
 |
|
 |
|
|
| Event Breakdown |
|
|
|
| Alex Homer
|
Building Manageable Applications - Designing for Operations |
Modern automobiles have become so complex that they require more computing power than that of the average desktop computer from of a few years ago. So what happens when it goes wrong? Usually, an engine-shaped red light is all the "user" sees. This basically means: "drive to your nearest dealer and let them fix whatever has failed." The dealer plugs the car into another computer, which prints out reams of data about the system events, performance, and status. They immediately know that they just need to fit a replacement knurdle widget and it will all work fine again. Do your applications behave like this? When they go seriously wrong, does the user just see an error message saying "Sorry, something failed, please contact your system administrator"? That's fine, but what does the system administrator do next? Do you provide them with the facility to extract useful information that will help them to locate the fault and fix it? Or do they have to run the application themselves and try to figure it out from experience? Or maybe they simply phone the development team and say "It's broken again..."?
Studies show that the most significant costs for modern distributed applications occur during the operational phase. On average, implementation and installation account for only around 20 percent of the total lifetime cost. The remaining 80 percent is the cost of deploying, maintaining, and managing a complex application. Architects and system designers can use the Team System Management Model Designer Power Tool (TSMMD) to generate a model of an application that contributes to a minimized TCO. The TSMMD also assists developers to implement the required instrumentation and create management packs for monitoring systems, such as Microsoft System Center Operations Manager 2007. OK, so it sounds boring, but it could change the way you think about designing and implementing exception handlers, and it even writes the code for you!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 |
|
 |
|
|