How javaito/holandacatalinafw works
Project type and purpose
• From README ("Holanda Catalina is a powerful framework to create your own solution based on a micro-services architecture…") and the file tree (packages like cloud, io/net/http, layers, service, security), this is a Java microservices framework, not a single runnable service. It provides core infrastructure (networking, RPC, eventing, data-access layers, plugins, scripting, security, etc.) so Java developers can build distributed microservices with minimal boilerplate.
File structure
Top-level modules:
• src/main/java/org/hcjf/cloud → core cloud registry, message bus, orchestrator
• src/main/java/org/hcjf/io/net and io/net/http → transport (TCP, HTTP/1.1 & HTTP/2), clients, servers, proxies
• src/main/java/org/hcjf/layers → the “layer” pattern (cache, CRUD, query, scripting, plugins, distributed layers)
• src/main/java/org/hcjf/service → service lifecycle, threads, sessions
• src/main/java/org/hcjf/service/security → permission model, security manager
• support packages: encoding, errors, events, io/console, io/fs, kubernetes integration, logging, names, properties, utils
Build & deployment: Maven (pom.xml), CI (GitHub Actions, Travis, GitLab CI), examples folder with simple salary service.
README for additional insights
• You start by defining a Service
• The framework wires it into the Cloud registry
• Exposes HTTP/REST endpoints or other transports
• Layers provide data access, caching, query, etc.
Be detailed yet clear
• Cross-cutting concerns: logging, security, naming.
• How the customer’s code (examples) sits on top of this core.