Monday Mar 30, 2015

Is Database-as-a-Service in your IT Services Catalog?

Private Database Cloud Services or Database as a Service (DBaaS) is no longer a new idea. In fact, it is quickly becoming the de facto standard for development and testing environments both on premises and in the public cloud. And while there are many use cases and deployment options, overall database total cost of ownership and business agility have benefited from a standardized approach to workload management. Whether you are a DBA, an operations manager, or a CIO, you are well aware that business-driven interest in social, mobile, big data, and internet of things have caused an explosion of development, data, and database workloads. The justification for database operations to pool resources and standardize services has never been clearer – watch this customer story (TRT1:30).[Read More]

Thursday May 17, 2012

Mobileize Your Business Process Applications

Mobileize Your BPM Applications

Recently, there has been a lot more talk about mobilizing corporate applications.  One of the customers that I work with wanted to know how they can mobilize their BPM applications.  There are a couple ways to do this.  Here are two different approaches (using ADF Mobile and/or Actionable Emails):

1. ADF Mobile:
b. (Datasheet)
c. (Documentation)

2. Actionable Emails:

 Figured that might help some people understand how you can mobilize your work force.

Tuesday Jan 03, 2012

Carpe Nube*


Enterprise Architecture is more important than ever with the increased adoption of Cloud Computing.  Most companies that I work with have a range of systems and initiatives that span the continuum of “must stay in house” to “this is best run in the public cloud.”  There are 3 types of Cloud Models:

  1. Private Cloud (we like cloud, but need to manage it ourselves because of security/cost/agility/etc.. reasons)
  2. Public Cloud (here are the systems we need, we will pay you to run it for us)
  3. Hybrid Cloud (some systems we need to keep in-house but for other stuff it would be cost effective (or cost avoiding)  if we did not have to run/maintain them ourselves)

In all cases, Cloud is an IT operational model (what systems run where) that is driven by business needs and imperatives.  Even if you go 100% Public Cloud, you still need to make sure that the Applications and Information provided by those systems are meeting the ever changing business needs.  The Hybrid Cloud model provides even more complexity because applications, communication, integration, data flow, and security need to be coordinated across the Cloud boundaries. 

Enterprise Architecture is the glue that can help keep all of these things together and is why Cloud Computing does not get rid of the need for EA, in fact, it is this humble author’s opinion that it dramatically increases the need of EA stewardship over Cloud.

* (Latin for Seize the Cloud)

Wednesday May 18, 2011

Combining SOA and WCM

A good friend of mine was in town this week to visit one of his clients.  When we got together for dinner (and, yes, drinks) one of the topics (inevitably) was architecture.  Lately he has been working with some very large international companies re-architecting their public web sites to flexibly deliver localized content.  The solution was to combine Service-Oriented Architecture with Web Content Management.

In a nutshell, the architecture includes a web front end that is composed from portlets where each portlet requests content from WCM system(s) using WSRP.  The front end is de-coupled from the WCM systems via a service bus where the service bus is responsible for routing the content request to the appropriate WCM system.  (I’m using the term “service bus” here in the most generic sense, not to denote a specific product.  My friend prefers the term “service fabric”.)

This has an obvious advantage for localized content.  The service bus routes the request to the correct WCM system based on the chosen local.  This allows each division, country, or geography to manage its own content yet the corporate web presence is still unified.

Another advantage my friend pointed out is that this architecture simplifies previewing of new or modified content.  The service bus can route content requests to a staging WCM system for users that are responsible for reviewing new or modified content.  The new/modified content can be viewed directly in the production web site before being “published”.

It figures that I’d have this conversation *after* writing the ORA User Interaction document (a part of ITSO).  Nonetheless the ORA User Interaction document does cover these topics albeit not this specific usage.  This architecture is a specific example of what is denoted generically as “federation” (e.g. section 4.2.3) in the document.

Monday Dec 06, 2010

ITSO - Behind the Scenes

[Read More]

Art, Artifacts, and Best Practices for Enterprise Architects


« July 2016