Best practices for Web services: Part 1, Back to the basics. The cloud of technologies being developed to deliver on the promise of web services has (in our opinion) finally reached a point of maturity that allows us to start moving beyond the initial hype and excitement into actual down-and-dirty implementation.
In April 2002, Google announced that it would enable developers to query more than 2 billion web documents directly from their own applications using WSDL and SOAP technologies; if nothing else, this demonstrates that the idea of using web services to deliver real-world applications has seriously begun to take root in the minds of developers. Indeed, at many of our customer service engagements, we are witnessing a trend: Customers, and not evangelists, are driving the rapid adoption of web service technologies, within and beyond the enterprise. The process is straightforward. What is the business objective of the solution? Creating Windows Services. How to Create Windows Services It's not uncommon for an enterprise application to need some form of background processes to do continuous work.
These could be tasks such as Cleanup abandoned shopping carts Delete temporary files left behind by some report or image generation feature Send email notifications Create daily reports and send them out Check an email inbox Pull messages from a queue Perform daily or monthly archiving etc.