Next station: Federation between Adatum & its Customers.

First things first: thanks everybody who wrote me about the first scenario article. I got quite some e-mail on it with great suggestions to improve, but in general it seems it resonates well with. Disclaimer: this post and the next ones are early drafts to share with you the direction we are taking. They might…

3

Claims based Authentication & Authorization Guide – The design of the book

As I mentioned in my previous post, we are going to use a “case study” approach in this book in which we will be presenting a series of concrete scenarios, each one will introduce some very specific requirements. Then we will be showing and discussing possible solutions in that context. The intent is that each…


Announcing new project – patterns & practices – Claims based Authentication & Authorization Guide

For the next couple of months I’ll be working on a new project here at patterns & practices, developing a new guide for claims based authentication and authorization. I’m personally very happy to be working on this project, for many reasons. I believe frameworks like “Geneva” (previously known as “Zermatt”, now Windows Identity Foundation), products…

5

First experiments with (new) SQL Data Services

Last week I got my new login to the new SQL Data Services. As a reminder for all readers: SDS accelerates its plans to offer relational capabilities May 11, 2009 – Based on customer feedback, SDS has accelerated its plans and will be offering true relational capabilities through SQL Server’s existing network protocol, Tabular Data…

7

Windows Azure 101 – Primitives and Application Patterns – Playing Mendeleyev

Windows Azure’s primitives are very simple, but as in many other things, the power comes from the combination of these simpler primitives to create more complex things. Look around and see how many things can be assembled from a little more than 100 “simple” elements. In Windows Azure,  there are essentially 2 types of building…

3

Azure IssueTracker Enterprise – Simple Demos

Provisioning IssueTracker Enterprise: Highlights: There’s no direct interaction with Access Control Service. IssueTracker uses ACS API to create the scopes, rules and the issuer (Contoso). The provisioning form captures all the required information to setup the trust relationship between Access Controls Service and the tenant (certificate, etc)     Tenant (Contoso_Enterprise) uses IssueTracker Enterprise from…


Architecting Cloud Application for the Enterprise – Part V – Management

Having solved the identity issue, the SuperCloudySoftware team focuses then on the management requirements raised in the meeting with VeryBigCorp CIO. To recap, they want to: Be able to to monitor IssueTracker from their existing infrastructure, that happens to be System Center Operations Manager (SCOM) and eventually author new rules to correlate IssueTracker specific events…

2

Architecting Cloud Applications for the Enterprise – Part IV – SuperCloudySoftware sketches IssueTracker Enterprise Edition

In the previous article, we explored the challenges of building services for an enterprise, illustrating those through a dialogue between VeryBigCorp CIO and a team from SuperCloudySoftware. VBC requirements can be summarized as: Identity integration (including Single Sign On and management of access policies) Management integration (ability to monitor and act on IssueTracker from within…

3

The need for “standards for application logic” in PaaS. Really?

In his latest post on Coghead’s demise, Phil argues that: “What this highlights is the lack of any standard for transferring not just data but application logic between such platforms.” My argument is that those standards already exist and are widely adopted: “Standards for capturing application logic already exist: Java & .NET (and COBOL). Coghead…

4