Live Techie

Before we come across the situation of drawing the detailed border between both the products, we should not forget that both the products started with different perspectives to solve the Complex Event Processing (CEP) Problem. TIBCO BusinessEvents (BE) was developed as a TIBCO's approach to solving the CEP. On the other hand, StreamBase was originally the product of StreamBase Systems which was then acquired by TIBCO on June 11, 2013, and rebranded as now known TIBCO StreamBase. Where TIBCO's CEP product TIBCO BusinessEvents was primarily focused to be an Event-Driven Tool to solve the CEP but the StreamBase has been broadly focused on Streaming Analytics and assist in extraction of data flow pattern in Real-Time. Since the same thing can also be achieved with BE. Therefore, at a high level, both are somehow is majorly about the Processing of the Event. Hence arises the question, "Then now, Why do we have two separate TIBCO Products to achieve the same thing ?" !

Complex Event Processing (CEP) is a set of technologies that allows  events  to be processed on a continuous basis. TIBCO offers a complete platform to enable CEP that is,  TIBCO BusinessEvents. It is a Rule Engine where Event-Based Programming Paradigm is followed that has Java at its core. CEP is unlike conventional event processing technologies, however, in that it treats all events as potentially significant and records them asynchronously. CEP Applications are event-driven in nature, therefore some of its aspect has real-time behavior. For example, “Situation Awareness,” “Sense and Respond,” or “Track and Trace” are some of the aspects that CEP application can have that overlap in actual business situations. Learning TIBCO BusinessEvents (BE) for developing such CEP Solution can open up the world of Even Processing for developers. TIBCO BusinessEvents Rule Engine's working can't be understand without understanding what "Run to Completion" Cycle is

TIBCO BusinessEvents (BE) utilizes, Run to Completion Cycle (RTC Cycle) and Conflict Resolution Cycle (CRC). RTC and CRC do play very significant role in designing the Complex Event Processing (CEP) Solution while using TIBCO BusinessEvents as a developing tool. Therefore it is very much important to learn about the RTC Cycle and CRC Cycle. RTC and CRC utilizes a runtime environment, Rete Network, to hold all the rules, triggers and relationships. Rete Network is based on  Rete Algorithm  therefore it provides the basic property of Inference to the RTC in TIBCO BusinessEvents Engine. Here, one very important property of RTC and CRC to understand is that, " CRC is initiated wherever there is any change in Rete Network cause by external actions when the change is asserted to the Working Memory of the Engine, after which an RTC is initiated. RTC ends when Rule Agenda is Empty or no other rule action needed to be executed. This is called Inferencing or Forward Chaining. One RT