Dont use services unless you necessarily need them

Posted by: Pablo M. Cibraro (aka Cibrax), on 14 May 2011 | View original | Bookmarked: 0 time(s)

There are multiple factors or requirements that might lead you to refactor some functionality into services. Here are some examples, You have explicit requirements to distribute work across machines. This is a typical example of smart client applications (i.e. Silverlight apps), which runs a thin UI layer and have all the backend logic as part of services. You need to run code remotely in a specific machine, so a good choice is to expose that as a service.   You need to expose...

Similar Posts

  • Idle Timeouts in RIA Services Authentication more
  • 12 ASP.NET MVC Best Practices more
  • Migrating to Postgresql with my friend NHibernate more
  • Formatting Text in RadControls for WinForms Q3 2009 more
  • SharePoint Conference 2009 more
  • Visual Studio 2010 Beta 2 and Silverlight updates more
  • Creating a Filtering User Interface With jQuery In a Web Forms Application: Part 1 more
  • Deleting All Records In a Table EXCEPT For the N Most Recently Added Records more
  • Exporting SWF & FLV format reports in SSRS 2005 and 2008 more
  • A proposed introduction... more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD