Distributed application development for three-tier architectures: Microsoft on Windows DNA

1998 ◽  
Vol 2 (2) ◽  
pp. 41-45 ◽  
Author(s):  
G.R. Voth ◽  
C. Kindel ◽  
J. Fujioka
Keyword(s):  
Application Development ◽  
Distributed Application ◽  
Windows Dna

Towards a Platform for Distributed Application Development

1998 ◽  
pp. 195-221 ◽  
Author(s):  
Gustavo Alonso ◽  
Claus Hagen ◽  
Hans-Jörg Schek ◽  
Markus Tresch
Keyword(s):  
Application Development ◽  
Distributed Application

Distributed application development

1991 ◽  
Vol 20 (4) ◽  
pp. 247-255 ◽  
Author(s):  
Hemant K. Jain ◽  
Sandeep Purao
Keyword(s):  
Application Development ◽  
Distributed Application

Framework to Enable Scalable and Distributed Application Development

2013 ◽  
Vol 4 (4) ◽  
pp. 64-81
Author(s):  
J. Aernouts ◽  
B. Claerhout ◽  
G. Ergeerts ◽  
M. Weyn
Keyword(s):  
Test Case ◽  
Input Rate ◽  
Critical Aspect ◽  
Application Development ◽  
Multiple Objects ◽  
Critical System ◽  
Specific Test ◽  
Distributed Application ◽  
Localization System ◽  
Generic Framework

In real-time middleware, latency is a critical aspect. When the input rate exceeds a certain threshold, queuing will result in an exponentially increasing delay. Distributed computing enables scaling so that this growing latency is kept at a constant minimum. When developing a generic framework, redundancy, platform independency, fault tolerance and transparency are important features that need to be taken care of. The authors’ test case, a localization system that is used to track multiple objects, is an example of such a heavy loaded and latency critical system. This specific test case requires that the framework quickly scales and reacts to changing loads, making this research challenging and innovative.

Structural Data Binding for Agile Changeability in Distributed Application Integration

2020 ◽  
pp. 51-81
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Web Services ◽  
Structural Data ◽  
Distributed Applications ◽  
Application Integration ◽  
Application Development ◽  
Distributed Application ◽  
Data Schema ◽  
Data Binding ◽  
Integration Problem ◽  
Application Specific

The interaction of distributed applications raises an integration problem that consists in how to satisfy the minimum interoperability requirements while reducing coupling as much as possible. Current integration technologies, such as Web Services and RESTful APIs, solve the interoperability problem but usually entail more coupling than required by the interacting applications. This is caused by sharing data schemas between applications, even if not all features of those schemas are actually exercised. This has its toll in application development agility. This chapter proposes compliance and conformance as the concepts to minimize coupling without impairing interoperability by sharing only the subset of the features of the data schema that are actually used. In addition, data binding between messages and the receiver's schema is done structurally in a universal and application-independent way. This eliminates the need for application-specific stubs and allows clients to use any server with which they comply and servers to replace any server to which they conform.

Sign in / Sign up

Export Citation Format

Share Document