Case study 02 / Prototype
Distributed Application Service.
One request across two transport boundaries.
01 The problem
A client needs to request a computation without running it locally. This prototype explores how a socket-facing server can delegate execution to a separate Java process.
02 The solution
A TCP client talks to a server that looks up a remote compute service. Sample tasks include sorting, Fibonacci, and magic-square logic.
03 The architecture
The TCP server handles client connections. The compute engine exports a remote object through Java RMI and registers it under a shared name. The Compute and Task interfaces define how work is submitted and executed.
- 01TCP clientRequests a computation
- 02TCP serverResolves the remote compute service
- 03RMI engineExecutes the task via a shared interface
04 Engineering decisions
A shared task interface lets the same engine execute different computations without embedding each algorithm in the engine. The extra network hop adds a separate failure point, and the shared Java types couple the endpoints to the same runtime.