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 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 finally there's the W3C's Widgets 1.0 Family of Specifications. Based on a preliminary analysis, the OpenAjax specs appear to be the most comprehensive for widget interoperability issues but OpenSocial seems to have gained more adoption. The W3C work appears to be moving very slowly (no surp... (more)

Loosely Coupled Flex and JS Widgets

It has become very popular to build web sites that use and embed widgets from various providers. For example, MySpace and Facebook let their users easily embed various JavaScript widgets and Flash-based applications and videos onto their personal pages. In most cases, the widgets act in a standalone fashion, unaware of the other widgets contained on the same page. Standalone widgets are fine for simple portal pages but for more targeted applications some level of interaction among the components on the page is needed. When such interactions are needed, they are usually achieved t... (more)

Opinion: Not All SOAs Need ESBs

I've recently asked one of my developers to research some integration and middleware technologies for a project we're working on. After spending a couple days on this, he said to me "these things are all part of ESBs now" - i.e. all the integration and middleware vendors have pretty much taken these capabilities and bundled them into their ESB platforms. "Oh you need a message bus? That's part of our ESB now." "Oh you need this adapter? That's included in our ESB." In most cases when you're implementing an SOA, you will need some piece of middleware or integration technology. With ... (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)

SOA Data Strategy

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. Curren... (more)