Thursday, February 11, 2010

Competitive price offerings from expressor-software

Booyah! I watched expressor-software's deep dive webinar today hosted by two of their highly knowledgeable - Director of Field Engineering (DFE), Marketing Director (MD). After the webinar I had tons of questions around the framework that I would perhaps need to design for a large EDW if I used expressor-software.
Soon after, DFE spoke about scalability, stress testing, semantic repository, operational metadata, I feel it is an amazing kick-off. Following are features that came fascinating to me right away -
1. Semantic repository based on a rules engine. What that means is a data steward who creates business rules can log the rules into their semantic engine and a developer can pick it off during the dev. phase. Amazing isnt't it?
2. Re-usability - Often on financial and banking projects we hear developer's frustrations. "Should I recreate the business rule? Phew! the tool could have been a little better to offer something like a shared container(IBM DataStage term), mapplet(Informatica lingo)". expressor-software's thrust is on their business rules re-usability.
3. Pipeline Partitioning - Early 2000s is when Ascential introduced pipeline partioning into DataStage at VERSION 5. Even Informatica introduced pipeline partitioning later in their offerings. For a startup tool, this is great to have in its 2nd version itself! Good visioning expressor-software!
4. Pricing Model - Channel based pricing. A channel based on their pricing model is sequential processing if 1 channel. For multi-processing multi channels need to be bought. Excellent price chart starting with 6months, 1 year, 2 year based subscriptions. Feels like you are at a redbox for renting a tool.

What I really lookforward from expressor-software is -
1. Although every tool should and can be configured with an enterprise scheduler in this era of fast paced data integration world, every tool needs to have its own workflow designer. I'm waiting for expressor-software to come out with its own workflow based designer for developers to call it fully packaged enterprise tool and for operators to receive notifications at wee and fiesta hours. :)

Disclaimer: The above are my personal opinions based on my observation and do not represent my employer's view in any way.

2 comments:

  1. As you pointed out in your blog, we agree that expressor has done a great deal of work creating an enterprise-ready product while introducing several very compelling differences in the way data integration can be done.

    We continue to be sharply focused on both ease of use and team development in our product roadmap – watch for us to bring some exciting, game changing innovations to this area just as we have in the topics you are discussing in your blog.

    As you point out in your final paragraph, workflow is an important component to the making the team development process progress efficiently - we couldn’t agree more and believe we have some compelling ideas for that as well.

    ReplyDelete
  2. What are workflow integration techniques with expressor-software's jobs?

    ReplyDelete