Design and Implementation of a Central Core for 6AM Mart Source Code using the Strangler Fig Approach (Migration to Microservices Architecture)
Budget: $3,000 – $5,000 USD
Project Title
Design and Implementation of a Central Core for 6AM Mart Source Code using the Strangler Fig Approach (Migration to Microservices Architecture)
6AM Mart System Overview
The 6AM Mart source code is a complete multi-vendor marketplace and delivery platform that provides multiple services simultaneously. The system includes the following main modules:
* Food
* Grocery
* Pharmacy
* Parcel
* Shop
In addition to these modules, the system includes operational components such as:
* Order Management
* Payment Processing
* User Management
* Vendor Management
* Delivery Management
The system is accessed through:
* Admin Panel
* Vendor Panel
* Customer Application
* Delivery Application
Current Platform Status
* Backend: Laravel
* Web: React
* Mobile: Flutter
The current architecture is monolithic, with an internal Core responsible for authentication, user management, and core business logic.
This Core is tightly coupled with the domain logic, and the system includes heavy database structures and concurrent processing, indicating significant complexity.
Therefore, the migration must follow a controlled approach using the Strangler Fig pattern, rather than a full system rewrite.
This project is not limited to Core development only; it is a complete end-to-end solution, including:
* System Integration
* Deployment
* Penetration Testing
The system is currently deployed on a Hetzner server (Production environment), but it has not been launched yet and is in the pre-launch stage.
The expected business launch is in approximately one month, and currently, there are no active users.
Project Objective
The goal of this project is to build the necessary infrastructure to transition the system into a true Microservices architecture.
In this approach:
* Shared components
* Heavy processing components
will be moved into a central Core, while other parts will be gradually separated into independent services.
The ultimate goal is to transform the entire system into Microservices progressively, without introducing unnecessary complexity or disruption.
Target Architecture
In the new architecture:
* A standalone Core will be developed outside of 6AM Mart
* 6AM Mart will connect to this Core
* The Core will act as the central hub of the system
In this structure:
* The internal Core of 6AM Mart must be disabled or removed
* No disruption to the system is allowed
* Modifications to 6AM Mart are allowed as needed, provided system functionality is not affected
Detailed architecture, Microservices definition, Core requirements, API design, integration approach, and other technical aspects are fully described in the attached PDF.
Database
The current system uses MySQL, but we are in the process of migrating to PostgreSQL.
Therefore, the Core and all new components must be designed and implemented based on PostgreSQL.
Authentication
All panels and applications must authenticate through the Core:
* Admin
* Vendor
* User
* Delivery
System Requirements
* Each module must be deployable on a separate server
* The Core must operate independently
* API traffic must not affect application performance
* The system must support high load
* Security must be fully implemented
* Proper testing must be conducted to eliminate vulnerabilities
* Future support and scalability must be considered
For more details, refer to the attached PDF.
Project Requirements
* Core architecture documentation (service boundaries, API contracts)
* Authentication system setup and integration with 6AM Mart
* Initial Core structure implementation
* Setup of development, testing, and staging environments
* Roadmap for extracting additional modules
Phase 1 & Phase 2 Scope
Full details are provided in the PDF.
The proposal must clearly specify:
Phase 1 includes:
* Core architecture design
* Authentication implementation (Keycloak)
* Migration of 6AM login system
* User Service
* Full integration with 6AM Mart
* Staging & Production setup
* Penetration testing
* Performance optimization
Phase 1 excludes:
Phase 2 includes:
* Gradual extraction of modules
* Full Microservices transformation
* Development of new services
Source Code Access
https://drive.google.com/file/d/1xdroBC86PwFkv04vGQvVY4a_vZpecR2i/view?usp=drive_link
References
* 6ammart.app
* CodeCanyon
Timeline
* Preferred duration: 2 to 3 weeks
* Maximum acceptable duration: 4 to 5 weeks (including full testing)
Any timeline beyond this will not be accepted.
Freelancer Proposal Requirements
After reviewing the project details, PDF, and source code, please submit a complete proposal including:
* Phase 1 and Phase 2 cost
* Delivery timeline for both phases
* Support duration
* Clear Phase 1 scope (what is included and what is not)
* Estimated timeline and cost for future phases
Selection Criteria
* Proven experience in Microservices (mandatory)
* Relevant project portfolio
* Strong architectural understanding
* Proper execution capability
* On-time delivery
Architecture quality and Microservices experience are more important than any other factor.
Important Notes
* There are specific questions in the PDF that must be answered in your proposal
* Submit your proposal only after reviewing the PDF and source code
* Proposals without proper review will not be considered
Final Outcome
After Phase 1, the system must be ready for initial production launch.
Final Note
Our primary focus is on proper execution, architectural quality, and timely delivery.
Since the launch is planned in approximately one-month, accurate timeline commitment and high-quality implementation are critical.
We look forward to receiving your detailed proposal.
Best regards,
Adel Abdullah
Design and Implementation of a Central Core for 6AM Mart Source Code using the Strangler Fig Approach (Migration to Microservices Architecture)
6AM Mart System Overview
The 6AM Mart source code is a complete multi-vendor marketplace and delivery platform that provides multiple services simultaneously. The system includes the following main modules:
* Food
* Grocery
* Pharmacy
* Parcel
* Shop
In addition to these modules, the system includes operational components such as:
* Order Management
* Payment Processing
* User Management
* Vendor Management
* Delivery Management
The system is accessed through:
* Admin Panel
* Vendor Panel
* Customer Application
* Delivery Application
Current Platform Status
* Backend: Laravel
* Web: React
* Mobile: Flutter
The current architecture is monolithic, with an internal Core responsible for authentication, user management, and core business logic.
This Core is tightly coupled with the domain logic, and the system includes heavy database structures and concurrent processing, indicating significant complexity.
Therefore, the migration must follow a controlled approach using the Strangler Fig pattern, rather than a full system rewrite.
This project is not limited to Core development only; it is a complete end-to-end solution, including:
* System Integration
* Deployment
* Penetration Testing
The system is currently deployed on a Hetzner server (Production environment), but it has not been launched yet and is in the pre-launch stage.
The expected business launch is in approximately one month, and currently, there are no active users.
Project Objective
The goal of this project is to build the necessary infrastructure to transition the system into a true Microservices architecture.
In this approach:
* Shared components
* Heavy processing components
will be moved into a central Core, while other parts will be gradually separated into independent services.
The ultimate goal is to transform the entire system into Microservices progressively, without introducing unnecessary complexity or disruption.
Target Architecture
In the new architecture:
* A standalone Core will be developed outside of 6AM Mart
* 6AM Mart will connect to this Core
* The Core will act as the central hub of the system
In this structure:
* The internal Core of 6AM Mart must be disabled or removed
* No disruption to the system is allowed
* Modifications to 6AM Mart are allowed as needed, provided system functionality is not affected
Detailed architecture, Microservices definition, Core requirements, API design, integration approach, and other technical aspects are fully described in the attached PDF.
Database
The current system uses MySQL, but we are in the process of migrating to PostgreSQL.
Therefore, the Core and all new components must be designed and implemented based on PostgreSQL.
Authentication
All panels and applications must authenticate through the Core:
* Admin
* Vendor
* User
* Delivery
System Requirements
* Each module must be deployable on a separate server
* The Core must operate independently
* API traffic must not affect application performance
* The system must support high load
* Security must be fully implemented
* Proper testing must be conducted to eliminate vulnerabilities
* Future support and scalability must be considered
For more details, refer to the attached PDF.
Project Requirements
* Core architecture documentation (service boundaries, API contracts)
* Authentication system setup and integration with 6AM Mart
* Initial Core structure implementation
* Setup of development, testing, and staging environments
* Roadmap for extracting additional modules
Phase 1 & Phase 2 Scope
Full details are provided in the PDF.
The proposal must clearly specify:
Phase 1 includes:
* Core architecture design
* Authentication implementation (Keycloak)
* Migration of 6AM login system
* User Service
* Full integration with 6AM Mart
* Staging & Production setup
* Penetration testing
* Performance optimization
Phase 1 excludes:
Phase 2 includes:
* Gradual extraction of modules
* Full Microservices transformation
* Development of new services
Source Code Access
https://drive.google.com/file/d/1xdroBC86PwFkv04vGQvVY4a_vZpecR2i/view?usp=drive_link
References
* 6ammart.app
* CodeCanyon
Timeline
* Preferred duration: 2 to 3 weeks
* Maximum acceptable duration: 4 to 5 weeks (including full testing)
Any timeline beyond this will not be accepted.
Freelancer Proposal Requirements
After reviewing the project details, PDF, and source code, please submit a complete proposal including:
* Phase 1 and Phase 2 cost
* Delivery timeline for both phases
* Support duration
* Clear Phase 1 scope (what is included and what is not)
* Estimated timeline and cost for future phases
Selection Criteria
* Proven experience in Microservices (mandatory)
* Relevant project portfolio
* Strong architectural understanding
* Proper execution capability
* On-time delivery
Architecture quality and Microservices experience are more important than any other factor.
Important Notes
* There are specific questions in the PDF that must be answered in your proposal
* Submit your proposal only after reviewing the PDF and source code
* Proposals without proper review will not be considered
Final Outcome
After Phase 1, the system must be ready for initial production launch.
Final Note
Our primary focus is on proper execution, architectural quality, and timely delivery.
Since the launch is planned in approximately one-month, accurate timeline commitment and high-quality implementation are critical.
We look forward to receiving your detailed proposal.
Best regards,
Adel Abdullah