Frictionless Connectivity Across Applications
An application that relies on collections of smaller applications that are connected to or integrated with each other is called a composite application. The Microsoft® .NET Service Bus provides a secure, standards-based messaging infrastructure that dramatically reduces the barriers for building composite applications, even when their components have to communicate across organizational boundaries.
Overview
Lower Barriers to Building Composite Applications
Using the Service Bus, an application or service can expose and access endpoints that would otherwise be hard or impossible to reach. For example, the endpoints may be located behind network address translation (NAT) boundaries or bound to frequently changing, dynamically assigned IP addresses.
Exposes Service Endpoints Easily
- Users can access a global hierarchical namespace that is DNS- and transport- independent
- Services can be located through a stable, Internet-accessible URL, irrespective of location.
- One-way messaging between sender and listener supports unicast and multicast datagram distribution
- Full-duplex connection-oriented sessions between sender and listener support bi-directional communication
- Full-duplex, connection-oriented peer-to-peer sessions with network-boundary traversal create direct end-to-end connectivity through NAT
- The simple publish/subscribe model lets multiple publishers and multiple subscribers simultaneously use the service’s topic management and event distribution system
Lightweight, Developer-Friendly Programming Model
Building applications using the Service Bus does not require a significant footprint within an organization and leads to more rapid deployments while keeping the local infrastructure intact.
Supports Standard Protocols
- Web Service specifications (WS-*)
- REST and HTTP
- Access from non-.NET platforms
- The service is a small, lightweight download that tightly aligns with your existing .NET developer skills
- For Windows® Communication Foundation programmers, the Service Bus capabilities come as extensions to the familiar standard bindings
Secure Design
By default, all communication with and through the Service Bus infrastructure is subject to authorization by the Microsoft .NET Access Control Service and supports a whole range of Microsoft data center network defenses. As a result, the Service Bus infrastructure helps to block malicious traffic and shield your services from intrusions and denial-of-service attacks.
Simplifies Coding
- Service endpoints can be secured with a Web interface or programmatically, based on Access Control Service rules
- Anonymous access to services is supported only if you permit it
Take a Closer Look
Developer Resources on MSDN
.NET Services