| Author |
Message
|
| brgmo |
 Posted: Wed Jun 20, 2007 3:57 am Post subject: Does ESQL is needed any more |
 |
|
Master
Joined: 03 Jun 2002
Posts: 227
|
Hi All,
We are planning to use WBIMB for our current project. Now, we have WLI as well which implemets all it's integrating logic in java. I have used WBIMB in past but with the ESQL. Now,since we have java available with v6.0, do we really need to know ESQL any more. I mean, can i do all the qork that i uded to do in ESQL without any problem if i use java compute nodes and get the same level of performance. Further,what is the adavantage or disadvantage of using java over ESQL.
Regards
brgmo. |
|
| Back to top |
|
 |
| gkorodi |
| Posted: Wed Jun 20, 2007 4:02 am Post subject: |
|
|
Novice
Joined: 28 Sep 2003
Posts: 13
Location: Boston-London-Budapest
|
IMHO you will never get the same performance with java that you would get from ESQL.
Not even close.
However, you could use a lot more additional functionality (at the price of performance) with Java. You could add your own functionality to the broker as well.
However, you should not do too many things at once. You are better off just doing transformation and routing with the broker, through ESQL, and process the data outside, maybe with Java program or with C++ program.
Just my two penny.
_________________
Gabe "The Hun" Korodi |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 20, 2007 4:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you're using v6, you're not using WBIMB, you're using WMB. Same thing, different name.
ESQL can be faster to write, if you know ESQL.
The performance should be about the same. The Java API requires a "lower" level of understanding of how the message tree is built, and manipulated - I mean you have to know more about the elements of the message tree and etc.
The XPath expressions in the Java API can make Java coding easy - but are also subject to performance issues if you don't know exactly what you're doing. This is because of things like what appears to be a simple statement to access a single field might actually be accessing every field in the tree that matches the same path.
There are things you can do with Java that you can't do with ESQL - like read and write files, or access JDBC datasources.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Jun 20, 2007 4:05 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
This question comes up lots; try searching. ESQL is better at tree manipulation; Java is better at other things. It usually comes down to skill levels and what you feel most comfortable with.
In Broker, neither language is going away. |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Wed Jun 20, 2007 4:09 am Post subject: Re: Does ESQL is needed any more |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
JAVA is little slower.
When you need simple manipulation ESQL is easier to implement (no additional projects, ...). This is my opinion.
I'm "Java oriented", but in broker I use JAVA only when I can not use ESQL (additional functionality).
_________________
Marcin |
|
| Back to top |
|
|
| brgmo |
| Posted: Wed Jun 20, 2007 5:06 am Post subject: |
|
|
Master
Joined: 03 Jun 2002
Posts: 227
|
I did a POC work for this. Using java i was able to process 60 msgs per second. The message size was 150k each. However,with ESQL the message processing rate was between 54 to 57 per second. With java,i feel i can do all the possible stuff which can be done by ESQL and even more.
Regards
brgmo. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jun 20, 2007 8:29 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
ESQL is much easier to learn. The purpose of WMB was to get away from having to have deep programming skills in order to build integration logic.
IBM have eventually introduced Java but I believe their vision was for minimal programming skills to be necessary.
If you're not careful the maintenance and re-use of WMB logic could become very difficult if too much Java code is used. |
|
| Back to top |
|
|
| raghug |
| Posted: Thu Jun 21, 2007 5:49 pm Post subject: ESQL Esay to perform |
|
|
Acolyte
Joined: 19 Jul 2006
Posts: 60
Location: NJ
|
Last month I got same problem one of team mate write java and ESQL Esay to perform .But ESQL perform well because of that we remove Jave
Thanks
WIN |
|
| Back to top |
|
|
| jbanoop |
| Posted: Thu Jun 21, 2007 7:09 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Tree creation and manipulation is much more elegant and easier and clearer in ESQL.
If I was given a choice, I would go with ESQL as much as possible. But when you need functionality that ESQL cannot offer, java comes as a welcome relief as it gives you a whole lot more options.
There would also be cases in which MB may come in to replace an exisiting middleware solution (like egate or an inhouse java based framework etc). In these cases, migration would be much much more simpler if java were used because many components of the old system could possibly be reused.
I have heard of projects where it has been decided that only java would be used, mainly by decision makers who dont know head or tail of the product.
In my opinion the mix of ESQL and Java makes Message Broker a very powerful and flexible offering.
I do come from a background of java/j2ee. |
|
| Back to top |
|
|
|
|
