FIT for SOA? Introducing the F.I.T.-Metric to Optimize the Availability of Service Oriented Architectures

Frischbier, Sebastian; Buchmann, Alejandro; Putz, Dieter

doi:10.1007/978-3-642-25203-7_6

Cited by 3 publications

(5 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, different data sources may use variations of these identifiers or identifiers change over time due to mergers so that the same instrument instance is represented by different symbols based on their context. For example, the stock of Apple Inc. is known as AAPL on NASDAQ 2 but as APC on Börse Frankfurt 3 while being associated with the ISIN US0378331005 as a unique identifier; moreover market data about this stock is available as AAPL.OQ (Reuters) 4 or AAPL:US (Bloomberg) 5 . Hence, data must be mapped and normalized at runtime.…”

Section: Background: Financial Data Feedsmentioning

confidence: 99%

“…This approach massively reduces the heterogeneity of our system landscape from a development point of view by encapsulating business functionality into services exposed only via a homogeneous interface and accessible via an encrypted protocol. Legacy applications are integrated by exposing their functionality to our microservice universe via a REST service as facade (e.g., Oracle's REST Data Service); the legacy system behind this facade can be optimized or replaced to reduce operational heterogeneity without impacting depending services [5]. With this platform approach we can transparently combine pull-and push-based systems, seamlessly reuse and recombine existing functionality for products to exploit synergies, and reduce complexity on the infrastructure level by consolidating and standardizing systems.…”

Section: Technology: Modular Platform and Hybrid Infrastructuresmentioning

confidence: 99%

See 1 more Smart Citation

Managing the Complexity of Processing Financial Data at Scale - An Experience Report

Frischbier¹,

Paic²,

Echler³

et al. 2019

Complex Systems Design &Amp; Management

Self Cite

View full text Add to dashboard Cite

Financial markets are extremely data-driven and regulated. Participants rely on notifications about significant events and background information that meet their requirements regarding timeliness, accuracy, and completeness. As one of Europes leading providers of financial data and regulatory solutions vwd processes a daily average of 18 billion notifications from 500+ data sources for 30 million symbols. Our large-scale geo-distributed systems handle daily peak rates of 1+ million notifications/sec. In this paper we give practical insights about the different types of complexity we face regarding the data we process, the systems we operate, and the regulatory constraints we must comply with. We describe the volume, variety, velocity, and veracity of the data we process, the infrastructure we operate, and the architecture we apply. We illustrate the load patterns created by trading and how the markets' attention to the Brexit vote and similar events stressed our systems.

show abstract

Section: Background: Financial Data Feedsmentioning

confidence: 99%

Section: Technology: Modular Platform and Hybrid Infrastructuresmentioning

confidence: 99%

Managing the Complexity of Processing Financial Data at Scale - An Experience Report

Frischbier¹,

Paic²,

Echler³

et al. 2019

Complex Systems Design &Amp; Management

Self Cite

View full text Add to dashboard Cite

show abstract

“…We evaluate our monitoring approach in terms of performance, scalability and precision in Section V. We discuss related work in Section VI. We summarize our findings in Section VII and outline steps necessary to apply the FIT-metric [7] to eventbased applications as part of ongoing and future work.…”

Section: Motivationmentioning

confidence: 99%

“…The FIT metric [7], for example, identifies and ranks hotspots in a SOA-based enterprise system landscape by quantifying the criticality of relationships between services. It deduces how important any given participating system is for the whole application landscape based on its Function (business criticality), Integration (impact on other participating systems) and Traffic (actual usage).…”

Section: Conclusion Ongoing and Future Workmentioning

confidence: 99%

Effective Runtime Monitoring of Distributed Event-Based Enterprise Systems with ASIA

Frischbier

Turan

Gesmann³

et al. 2014

2014 IEEE 7th International Conference on Service-Oriented Computing and Applications

Self Cite

View full text Add to dashboard Cite

Abstract-Cyber Physical Systems (CPS), interconnected smart devices in the Internet of Things (IoT) and other data sources are increasingly bridging the gap between the physical and digital world by providing fine-grained data about real-world events. Enterprise software systems are adopting the paradigm of eventbased systems (EBS) to enable them to react to meaningful events in a timely manner. Smart supply chains fusing dynamic sensor data with information provided by backend-systems are one such example of event-based enterprise systems.Monitoring their global state in an effective way for runtime governance remains an open research challenge: providing the required type of information while trading off precision for costs. We previously introduced application-specific integrated aggregation (ASIA) as a means for collecting metadata in distributed event-based systems. In this paper, we show how ASIA can support IT Service Management in monitoring and governing decentralized event-based enterprise systems at runtime. We present a dashboard based on industry-strength technology as proof of concept and discuss how to integrate usage statistics provided on-the-fly by ASIA into metrics for runtime governance. We evaluate our monitoring approach in terms of performance, scalability and precision. I. MOTIVATIONIn the Internet of Things (IoT), a multitude of data sources offer continuous information about events taking place in the physical world. Prominent examples are temperature readings about temperature-sensitive freight or geographical coordinates of trucks delivering goods. Enterprise software systems today have to bridge the gap between the physical and the digital world by fusing the information provided by Cyber Physical Systems (CPS) and other data sources with metadata provided by backend systems [3].Event-based systems (EBS) within an enterprise application landscape complement service-oriented architectures (SOA) to leverage streams of dynamic real-time information and react to meaningful events in a timely manner [2]. For example, smart supply chain management (SCM) systems can automatically redirect delivery routes of cargo containers or trigger processes to replenish goods if they detect delays along the supply chain based on incoming notifications; financial trading applications decide to buy or sell company shares based on real-time news feeds; and data centre management systems scale and reassign resources based on detected usage patterns [17]. In these examples, services in a SOA are invoked by components of an EBS that receive or detect meaningful events. Service invocations, in turn, can result in meaningful changes to a system, triggering components of an EBS to publish events.EBS are anonymous, information-centric networks. They consist of loosely-coupled software components with different roles that communicate asynchronously using messages: Publishers are components that publish notifications if they have detected a specific event taking place. Subscribers are components that want to be not...

show abstract

“…Service-oriented concepts have already provided significant steps towards more flexible enterprise software systems within companies (Frischbier and Petrov, 2010). However, they are not yet ready for unanticipated changes across company borders and do not yet provide the selfmonitoring capabilities needed (Frischbier et al, 2011).…”

Section: Architectural Perspectivementioning

confidence: 99%

Emergence as Competitive Advantage - Engineering Tomorrow’s Enterprise Software Systems

Frischbier¹,

Gesmann²,

Mayer³

et al. 2012

Proceedings of the 14th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Companies rely heavily on complex software systems and tightly integrated supply-chains to serve their customers in increasingly fast changing markets. To gain competitive advantage in such a setting, companies must adapt their processes, products and inter-organizational relationships quickly to changing environments. In the future, enterprise software systems must be explicitly designed for flexibly switching intensive interorganizational relationships and for rapidly implementing changes in requirements or context while retaining existing functionality and user acceptance. In this position paper we introduce the notion of emergence in enterprise software systems as a guiding principle. Emergent Enterprise Software Systems (EESS) will be capable of reacting to changes in the environment by adapting their behavior and exposing new functionality. The consequent challenges we face when designing, building and operating EESS are discussed.

show abstract

FIT for SOA? Introducing the F.I.T.-Metric to Optimize the Availability of Service Oriented Architectures

Cited by 3 publications

References 31 publications

Managing the Complexity of Processing Financial Data at Scale - An Experience Report

Managing the Complexity of Processing Financial Data at Scale - An Experience Report

Effective Runtime Monitoring of Distributed Event-Based Enterprise Systems with ASIA

Emergence as Competitive Advantage - Engineering Tomorrow’s Enterprise Software Systems

Contact Info

Product

Resources

About