brenda m. michelson 's Library tagged → View Popular, Search in Google
Paul Vincent on events and Higgs boson:
"Earlier this month Dr Neil Geddes gave a fascinating presentation at the BCS on “Data Processing at the Large Hadron Collider”, describing how LHC experiments create 1 Billion events per sec of which they can record in detail 100 events per sec."
I would edit this to be: "Make event-driven architecture and complex event processing first-class citizens", but I can live with the following from Gartner:
"Make event-driven architecture and complex event processing first-class citizens in data modeling work and metadata repositories."
"StreamBase allows business analysts, actuaries, quantitative contributors and developers to share a common language. An event-driven integration whiteboard, if you will, that compiles to efficient optimized native binary code. Add Erlang for development of analytics like MACD and you have a powerful combination."
..."Learn more by watching Darach's presentation here, and follow him on Twitter at @darachennis"
"The first comprehensive survey on event processing was accepted for publication in ACM Computing Surveys, the leading avenue of publication for surveys. the survey was co-authored by GIANPAOLO CUGOLA and ALESSANDRO MARGARA and is available from the Politecenico di Milano webpage, the paper surveys the area from the days of active databases until current products. The paper view complex event processing, data streams and active databases as kind of information flow processing, and as such information flow contains both events and data, thus the scope of this survey is quite large."
"The second Dagstuhl seminar on event processing took place in May 2010. This five-day meeting was oriented to work toward a comprehensive document that would explain event processing and how it relates to other technologies and suggest future work in terms of standards, challenges, and shorter-term research projects.
The 45 participants came from academia and industry, some of them out of the event processing field. The teams continued the work after the conference and have summarized their findings in this document. The chapters were written by different teams and then edited for consistency. "
I was on this call. Nice of Sandy to document it for all of us. I'm interested in the Event Processing ties. Will get more info from SAP on Event Insight closer to the Feb 23 launch.
"A group of bloggers had an update today from Steve Lucas, GM of the SAP business analytics group, covering what happened in 2010 and some outlook and strategy for 2011.
No surprise, they saw an explosion in growth in 2010: analytics has been identified as a key competitive differentiator for a couple of years now due to the huge growth into the amount of information and event being generated for every business; every organization is at least looking at business analytics, if not actually implementing it. SAP has approached analytics across several categories: analytic applications, performance management, business intelligence, information management, data warehousing, and governance/risk/compliance. In other words, it’s not just about the pretty data visualizations, but about all the data gathering, integration, cleanup, validation and storage that needs to go along with it. They’ve also released an analytics appliance, HANA, for sub-second data analysis and visualization on a massive scale. Add it all up, and you’ve got the right data, instantly available..."
"In this IBM® Redbooks® publication, we discuss and describe the positioning, functions, capabilities, and advanced programming techniques for IBM InfoSphere™ Streams.
Stream computing is a new paradigm. In traditional processing, queries are typically run against relatively static sources of data to provide a query result set for analysis. With stream computing, a process that can be thought of as a continuous query, that is, the results are continuously updated as the data sources are refreshed. So, traditional queries seek and access static data, but with stream computing, a continuous stream of data flows to the application and is continuously evaluated by static queries. However, with IBM InfoSphere Streams, those queries can be modified over time as requirements change."
Forrester embraces Event Processing... [Told you I was early]
"In “The Next Big Architecture Movement: Business Events,” Forrester’s VP and Principal Analyst John Rymer and Senior Analyst Mike Gualtieri will talk about business event architecture (BEA). Enterprise architects can use BEA to make business capabilities much more responsive to change. BEA is not just about event processing platforms — it’s a larger architecture paradigm that unifies SOA with other flexible platforms such as business rules management systems and business process management. Where rules can automate responses to individual occurrences, BEA can enable awareness of and consistent responses to patterns of events for much more complex scenarios. Just when you thought it was safe, another architecture movement arrives to rock your world!"
Enterprise Architects don’t always take the “event” viewpoint, and instead focus on the process or value chains in the business. However, these high level processes and value chain links can benefit from, or use, real-time event processing, and analysing these events can be very useful for each step, department or service in understanding what services and technologies apply.
So, my challenge for Enterprise Architects is to look at their high-level business process or value chain, and consider for each step where an event viewpoint and real-time business event handling can provide some benefit.
How many of your systems are designed to issue event notifications to other systems when information is updated? In my own personal experience, this is not a common pattern. Instead, what I more frequently see is systems that always query a data source (even though it may be an expensive operation) because a change may have occurred, even though 99% of the time, the data hasn’t. Rather than optimizing the system to perform as well as possible for the majority of the requests by caching the information to optimize retrieval, the systems are designed to avoid showing stale data, which can have a significant performance impact when going back to the source(s) is an expensive operation.
With so much focus on web-based systems, many have settled into a request/response type of thinking, and haven’t embraced the nearly real-time world.
Nice event processing metaphor by Jeff Adkins: "Detect, Derive, Decide and Do". Reflects the separation of concerns and therefore implementation options.
Selected Tags
Related Tags
Top Contributors
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo
