什么是服务总线和访问控制？
我很难理解 Windows Azure 服务总线和访问控制概念。通俗地说，它们是什么？它们有什么用？
I am having a hard time understanding Windows Azure service bus and access control concepts. In layman's terms, what are they? What are they used for?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Windows Azure 的服务总线组件旨在处理多个网络中的服务所产生的问题。基本上，服务总线只是让您的代码看起来像是在单台计算机上运行，而实际上它可以在 Azure 数据中心内的任何位置运行。
访问控制允许您使用“基于基于声明的 RESTful 模型的服务联合身份验证”。（抱歉，从 O'Reilly 有关 Azure 的书中复制并粘贴！）
基本上，当您创建 Azure 站点、应用程序或服务时，它可以在数据中心内数千个系统中的任何一个上运行。每个系统都有自己的 IP 地址、网络、内存、处理器等等。为了让它们协作并显示为单个系统，创建了这两项服务。
如果您想了解有关 Azure 的更多信息，现在是购买一本书的好时机！ :-)
Azure 相当复杂，服务总线和访问控制是更高级的主题。
The Service Bus component of Windows Azure is meant to handle the problems arising from services that are living in multiple networks. Basically, a service bus just makes it appear as if your code is running on a single machine, while in reality it could be running anywhere within the Azure datacenters.
Access Control lets you use "federated authentication for your service based on a claim-based RESTful model. (Sorry, copy&Paste from an O'Reilly book about Azure!)
Basically, when you create an Azure site, application or service, it could be running on any of the thousands of systems within the datacenter. And each of those systems has it's own IP address, it's own network, memory, processor and whatever more. To let them collaborate and to appear as a single system, these two services have been created.
If you want to learn more about Azure, this would be a good moment to buy a book! :-)
Azure is quite complex and service buses and access control are a bit more advanced topics.
服务总线是用于集成多个应用程序的解决方案，无论它们是托管在同一基础设施上还是分布在多个基础设施或/和云计算提供商中。如果您在互联网上进行更多搜索，您可能会发现很多有关 EAI（企业应用程序集成）的信息，这是我关于此主题的博客文章：
http://haggan.wordpress.com/2013/03/07/introduction-to-enterprise-application-integration-eai/
我希望这里的另一个可以帮助您更好地理解什么是服务总线：
http://haggan.wordpress.com/2013/03/09/introducing-service-bus/
换句话说，它是一个消息传递平台，可以帮助您与多个应用程序、软件或服务进行通信，无论什么情况它们是用什么编程语言编写的，或者它们托管在哪个操作系统或平台上。当您将多个节点连接在一起时，您会特别感受到它的效果，我不是指 5 或 6 个节点，而是 10 个及以上。
当然，服务总线有多种类型，无论是基于中继消息服务还是基于代理消息服务，每一种都有多种用途、目的和工作方式。
对于访问控制，这非常简单，它是使用第三方对您的应用程序进行身份验证和授权的一种方式，它是基于声明的身份，您可以通过第三方数据库进行所需的身份验证。您不需要在数据库中从头开始构建所有内容。这在开发过程中很有帮助，我相信这对社交媒体营销和品牌推广有很大帮助，因为在身份验证过程中使用了 facebook、twitter。
Service Bus is a solution for the integration between multiple applications whether they are hosted on the same infrastructure or even spread along multiple infrastructure or/and Cloud Computing provider. If you search more in the internet you might find a lot about EAI (Enterprise application integration) here is my blog post about this topic:
http://hhaggan.wordpress.com/2013/03/07/introduction-to-enterprise-application-integration-eai/
and here another that I hope that helps you understand better what is the service bus:
http://hhaggan.wordpress.com/2013/03/09/introducing-service-bus/
in another words, it is a messaging platform that helps you communicate with multiple applications, softwares or services no matter what programming language they are written with or on which os or platform they are hosted on. you will feel its effect specially when you work on connecting multiple nodes together, I don't mean 5 or 6 nodes but 10 and above.
Certainly there are several types of service bus, whether they are based on relayed messaging service or brokered messaging service, each one of them has several uses, its purpose and way of working.
For the Access control, this is so easy, it is a way of authentication and authorization for your application using third parties, It is a claim based identity that you can do the required authentication through the third party database. you wont need to build everything from scratch in your database. this helps a lot during development and I believe that this can help a lot in social media marketing and branding because of the use of facebook, twitter during the authentication.