|
|
Sponsored Content
Special Forums
UNIX and Linux Applications
Virtualization and Cloud Computing
Data Warehouse evolving towards CEP?
Post 302178227 by Linux Bot on Tuesday 25th of March 2008 04:10:13 AM
03-25-2008
Data Warehouse evolving towards CEP?
vincent
Tue, 25 Mar 2008 03:15:31 +0000
Whilst at DAMA last week I managed to miss the Teradata talk on “active data warehouses“. Luckily James Taylor blogged comprehensively on the talk, and although it seems Teradata declined to make the presentation available to attendees, I’m guessing it was pretty much the same as this one (”Google is your friend”/”Time to Yahoooo”, etc).
Now, DAMA is targeted at Data Professionals, many of whom also have to deal with data warehouses to store longer term data for analysis and analytics. Yet here is a highly respected DW company, who sells mostly in the DW space, advocating an event-driven approach to analysing your data. Fascinating! Furthermore, they presented “event-driven” use cases (albeit old ones) such as real-time event processing for the airline industry that we have already seen adopt CEP. But then, the use of an ESB, event-store, and rule-engine as a DIY CEP engine is a perfectly valid approach to event processing (cost notwithstanding) versus an off-the-shelf CEP engine (not mentioning any names of course).
At the same time, we see a similar development in the BI space as indicated by this IntelligentEnterprise comment on BI Emerging Technologies. The key term here is “in-memory analytics” although some of the other “emerging technologies” may also seem familiar (namely: advanced visualization - cue TIBCO Spotfire - and cloud computing - although in this case they refer to hardware clouds rather than event clouds).
Source...
Tue, 25 Mar 2008 03:15:31 +0000
Whilst at DAMA last week I managed to miss the Teradata talk on “active data warehouses“. Luckily James Taylor blogged comprehensively on the talk, and although it seems Teradata declined to make the presentation available to attendees, I’m guessing it was pretty much the same as this one (”Google is your friend”/”Time to Yahoooo”, etc).
Now, DAMA is targeted at Data Professionals, many of whom also have to deal with data warehouses to store longer term data for analysis and analytics. Yet here is a highly respected DW company, who sells mostly in the DW space, advocating an event-driven approach to analysing your data. Fascinating! Furthermore, they presented “event-driven” use cases (albeit old ones) such as real-time event processing for the airline industry that we have already seen adopt CEP. But then, the use of an ESB, event-store, and rule-engine as a DIY CEP engine is a perfectly valid approach to event processing (cost notwithstanding) versus an off-the-shelf CEP engine (not mentioning any names of course).
At the same time, we see a similar development in the BI space as indicated by this IntelligentEnterprise comment on BI Emerging Technologies. The key term here is “in-memory analytics” although some of the other “emerging technologies” may also seem familiar (namely: advanced visualization - cue TIBCO Spotfire - and cloud computing - although in this case they refer to hardware clouds rather than event clouds).
Source...
|
|
LEARN ABOUT SUNOS
in.talkd
in.talkd(1M) System Administration Commands in.talkd(1M) NAME
in.talkd, talkd - server for talk program SYNOPSIS
in.talkd DESCRIPTION
talkd is a server used by the talk(1) program. It listens at the UDP port indicated in the ``talk'' service description; see services(4). The actual conversation takes place on a TCP connection that is established by negotiation between the two machines involved. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWrcmds | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), talk(1), inetadm(1M), inetd(1M), svcadm(1M), services(4), attributes(5), smf(5) NOTES
The protocol is architecture dependent. The in.talkd service is managed by the service management facility, smf(5), under the service identifier: svc:/network/talk Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). Responsibil- ity for initiating and restarting this service is delegated to inetd(1M). Use inetadm(1M) to make configuration changes and to view config- uration information for this service. The service's status can be queried using the svcs(1) command. SunOS 5.10 31 Jul 2004 in.talkd(1M)