Geeks With Blogs
devwaves - bits from the software front Bits and pieces from the software development scene.. things seen, heard and felt first hand... May 2013 Entries
Tree-Of-Trust
Overview Enterprise applications of today are no longer independent, but dependent on other applications, services and components for completing their functionality. Authenticating/Trusting another application typically requires having a new authentication/identity management module written for each new application that is integrated. With the advent of claims based/token based authentication, this pain has been eased very much for a developer. Supporting protocols, standards and frameworks such ......

Posted On Sunday, May 26, 2013 7:08 PM

Humans and Human body as the final Architectural reference point.
Its an interesting perspective to consider humans, their means of interaction with others including other humans, animals, machines, their growth, evolution, human anatomy among others as a software architecture reference point. Given a scenario for high load data transactions that come in, how would a typical single human handle it? How would many humans handle it? In case of multiple humans interacting to achieve a goal, how do they interact and how do they establish trust (also read tree-of-trust). ......

Posted On Sunday, May 26, 2013 7:04 PM

Need of the hour : Strong mobility in .NET based distributed applications.
Typically, distributed application written in .NET are either code distributed (assemblies moved across machines/nodes) or data distributed (data serialized across machines/nodes). What might additionally be required is strong mobility of process/thread/ TPL task/fiber etc. This effectively means serializing a task/thread with its execution context too. Once this is implemented, this means that a thread/method/delegate function would theoretically be executed across machines, with the context flowing ......

Posted On Sunday, May 26, 2013 7:03 PM

Message ReSequencing in a Distributed Publisher-Subscriber System
In a typical cloud based distributed environment with many message publishers and subscribers, the message could be processed by any of the subscriber and this is usually not predictable. In certain scenarios, it could be necessary to have a group of messages processed in sequence though they reached the subscribers randomly. One solution to this is described below. The solutions tries to satisfy the following requirements : 1.) Make sure there is no tie-up / hard-link between subscribers and publishers: ......

Posted On Sunday, May 26, 2013 7:02 PM

Copyright © Nitin Stephen Koshy | Powered by: GeeksWithBlogs.net