Current provisions for discovery are based on keyword searches through repositories. Keywords are nominated by service providers through publication and advertising features of software as a service (SaaS) functions. Details of message inputs, outputs, and methods are also captured from WSDL file scans and factored into searches.
Such discovery techniques are suitable in tightly coupled and well-scoped domains where service consumers can determine what services offer and how they can be independently utilized from search results. In other words, users are expected to know what they want before they search.
As seen through this section, web serviceecosystems can generally be described as a logical collection of web services whose exposure and access are subject to constraints, which are characteristic of business service delivery. A lower level analogy can be found with application servers, where access and inter-operation of components is regulated by middleware functions such as discovery/brokering, remote access, object pooling, transactions, asynchronous messaging, persistence management, and so on.
As web services technologies mature, and commercial-scale, service oriented architectures shift from early adoption to mainstream development, a new revolution of service orientation is emerging. Beyond the orchestration of web services in multi-party business processes, a dedicated treatment for procuring web services into different markets is coming into focus.
The first beneficiaries of open procurements of web services are ventures having successfully overcome the dotcom-burst such as Salesforce, StrikeIron, and GrandCentral. These companies leverage XML-based technology to consolidate enterprise application portfolios built by independent software developers for the small to medium markets. Their early successes are paving the way to long-anticipated Amazon/eBay-style marketplaces for web services.
Service-oriented architecture (SOA) has gained mainstream acceptance as a strategy for consolidating and repurposing legacy applications to be combined with new applications in more dynamic environments, through self-contained, reusable, and configurable services. As fostered through the web services standards stack, services, once in place, can interoperate with other services, be composed into long-running business processes, spanning intra- and inter-organizational boundaries, and be procured through different business domains and market sectors. As web services are exposed and connected with one another, they give rise to service ecosystems.
As I promised this morning, these are a few lines to help on setting your intranet systems in the Cloud Computing enviroment. As you probably already noticed, it is all about infrastructure as a service, designed to make web-scale computing easier for developers.
Amazon EC2 (Amazon Elastic Compute Cloud):In simple words, is a collection of web services that provides resizable compute capacity in the cloud. It provides you with complete control of your computing resources and lets you run on Amazon’s computing environment. Amazon EC2 reduces the time required to obtain and boot new server instances to minutes, allowing you to scale capacity, both up and down, as your computing requirements change. EC2 allow you to pay only for capacity that you actually use.
There is an easy way to work with a team remotely and share documents from diverse sources like MS word, Excel, Power Point and many others, without failing in duplication of information or having different version of the same documents. This is an issue that it need to be fix and who better than Google with its online applications (SaaS: Software as a Service) running over their powerful grid and web services platform.
Watch this video and you will understand in few minutes all the benefits of working with virtual documents.