How orcid/orcid-source works
Project type and purpose
• ORCID-Source is a monorepo implementing the ORCID Registry: a full-stack, highly modular Java/Spring micro-service ecosystem that powers a public researcher identifier system (APIs, web UI, background jobs).
Top-level components (modules/directories)
• UI & API façade
• orcid-web & orcid-web-frontend: the user-facing web application (FreeMarker & AngularJS).
• orcid-web-proxy, orcid-lb, orcid-haprouter: Nginx/Haproxy and load-balancer configs.
• Public & internal REST APIs
• orcid-api-web & orcid-pub-web: public ORCID REST endpoints (Jersey + Spring MVC).
• orcid-internal-api: internal API for member organizations.
• Core business logic & data access
• orcid-core: domain services, adapters, manager layer (Spring, JPA/Hibernate).
• orcid-persistence: DAO layer, Liquibase schema migrations, Postgres persistence.
• Asynchronous processing
• orcid-activemq: JMS broker config & listeners.
• orcid-message-listener & orcid-activities-indexer: background consumers that read from S3 or JMS, update Solr indexes.
• orcid-scheduler-web: scheduled jobs (email trickle, cleanup, indexing).
• Shared libraries & utilities
• orcid-api-common, orcid-utils: shared code for clients, analytics, JAXB, common filters.
• Infrastructure & deployment
• Dockerfile, docker-compose.yml, Jenkinsfile, GitHub workflows, environment files, HAProxy/Nginx configs.