ACM Home Page
Please provide us with feedback. Feedback
Java support for data-intensive systems: experiences building the telegraph dataflow system
Full text PdfPdf (1.38 MB)
Source ACM SIGMOD Record archive
Volume 30 ,  Issue 4  (December 2001) table of contents
COLUMN: Systems and prototypes table of contents
Pages: 103 - 114  
Year of Publication: 2001
ISSN:0163-5808
Authors
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 30,   Citation Count: 10
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/604264.604282
What is a DOI?

ABSTRACT

Database system designers have traditionally had trouble with the default services and interfaces provided by operating systems. In recent years, developers and enthusiasts have increasingly promoted Java as a serious platform for building data-intensive servers. Java provides a number of very helpful language features, as well as a full run-time environment reminiscent of a traditional operating system. This combination of features and community support raises the question of whether Java is better or worse at supporting data-intensive server software than a traditional operating system coupled with a weakly-typed language such as C or C++.In this paper, we summarize and discuss our experience building the Telegraph dataflow system in Java. We highlight some of the pleasures of coding with Java, and some of the pains of coding around Java in order to obtain good performance in a data-intensive server. For those issues that were painful, we present concrete suggestions for evolving Java's interfaces to better suit serious software systems development. We believe these experiences can provide insight for other designers to avoid pitfalls we encountered and to decide if Java is a suitable platform for their system.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
IBM alphaWorks Home Page. http://www.alphaworks.ibm.com/, 2001.
 
2
Java 2 Platform API Specification, JDK 1.4. http://java.sun.com/j2se/1.4/docs, 2001.
 
3
OptimizeIt Home Page. http://www.optimizeit.com/, 2001.
 
4
PostgreSQL. http://www.postgresql.com/, 2001.
 
5
VTune Tool Home Page. http://developer.intel.com/vtune/analyzer/, 2001.
6
 
7
M. K. Bergman. The Deep Web: Surfacing Hidden Value, White Paper. http://www.brightplanet.com/deepcontent/index.asp/, September 2001.
8
 
9
G. Czajkowski, T. Mayr, P. Seshadri, and T. von Eicken. Resource Control for Java Database Extensions. 5th USENIX Conference on Object-Oriented Technologies and Systems, May 1999.
 
10
O. Doederlein. The Java Performance Report - Part III. http://www.javalobby.org/fr/-html/frm/javalobby/features/-jpr/part3.html, September 2000.
11
 
12
 
13
Hamilton, James. Personal Communication. Feb 2001.
14
 
15
Hong, Wei. Personal Communication. Feb 2001.
 
16
IBM DB2. IBM DB2 Reference Manual. Version 6.1.
17
 
18
D. Kegel. The C10K Problem. http://www.kegel.com/c10k.html, 2001.
19
20
21
 
22
D. C. Schmidt. Reactor: An Object Behavioral Pattern for Demultiplexing and Dispatching Handles for Synchronous Events. Pattern Languages of Programs Conference, August 1994.
23
 
24
M. Welsh. Non-blocking I/O for Java. http://www.cs.berkeley.edu/ mdw/proj/java-nbio, September 2001.
 
25
M. Welsh and D. Culler. Jaguar: Enabling Efficient Communication and I/O in Java. Concurrency Practice and Experience, Dec 1999.
26
 
27
N. Wyatt and A. Carlson. Cloudscape 3.6, A Technical Overview. A Cloudscape White paper, March 2001. see http://www.cloudscape.com/products/whitepapers.jsp.

CITED BY  10
Collaborative Colleagues:
Mehul A. Shah: colleagues
Michael J. Franklin: colleagues
Samuel Madden: colleagues
Joseph M. Hellerstein: colleagues