http://t.co/M5hSRU76: Six steps to IT investment business case http://t.co/dyb9nfrV
I found this video on the HP site explaining how to use the color-coding technique available through the ‘Organize’ feature in Outlook. It may be a simplistic way to sort your mails, but effective nevertheless.
Tags: color-coding technique, email prioritization, Outlook organize feature
At a recent Gartner Symposium IT/Expo, David Cappuccio, managing vice president and chief of research for the Infrastructure teams with Gartner, introduced what he sees to be 10 key topics for next year’s CIO and business agendas:
1 Virtualization: nothing new here
2 Big data, patterns and analytics: ability to make sense of large unstructured data will be a key challenge in next few years
3. Energy efficiency and monitoring: IT will need to do more whilst consuming less power consumption
4. Context aware apps: connecting social networks with business intelligence to show something relevant on you smartphone
5. Staff retention and retraining: keeping good employees cost less than have new ones onboard
6. Social networks: they cannot be ignored and should be managed very carefully as they may have an impact on brand reputation, business operations, marketing intelligence, etc.
7. Consumerization: more complex applications will be available through everyday mobile phones. Desktop computers will be less relevant
8. Compute per square foot: ability to scale up data centers while not increasing the actual physical space that servers may occupy
9. Cloud computing: elasticity and scalability will drive further penetration
10. Fabrics: vertical integration of server, storage, and network systems and components to optimize shared data center resources
Tags: 2012 IT trends, brand reputation, business intelligence, Cloud Computing, data patterns, Gartner IT trends
Gartner: the Top 10 Strategic Technology Trends for 2012 http://t.co/niyEQsr1
As it seems my WSDL vs XSD post is still the most popular one, this is another try at explaining web services terminology in more common business terms.
This time I would like to introduce RESTful approach to services and explain the high level differences with WSDL/SOAP presented before.
Representational State Transfer or REST is making use of standard URIs (Uniform Resource Identifiers, i.e. a fancy acronym meaning web site addresses) and Http operations like GET, PUT, POST, and DELETE to allow consumers to use its service. Accessing a REST service is as simple as going to a web page where you pass along some parameters:
http(s)://www.provider.com/service/method?Parameters=xyz
Let me try to go through some of the key differences that differentiate the RESTful and SOAP/WSDL approaches:
1) RESTful makes use of Http operations and thus can only be used via Http(s), while SOAP can use different transport mechanisms (e.g. SMTP)
2) RESTful does not force the use of XML format leaving developers other options such as JSON or HTML. SOAP/WSDL support XML only
3) SOAP web services are usually associated with business actions like “createOrder” or “getLabel” while RESTful is about “resources” like images where Http operations (e.g. “Put”) are applied
4) RESTful is more lightweight and usually human-readable. Web Services through SOAP envelopes and WSDL specifications are enforcing more strict rules to govern communications and utilization between systems. SOAP can also guarantee transactions security
5) If the implementation requires a dialog between systems where a conversational state must be kept, then SOAP can support that as part of its specification while this would need to be built if the RESTful approach is used
In another post I will go on with some examples, for the moment it should be clear that RESTful or WSDL/SOAP have their pros and cons. In general, SOAP is more mature and well defined backed with a complete set of specifications for robust and secure business transactions. RESTful is light weight and high performance to support client rich web applications.
Tags: RESTful vs SOAP/WSDL, soap web services, soap wsdl, web services description language, web services terminology
Facebook
LinkedIn
Twitter