I've had a Comcast cable Internet connection for years. Last year I got a shiny new fiber connection from Mstar. But rather than uninstall the cable connection, I asked FatPipe Networks if they'd be willing to let me perform an extended test of the company's flagship route clustering product, WARP.
Stories by Phillip J. Windley
Federated identity has long been a goal of many IT organizations. One look at the promise of federation, and it is easy to see why. After all, empowering one organization to serve as an identity provider for another frees IT from having to manage the identities of partnering organizations' employees and customers, thereby facilitating the pursuit of competitive-advantage projects. In this era of increasing enterprise decentralization, thanks in large part to the Web, establishing a federated identity framework is fast proving as essential as it is hard to pull off.
Designing a Web service for a few dozen participants is one thing. Designing a system for thousands of clients with hundreds added weekly is a different story. In the latter scenario, there is a high premium on service provisioning, customer self-service, and security.
If you use a firewall as part of your network security strategy, you might be feeling smug, thinking that you've closed access to thousands of ports and vulnerabilities. What you may not realize is that your firewall is most likely blithely passing XML through port 80, the Web's default port.
In distributed architectures, most of the interacting software components operated in a single trusted domain that was centrally managed. In the new decentralized model, interactions between components span organizational boundaries, making it difficult to manage, configure, monitor, and update the components from a single operations organization.