SOA with REST-Prentice Hall(2012).pdf下载

weixin_39821526 2020-06-19 04:30:21

When I rst heard about REST in early 2002, I was a strong believer in the value of the emerging Web services speci cations and standards. I was initially intrigued by the approach, particularly the “uniform interface” idea, but quickly concluded that while REST might be interesting, it was most cer
相关下载链接：//download.csdn.net/download/windstand/10333529?utm_source=bbsseo

...全文

22 回复打赏收藏转发到动态举报

写回复

回复

切换为时间正序

请发表友善的回复…

发表回复

When I rst heard about REST in early 2002, I was a strong believer in the value of the emerging Web services speci cations and standards. I was initially intrigued by the approach, particularly the “uniform interface” idea, but quickly concluded that while REST might be interesting, it was most certainly not applicable in enterprise use cases. A year or two later, I had started to appreciate the elegance and simplicity of the REST style, and became convinced that in some cases, it was a better choice, while more advanced use cases still required SOAP and WSDL and WS-*. Another year later, I found myself recommending RESTful HTTP over SOAP-style Web services in most situations, and decided that I could call myself a “RESTafarian” by conviction. I had become convinced—and still am—that adhering to the constraints of the REST archi- tectural style not only leads to better systems on the public Web, but also within all kinds of enterprise-internal scenarios. Today, REST has become mainstream—with all the positive and negative effects this has for any technology. It is now relatively easy to introduce a RESTful approach, even in large enterprises, without raising too many eyebrows. I am still surprised how often it is even viewed as the obvious default choice. So maybe the REST community should be happy and satis ed, and look forward to all the excellent system development and integration work we will do, both on the public Web and within companies. But there are two problems with this: Not everything that claims to be RESTful actually is so, and often SOA is perceived as the architecture of WS-* style Web services and therefore seen as incompatible with REST.

REST的SOA（SOA with REST）概念发展 1992年网站（Web Sites）是在Web浏览器和Web服务器直接通过HTTP传输HTML。 2000年WS-* （Web Services）是在客户端和服务器之间基于HTTP传输SOAP XML格式的数据，服务端用WSDL来规定契约。 2007年RESTful （Web Services）是在客户端和服务器之...

本节书摘来自异步社区《SOA与REST：用REST构建企业级SOA解决方案》一书中的第1章1.5节附加信息，作者【美】Thomas Erl , Benjamin Carlyle , Cesare Pautasso , Raj Balasubramanian，更多章节内容可以访问云栖社区“异步社区”公众号查看。 1.5　附加信息以下章节针对Thomas E...

3月，InfoQ发布了Thomas Erl的新书（《SOA设计模式》）的摘录（~30MB PDF），并借此机会采访了作者。话题涉及到模式目录（patterns catalog）的作用，面向服务、SOA和Web服务三者之间的区别，以及SOA世界的现状。\InfoQ：在您看来，服务目录给SOA社区带来的主要好处是什么？\Thomas Erl (TE)：对于有兴趣了解某个已知设计问题曾经是如何被成功解决...

作者简介托马斯.埃尔( Thomas ErI) Arcitura教育创始人，也是"Prentice Hall ServiceTechnology Series from Thomas Erl"系列图书的编辑。他的书籍在全球已发行超过30万册，成为国际畅销书，并获得IBM、微软、甲骨文、英特尔、埃森哲、IEEE、HL7、MITRE、SAP、CISCO、惠普等很多主要IT机构高级成员的正式认可。作为Arcitura教育公司的首席执行官，托马斯领导了国际公认的大数据科学专业认证(BDSCP)、云专业认证( C

下载资源悬赏专区

13,656

社区成员

12,675,616

社区内容

发帖

与我相关

我的任务

其他技术论坛（原bbs）

社区管理员

加入社区

近7日
近30日
至今

加载中

查看更多榜单

社区公告

暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章