---
# System prepended metadata

title: RFC For Converging Backend Repos

---

## Summary
Converging Backend Repositories
## Motivation
> To optimize resource and make the client onboarding easier    
## Requirements
- Management API Jar and Combine Scheduler with notification
- Analyse impact, routes, name conflicts
- Handle parent pom and child pom
- Release Pipeline, Fluent Bit And Config
- Make Sure All The Code Are In Sync
- Docker File And Project Yaml
- Test All The APIs
- check for reactor-build
## Repositories after re-arch
 1. apiwiz-core-api-v2 (4 JARs)
	 - cloud-app
	 - linter-agent
	 - notification-agent
     - api-scheduler
 2. apiwiz-build-services (3 JARs)
	 - mock-agent
	 - testsuite-agent & inspector-agent (apiwiz-build-agent-app.jar)
	 - consent-agent
 3. apiwiz-gw-connectors (1 JAR)
 4. apiwiz-runtime-services (5 JARs)
	 - monitor-agent
	 - api-checker & api-visualizer & api-security (apiwiz-runtime-agent-app.jar)
	 - monetization 
	 - logger
	 - builder
 5. apiwiz-core-api(SSO)(2 JAR)
## Impact
- base path will change for these apps (UI needs to change for both workspace and devportal)
    - cloud-app
    - api-scheduler
    - notification-agent
    - inspector-api
    - mock-api
    - testsuite-api
    - consent-api
    - api-scanner
    - api-reports
    - monitor-api
    - api-builder
    - logger-api
- time to build will increase in jenkins for core-api
## Effort Estimation
- 5 Days Of Backend , 1 Day for UI and 2 Days Of Devops 
## Test Cases
- Test Happy Flow For All The Impacted Repos
#### Components
- (itorix/apiwiz-*)
## Approvers
|Module| Approver |
|--|--|
| Backend | Adeeb |
| Frontend | Shashil |
| QA | Chinmayee |