GitHub user bobbai00 closed a discussion: Docker Image Organization Strategy for Texera's Microservices
## Background As we are preparing for the release, we need to decide on a strategy for organizing our Docker images basedo on our microservices architecture. ## Options ### Option 1: Repository-Level Identification Each microservice has its own dedicated Docker repository. **Image naming pattern:** - `apache/texera-file-service:1.1.0` - `apache/texera-web-application:1.1.0` - `apache/texera-config-service:1.1.0` - etc. If we choose this approach, we will need to create and maintain 8 image repositories. ### Option 2: Tag-Level Identification All microservices share a single Docker repository, differentiated by tags. **Image naming pattern:** - `apache/texera:file-service-1-1-0` - `apache/texera:web-application-1-1-0` - `apache/texera:config-service-1-1-0` - etc. ## Initial investigation After investigation, **Option 1** appears to be a more common approach. Please share your thoughts on this! GitHub link: https://github.com/apache/texera/discussions/4046 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
