Demo Data from EDBT 2026 / reviewers in the wild / expert
Michael Golm
dblp:01/6234
· DBLP profile ↗
3ranked-venue papers
2as first author
0since 2021 · last 2009
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2 · 1 first-authorSystems, architecture and hardware · 1 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 100% |
Topics — the 1 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Operating systems › operating system design
component-based operating system |
0.0 | 1 | 2002 | The JX Operating System · USENIX ATC, General Track 2002 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2009 | Anatomy of a Visual Domain-Specific Language Project in an Industrial Context
Christoph Wienands, Michael Golm |
MoDELS | 2 |
| 2002 | The JX Operating System
Michael Golm, Meik Felser, Christian Wawersich, Jürgen Kleinöder |
USENIX ATC, General Track | 1 |
| 2001 | Beyond Address Spaces - Flexibility, Performance, Protection, and Resource Management in the Type-Safe JX Operating SystemabstractEarly type-safe operating systems were hampered by poor performance. Contrary to these experiences we show that an operating system that is founded on an object-oriented, type-safe intermediate code can compete with MMU-based microkernels concerning performance while widening the realm of possibilities. Moving from hardware-based protection to software-based protection offers new options for operating system quality, flexibility, and versatility that are superior to traditional process models based on MMU protection. However, using a type-safe language-such as Java-alone, is not sufficient to achieve an improvement. While other Java operating systems adopted a traditional process concept, JX implements fine-grained protection boundaries. The JX System architecture consists of a set of Java components executing on the JX core that is responsible for system initialization, CPU context switching and low-level domain management. The Java code is organized in components which are loaded into domains, verified, and translated to native code. JX runs on commodity PC hardware, supports network communication, a frame grabber device, and contains an Ext2-compatible file system. Without extensive optimization this file system already reaches a throughput of 50% of Linux. Michael Golm, Jürgen Kleinöder, Frank Bellosa |
HotOS | 1 |