1. Why is the perception getting stronger that integration will become a critical factor in coming days?The perception of integration getting stronger is because it can bring business benefits. The benefits could be extracted from a research from a networking consultancy company called Camden. (Zeichick. A., 2004)The research is called 'THE BUSINESS BENEFITS OF INTEGRATION', and the main points are summarized below.
Integration may be the most cost-effective way for IT to add business value to the enterprise.Revenue Enhancers
1. Sell more through suggestive sales techniques.
2. Boost customer retention by turning customer service into self-service.
3. Increase revenue by empowering your own sales and support teams.
Cost Reducers
4. Eliminate the cost of storing and managing redundant data.
5. Reduce the cost of manual data reentry and report generation.
6. Lower ongoing system administration expenses.
Efficiency Improvers
7. Accelerate application development using modern RAD platforms.
8. Control and simplify business processes via work flow.
9. Efficiently incorporate modern security programs.
Future Planning
10. Lay an architectural framework that will provide the enterprise with greater agility.
ReferencesZeichick.A. (2004).
The Business Benefits of Integration. Camden Associates. Retrieved on 3 April, 2010 from www.attachmate.com/NR/rdonlyres/...50C0.../literature_bbintegrate.pdf
2. What is the relationship of AJAX to JQuery (jquery.com) and the lightweight Web 2.0 javascript framework called MooTools (mootools.net) within the enterprise software architecture?The below information are extracted from Wiki.
jQuery is a lightweight cross-browser JavaScript library that emphasizes interaction between JavaScript and HTML. It was released in January 2006 at BarCamp NYC by John Resig. Used by over 27% of the 10,000 most visited websites, jQuery is the most popular JavaScript library in use today. (Wiki, 2010)
MooTools (My Object-Oriented Tools) is an open-source, lightweight, modular object-oriented programming JavaScript Web application framework released under the MIT License. …The framework includes built-in functions for manipulation of CSS, DOM elements, native JavaScript objects, Ajax requests, DOM effects, and more. MooTools also provides a detailed, coherent application programming interface (API)[8], as well as a custom downloads module allowing developers to download only the modules and dependencies they need for a particular app.
ReferencesWiki. (2010). iQuery. Retrieved on 4 April 2010 from http://en.wikipedia.org/wiki/JQuery
Wiki. (2010). Mootools. Retrieved on 4 April 2010 from http://en.wikipedia.org/wiki/Mootools
4. What does it mean to develop RESTful practices into our web applications? Representational State Transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. Conforming to the REST constraints is referred to as being ‘RESTful’.
Constraints
The REST architectural style describes the following six constraints applied to the architecture, while leaving the implementation of the individual components free to design:
Client-server
Stateless
Cacheable
Layered system
Code on demand (optional)
Uniform interface
Complying with these constraints, and thus conforming to the REST architectural style, will enable any kind of distributed hypermedia system to have desirable emergent properties, such as performance, scalability, simplicity, modifiability, visibility, portability and reliability.
Impmenting RESTful web services
A RESTful web service (also called a RESTful web API) is a simple web service implemented using HTTP and the principles of REST. It is a collection of resources, with three defined aspects:
• the base URI for the web service, such as http://example.com/resources/
• the MIME type of the data supported by the web service. This is often JSON, XML or YAML but can be any other valid MIME type.
• the set of operations supported by the web service using HTTP methods (e.g., POST, GET, PUT or DELETE).
Unlike SOAP-based web services, there is no "official" standard for RESTful web service.[8] This is because REST is an architecture, unlike SOAP, which is a protocol. Even though REST is not a standard, a RESTful implementation such as the Web can use standards like HTTP, URL, XML, PNG, etc.