How solop-develop/adempiere-grpc-server works
Project type and purpose
• This is a backend microservice (“ADempiere gRPC Server”) written in Java 17 that exposes ADempiere ERP functionality over gRPC.
• It decouples ADempiere into multiple functional modules (Access, Dictionary, Business, POS, Workflow, Dashboarding, etc.) and is deployed via Docker (with Envoy as a gRPC proxy) and connects to a PostgreSQL database.
File structure
• Top level:
• src/main/proto – .proto definitions for every service (record management, reporting, accounting, etc.)
• src/main/java/org/spin/grpc – generated stubs + service logic packages (one package per .proto service)
• src/main/java/org/spin/base, /dictionary, /dashboarding, /pos, /server, /compiere, /legacy – core business logic, DB setup, utility classes, legacy adapter code
• docker-compose and docker folders – definitions for Postgres, Envoy proxy, the backend container, environment files
• build.gradle, gradlew, gradle.properties – build configuration
• Patches directory overlays customized model and process classes into the ADempiere core at runtime.
README for additional insights
• Describes running modes (gradle run, standalone YAML, Docker images)
• Highlights use of Envoy as a sidecar/proxy in front of the gRPC server
• Lists required Docker images (Postgres, backend, proxy, frontend)
• Emphasizes the gRPC + Protobuf technology stack and that the server entry point is org.spin.server.AllInOneServices