Demo Data from VLDB 2026 / reviewers in the wild / expert
Michael Ogg
dblp:00/4675
· DBLP profile ↗
3ranked-venue papers
2as first author
0since 2021 · last 2000
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 2 · 2 first-authorSecurity and privacy · 1
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 |
Services computing and microservices · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
2 papers |
Distributed systems · 100% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Services computing and microservices
middleware |
0.0 | 1 | 2000 | A middleware overview: goals, research issues, and coded examples (abstract) · PODC 2000 |
Distributed systems
middleware |
0.0 | 1 | 2000 | A middleware overview: goals, research issues, and coded examples (abstract) · PODC 2000 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2000 | A middleware overview: goals, research issues, and coded examples (abstract)abstractIn this tutorial, I will focus on the roles, types, and issues of middleware. I will give a short overview of the software problems that middleware addresses and (mostly) solves. I will do a survey of the different kinds of middleware and their applicability to diverse problem domains. I will spend somewhat longer discussing, with examples, CORBA, RMI, and Jini, in particular pointing out relative strengths and weaknesses. Finally, I will discuss some of the major and outstanding research issues, especially those that a PODC audience might find stimulating, and suggest where and how solutions might be found. Michael Ogg |
PODC | 1 |
| 1999 | CosNamingFT - A Fault-Tolerant CORBA Naming ServiceabstractThis paper describes the design and implementation of a fault-tolerant CORBA naming service-CosNaming FT. Every CORBA object is accessed through its Interoperable Object Reference (IOR), which is registered with the CORBA name service. The name service therefore is a critical gateway to all objects in a distributed system; to avoid having a single point of failure, the name service should be made fault-tolerant. CosNamingFT uses the GroupPac package, a CORBA-compliant suite of protocols, to replicate the name server. GroupPac services are built from Common Object Services that function as building blocks to implement fault-tolerant applications. This paper aims to demonstrate the usefulness of some of these object services and to demonstrate the importance of open solutions issues in replicating distributed objects. Lau Cheuk Lung, Joni da Silva Fraga, Jean-Marie Farines, Michael Ogg, Aleta Ricciardi |
SRDS | 4 |
| 1995 | Architecture Decisions for Wide Area Applications (Abstract)abstractNo abstract available. Michael Ogg, Aleta Ricciardi |
PODC | 1 |