How semenishchev/lamada works
Project Type and Purpose
• This is a multi-module JVM framework (library/tool) for executing code remotely via Java functional interfaces (lambdas).
• Core “lamada” module provides the API, serialization, bytecode‐transformation (ASM) and abstractions (Sender, RemoteTargetManager).
• Three transport implementations live in sibling modules: redis‐impl, nats‐impl, netty‐impl.
File-structure Analysis
• Top‐level Gradle multi-project:
• build.gradle.kts, settings.gradle.kts (defines subprojects)
• src/… (core library)
• redis-impl/, nats-impl/, netty-impl/ (each with its own build.gradle.kts)
• Core library packages:
• asm/ (lambda bytecode correction & reconstruction)
• context/ (ExecutionContext, InvocationResult)
• defaults/ (FunctionalDistributedObject)
• serialization/ (Kryo setup, serializers, instantiators)
• sender/ (LoopbackSender)
• util/ (helpers, logging)
• DistributedExecutor, RemoteTargetManager, InstructionCommunicator, ObjectStub/Factory
• Implementation modules provide concrete Sender + RemoteTargetManager (e.g. RedisImplementation).
a. Main Components
• Application Code (your domain objects & lambdas)
• Core Lamada API
• DistributedExecutor
• DistributedObject / FunctionalDistributedObject
• ObjectStubFactory
• Serialization Pipeline
• ProjectKryo
• SimpleSerializers, ReferenceResolver
• ASM Pipeline
• LambdaReconstructor, LambdaCorrector
• Transport Abstractions
• Sender interface
• RemoteTargetManager interface
• Implementations (plugin modules)
• RedisImplementation (uses JedisPool, Redis queues)
• NatsImplementation
• NettyImplementation
• External Services
• Redis server
• NATS broker
• Raw TCP / Netty endpoints
• Loopback (in-process)
• LoopbackSender / LoopbackRemoteTargetManager
b. Relationships & Data Flow
1. App invokes DistributedExecutor.run()/runMethod()
2. Core serializes lambda + args via Kryo serializers
3. ASM utilities rewrite bytecode for remote invocation
4. InstructionCommunicator packages instruction
5. Sender.send() → pushes to transport (e.g., Redis list or pub/sub)
6. RemoteTargetManager on target JVM receives instruction
7. ExecutionContext unmarshals, invokes target method on DistributedObject stub
8. Result/exception serialized and sent back via Sender
9. Local side CompletableFuture completes
c. Architectural Patterns
• Plugin pattern: abstract Sender/RemoteTargetManager + multiple implementations
• Separation of concerns: API, serialization, bytecode transformation, transport
• Factory for stubs (ObjectStubFactory)
• Sync barrier via executor.sync() for consistent object registration
• Loopback for testing
d. Key Technologies
• Kotlin DSL Gradle multi-project build
• ASM for bytecode manipulation
• Kryo for serialization
• Jedis (Redis), Netty, NATS client libraries
Detail-Level
• Class‐grouping where helpful (e.g., list key classes under “Serialization”).
• Plugin hook (Sender & RemoteTargetManager interfaces) and how each implementation satisfies it.
• Sync() registration phase as a separate pre-execution step.