Uses for Transaction List

[victor]

Hi,

I have been scratching my head over this. Can someone please explain to me the advantages of using transaction list versus say DAP other than obfuscation of DB layer in the strategy?

What are some uses of TL that would make me wonder why everyone and their mother is starting to use it around me, and I am sitting here, scratches my head and mumbling "why".

[Kubig]

Other case/customer is different, so the needs for routing and using DA layer are different so. I used database acces for reading dynamically parameters in routing strategy and transaction list as an backup of these parameters - default values. For static values or values which can be changed rarely I used TL too. Big advantage of this is, that you are able to develop one strategy for many different customer service.

[bublepaw]

I see following advantages of TL:

- ready to use GUI for manipulating TL (I know it is not perfect but still there is GUI)
- build in security for handling user access
- fast access
- permanent access - there is no situation in which routing is working but TL is not available

on top of those advantages there is also GAX which gives really nice GUI for manipulating TL content.

[Timur Karimov]

I'm not sure, but think that URS is load all data from list to the memory on start/update. So it's work even you lost the DB/config access.

[GMG]

Hello Victor,

I have different definition for TL, URS keeps all TL data in it's [glow=red,2,300]cache[/glow], as compare to other Database custom DIP, URS every time execute the query to Database.

In Case we update Tl data, them config server dynamically send update to URS to update the Data.


Just Imagine, you have [glow=red,2,300]10 million[/glow] call volume daily basis and your custom Database does not capable to handle 10 million execution, so best way to use is TL

Yes Timur, URS keep all TL data in it's memory. earlier I use to think that URS does DB query to config DB, in reality it has all data in it's cache... even you shutdown main Database, it's keep executing the strategy with last data available in it's memory.

--
Gaurav Gupta

[cavagnaro]

Really?? :S Ok for read but if you shutdown Database then how do you write?

[fnunezsa]

I'm starting to like TL as well, more now that GAX is available as a GUI to manage them, but one disadvantage of TLs when compared with DB DIP is that TLs are actually KVPs, i.e. there is a one-to-one relationship between a key an its value, so if your using TL for open/close hours, you will have to read the TL twice: one to get the opening hours and one to get the closing hours. Another thing that I've seen is that TLs can get corrupted and you won't notice it until you see that something is not working as expected and start troubleshooting your routing strategy to find that your passing the correct values to the ListGetDataCfg function, but for some reason it's not returning the expected values, then you need to export/import your TL options to get it fixed.