I agree with Cyril. In addition to what's already been mentioned, I don't think it's a good idea to make mediation threads blocked for database calls, etc via DBLookup/DBReport for longer periods of time, as most of the queries that are usually being used in pretty much any practical enterprise integration scenario would be time-consuming, particularly as respective data-stores get occupied of large volumes of data, over time. ESB, as quite being used as a backbone of any system that connects multiple disparate systems together via mediation, etc, letting its core blocked for such an environment isn't quite good, IMO. Instead, I believe, a better option would be to delegate the same responsibility to the data layer, which can then be scaled up and tuned to deal with similar instances.
Cheers, Prabath On Wed, Dec 16, 2015 at 12:05 PM, Cyril Rognon <cyril.rog...@emoxa.fr> wrote: > Hi > > DB mediator can be handy as you said but it is a bad practice to query > the DB right from the Esb. It is against the low coupling principles that > makes integration layer agile and thin and scalable etc. > > DSS is setup in two minutes and can fulfill your needs out of the box. > > Maybe we should provide a migration tool to turn DBMediator usage into > Daraservices operation call. One could even generate the dbs Dataservice > definition from the DBMediator. > > +1 for deprecating these mediators. Setup some tool or complete > documentation to migrate existing usage. > > Thanks, > Cyril > Le 9 déc. 2015 13:55, "Malaka Silva" <mal...@wso2.com> a écrit : > >> In my experience using DB mediator we can cover some of the use cases >> using ESB out of the box, which I find very handy. >> >> Also use case of integrating with stored procs can easily covered with >> this. >> >> However there are limits like batch update or getting multiple rows. >> >> I guess we can argue both ways. IMO we should keep these mediators since >> it'll become handy for some use cases :) >> >> On Wed, Dec 9, 2015 at 4:58 PM, Kasun Indrasiri <ka...@wso2.com> wrote: >> >>> >>> >>> On Wed, Dec 9, 2015 at 3:32 PM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> +1 except DBReport/DBLookup mediators >>>> >>>> DBReport and DBLookup only offer a very limited set of capabilities. >>> IMO, for any real integration scenario, we can't use them. :). >>> >>>> On Wed, Dec 9, 2015 at 2:00 PM, Yumani Ranaweera <yum...@wso2.com> >>>> wrote: >>>> >>>>> Is it possible to provide sufficient documentation to help the >>>>> customers who would be migrating in future. >>>>> >>>>> Thanks, >>>>> Yumani >>>>> >>>>> >>>>> On Wed, Dec 9, 2015 at 1:45 PM, Chanaka Fernando <chana...@wso2.com> >>>>> wrote: >>>>> >>>>>> *- Callout mediator :* >>>>>> All the callout functionality is supported with 'call' mediator with >>>>>> blocking=true. Having two similar mediators will be create a bit of a >>>>>> confusion. >>>>>> >>>>>> It will make a lot of confusion when we have more than one mediators >>>>>> to do the same thing. Therefore, better to deprecate this mediator. >>>>>> >>>>>> *- DBReport/DBLookup mediator* >>>>>> These mediators offer very limited functionality and we always >>>>>> recommend to integrate with databases with the use of DSS (using a >>>>>> separate >>>>>> DSS or using DSS features inside ESB) >>>>>> >>>>>> Even though this mediator has been used by some customers, they are >>>>>> using that for very limited functionality and we always suggest them to >>>>>> use >>>>>> DSS as Kasun mentioned. If users really want to connect to a database, >>>>>> they >>>>>> can easily write a simple class mediator. >>>>>> >>>>>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active >>>>>> development happens on these. >>>>>> *- Router* : Same as filter mediator, so no use of having this. >>>>>> *- In, Out * : Rarely used and often not required with the new >>>>>> call/respond mediator approach. >>>>>> >>>>>> +1 for deprecating these mediators. >>>>>> >>>>>> With the new DAS integration, we can deprecate BAM mediator since we >>>>>> have the PublishEvent mediator. >>>>>> >>>>>> On Wed, Dec 9, 2015 at 6:41 AM, Kasun Indrasiri <ka...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Shall we deprecate following mediators in 4.10 release. >>>>>>> >>>>>>> *- Callout mediator :* >>>>>>> All the callout functionality is supported with 'call' mediator >>>>>>> with blocking=true. Having two similar mediators will be create a bit >>>>>>> of a >>>>>>> confusion. >>>>>>> >>>>>>> *- DBReport/DBLookup mediator* >>>>>>> These mediators offer very limited functionality and we always >>>>>>> recommend to integrate with databases with the use of DSS (using a >>>>>>> separate >>>>>>> DSS or using DSS features inside ESB) >>>>>>> >>>>>>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active >>>>>>> development happens on these. >>>>>>> *- Router* : Same as filter mediator, so no use of having this. >>>>>>> *- In, Out * : Rarely used and often not required with the new >>>>>>> call/respond mediator approach. >>>>>>> >>>>>>> Any comments on these or any other features that we should >>>>>>> deprecate from 4.10 release? >>>>>>> >>>>>>> Thanks, >>>>>>> Kasun. >>>>>>> >>>>>>> -- >>>>>>> Kasun Indrasiri >>>>>>> Software Architect >>>>>>> WSO2, Inc.; http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> cell: +94 77 556 5206 >>>>>>> Blog : http://kasunpanorama.blogspot.com/ >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thank you and Best Regards, >>>>>> Chanaka Fernando >>>>>> Senior Technical Lead >>>>>> WSO2, Inc.; http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> mobile: +94 773337238 >>>>>> Blog : http://soatutorials.blogspot.com >>>>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >>>>>> Twitter:https://twitter.com/chanakaudaya >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> *Yumani Ranaweera* | Technical Lead >>>>> Technical Support- Colombo >>>>> WSO2 Inc. | http://wso2.com >>>>> Blog: http://yumani.blogspot.com/ >>>>> Mob: + 94 777795242 >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> architect...@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Best Regards, >>>> >>>> Malaka Silva >>>> Senior Tech Lead >>>> M: +94 777 219 791 >>>> Tel : 94 11 214 5345 >>>> Fax :94 11 2145300 >>>> Skype : malaka.sampath.silva >>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>> Blog : http://mrmalakasilva.blogspot.com/ >>>> >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> http://www.wso2.com/ >>>> http://www.wso2.com/about/team/malaka-silva/ >>>> <http://wso2.com/about/team/malaka-silva/> >>>> https://store.wso2.com/store/ >>>> >>>> Save a tree -Conserve nature & Save the world for your future. Print >>>> this email only if it is absolutely necessary. >>>> >>> >>> >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Senior Tech Lead >> M: +94 777 219 791 >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> Skype : malaka.sampath.silva >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >> Blog : http://mrmalakasilva.blogspot.com/ >> >> WSO2, Inc. >> lean . enterprise . middleware >> http://www.wso2.com/ >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Save a tree -Conserve nature & Save the world for your future. Print this >> email only if it is absolutely necessary. >> >> _______________________________________________ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > _______________________________________________ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Prabath Abeysekara Technical Lead WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
