Welcome!

Innovative Technologies and Approaches for the Government

Tieu Luu

Subscribe to Tieu Luu: eMailAlertsEmail Alerts
Get Tieu Luu via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Tieu Luu

The adoption of Service Oriented Architecture (SOA) promises to further decouple monolithic applications by decomposing business functions and processes into discrete services. While this makes enterprise computing assets more accessible and reusable, SOA implementation patterns are primarily an iteration over previous application development models. Like most application development evolutions, SOA approaches inject more layers and flexibility into the application tier, but have often neglected the most fundamental building block of all applications: the underlying data. Current Data Environment of Most IT Organizations The condition of a typical organization's data environment is usually not where it needs to be before the organization can begin a SOA transformation - from an enterprise perspective, there's often a lack of authoritative sources and a wide array of ... (more)

SOA Message Exchage Patterns

There are a variety message exchange patterns that can be used to implement an SOA. Know them and when to apply them. It can mean the difference between an SOA that scales and performs vs. one that doesn't. The traditional synchronous request/response may not always be the most appropriate in all scenarios. Here are some examples of other types of MEPs: Asynchronous request/response using a callback--the consumer sends a request and provides a reference to a callback service as part of the request; instead of responding synchronously to the request, the service responds asynchron... (more)

Widget Wars: OpenSocial vs. OpenAjax vs. W3C Widgets

The popularity of widgets these days has brought to attention the need for interoperability, i.e. for widgets developed for one site or platform to be able to run in other sites and widgets developed by different people to be able to work with each other. So much so that I know of at least 3 somewhat competing specifications for widgets. There's the gadget portion of the OpenSocial specs which was adopted from the Google Gadgets work. Then there's OpenAjax which is more broadly focused on Ajax interoperability but has a lot of pieces geared towards widget interoperability. And... (more)

It’s All About the Relationships

Over the past few years I’ve been helping a lot of government clients design and implement architectures for information-sharing.  When it comes to information-sharing one of the most important aspects is the relationships in the data being shared because it’s those relationships that provide the context to help you understand and utilize the information better.  Within an enterprise, key data types are often dispersed across multiple systems so a lot of the things we did included implementing data services (i.e. SOAP/WSDL-based Web Services) on top of each of these systems to pr... (more)

Don't Forget Security on the Way Out

Typically when we think about security for a Web service, our focus is on how to protect it from unauthorized and malicious users. Thus, we tend to concentrate on such things as authentication of the requestor, checking to see that the requestor is authorized to access the service, validation of the request message, and so forth - all things that happen on the way in or during a request for the service. However, there is an equally important set of security functions that need to occur on the way out or after the service has finished processing the request. Because these securit... (more)