6amMart Conversion to Microservices Architecture
Budget: $1,500 – $3,000 USD
*Project Description:*
We have purchased the full source code of 6amMart, and the goal of this project is to convert this system into a Microservices architecture. This process will be carried out gradually. As a first step, we need to design and implement a new, dedicated Core system that will operate alongside 6amMart and gradually replace its existing internal core.
The 6amMart source is a complete multi-vendor Marketplace and Delivery platform designed to provide multiple services simultaneously. This system includes the following main modules:
Food
Grocery
Pharmacy
Parcel
Shop
In addition to these modules, operational components such as order management, payments, users, vendors, and delivery agents are managed through different panels (Admin, Vendor, and User). The system is structured in multiple layers, including an Admin panel, Vendor panel, User application, and Delivery application.
From a technical perspective, the system is built with Laravel (backend), React (web frontend), and Flutter (mobile applications), and all components communicate via APIs. The current architecture is Monolithic, with an internal Core responsible for handling key logic such as authentication, user management, and other core data. The system also includes heavy database tables and multiple concurrent processes, reflecting its complexity.
The internal Core of the monolith is deeply entangled with domain logic, which makes the separation process require a controlled approach. Therefore, this migration should be carried out using the Strangler Fig pattern, not through a complete and sudden rewrite.
At this stage, the requirement is not limited to Core Development only, but also includes a complete end-to-end solution covering system integration, deployment, and penetration testing.
*Project Goal:*
The goal of this project is to establish an infrastructure that enables the system to transition toward a true Microservices architecture.
*In this approach:*
Shared components of the system
And parts involving heavy processing or large database tables
will be moved into a central Core, while other parts will be separated into independent modules.
The ultimate objective is to enable a smooth and complete transition of the entire 6amMart system into Microservices over time, without introducing unnecessary complexity.
*Target Architecture:*
*In the new architecture:*
A standalone Core will be developed outside of 6amMart
6amMart will connect to this Core
The Core will act as the central hub of the entire system
*Within this structure:*
The internal Core of 6amMart must be disabled or removed
This transition must not cause any disruption to the system or the new Core
Any modifications to the 6amMart source code are fully allowed (to any extent necessary), but must not negatively affect its functionality
Definition of Microservices in This Project
*In this project, Microservices means:*
Each module is fully independent in terms of code
Each service can run on a separate server
Each service has its own dedicated resources
Each service can be developed, deployed, and scaled independently
The Core will serve as the central coordinator and communication hub between all services.
*Core Requirements:*
The Core must be designed to:
Be fully compatible with 6amMart and operate seamlessly with it
Handle core functionalities such as Authentication and User management
Manage shared data and heavy-processing components
Support multiple independent services simultaneously (at least 10 to 30 services in the future)
Act as the central communication point for all services
Allow system growth and scalability
Enable easy addition of new services without major changes
Ensure that failures or high load in one service do not affect others
Maintain service-level isolation from a security perspective
Support high scalability and be capable of serving millions of users
*Core Technology:*
The Core should be implemented using Laravel or FastAPI.
Using FastAPI is recommended due to its asynchronous (async) nature, high scalability, and suitability as a central hub for managing multiple services.
Laravel can also be considered as a compatible option with the current system structure, either alongside or as an alternative.
Additionally, Keycloak can be used for authentication, as it is suitable for microservices architectures and supports standards such as OAuth2 and OIDC.
An event-driven integration layer should also be implemented to ensure that 6amMart and the Core remain loosely coupled from the beginning.
*Freelancer / Team Requirements*
This project requires real experience in system architecture.
*The freelancer or team must:*
Have thoroughly reviewed the 6amMart source code before submitting a proposal
Have a deep understanding of the system’s structure and complexity
Have practical experience in:
Core system design
System integration
Microservices architecture
Already have an existing Core structure or codebase to ensure faster delivery
*Project Requirements:*
* Core architecture documentation including service boundaries and API contracts
* Setting up the authentication system and integrating it with 6amMart
* Creating the initial Core structure
* Preparing development, testing, and staging environments
* Providing a roadmap for extracting other modules
*Timeline & Proposal:*
A timeframe of 1 to 2 weeks is considered as a proposed estimate. If the project requires more time, please provide your maximum estimated timeline along with your proposed price.
For further review, you can refer to the documentation available on the official website (6ammart.app) or CodeCanyon.
We have purchased the full source code of 6amMart, and the goal of this project is to convert this system into a Microservices architecture. This process will be carried out gradually. As a first step, we need to design and implement a new, dedicated Core system that will operate alongside 6amMart and gradually replace its existing internal core.
The 6amMart source is a complete multi-vendor Marketplace and Delivery platform designed to provide multiple services simultaneously. This system includes the following main modules:
Food
Grocery
Pharmacy
Parcel
Shop
In addition to these modules, operational components such as order management, payments, users, vendors, and delivery agents are managed through different panels (Admin, Vendor, and User). The system is structured in multiple layers, including an Admin panel, Vendor panel, User application, and Delivery application.
From a technical perspective, the system is built with Laravel (backend), React (web frontend), and Flutter (mobile applications), and all components communicate via APIs. The current architecture is Monolithic, with an internal Core responsible for handling key logic such as authentication, user management, and other core data. The system also includes heavy database tables and multiple concurrent processes, reflecting its complexity.
The internal Core of the monolith is deeply entangled with domain logic, which makes the separation process require a controlled approach. Therefore, this migration should be carried out using the Strangler Fig pattern, not through a complete and sudden rewrite.
At this stage, the requirement is not limited to Core Development only, but also includes a complete end-to-end solution covering system integration, deployment, and penetration testing.
*Project Goal:*
The goal of this project is to establish an infrastructure that enables the system to transition toward a true Microservices architecture.
*In this approach:*
Shared components of the system
And parts involving heavy processing or large database tables
will be moved into a central Core, while other parts will be separated into independent modules.
The ultimate objective is to enable a smooth and complete transition of the entire 6amMart system into Microservices over time, without introducing unnecessary complexity.
*Target Architecture:*
*In the new architecture:*
A standalone Core will be developed outside of 6amMart
6amMart will connect to this Core
The Core will act as the central hub of the entire system
*Within this structure:*
The internal Core of 6amMart must be disabled or removed
This transition must not cause any disruption to the system or the new Core
Any modifications to the 6amMart source code are fully allowed (to any extent necessary), but must not negatively affect its functionality
Definition of Microservices in This Project
*In this project, Microservices means:*
Each module is fully independent in terms of code
Each service can run on a separate server
Each service has its own dedicated resources
Each service can be developed, deployed, and scaled independently
The Core will serve as the central coordinator and communication hub between all services.
*Core Requirements:*
The Core must be designed to:
Be fully compatible with 6amMart and operate seamlessly with it
Handle core functionalities such as Authentication and User management
Manage shared data and heavy-processing components
Support multiple independent services simultaneously (at least 10 to 30 services in the future)
Act as the central communication point for all services
Allow system growth and scalability
Enable easy addition of new services without major changes
Ensure that failures or high load in one service do not affect others
Maintain service-level isolation from a security perspective
Support high scalability and be capable of serving millions of users
*Core Technology:*
The Core should be implemented using Laravel or FastAPI.
Using FastAPI is recommended due to its asynchronous (async) nature, high scalability, and suitability as a central hub for managing multiple services.
Laravel can also be considered as a compatible option with the current system structure, either alongside or as an alternative.
Additionally, Keycloak can be used for authentication, as it is suitable for microservices architectures and supports standards such as OAuth2 and OIDC.
An event-driven integration layer should also be implemented to ensure that 6amMart and the Core remain loosely coupled from the beginning.
*Freelancer / Team Requirements*
This project requires real experience in system architecture.
*The freelancer or team must:*
Have thoroughly reviewed the 6amMart source code before submitting a proposal
Have a deep understanding of the system’s structure and complexity
Have practical experience in:
Core system design
System integration
Microservices architecture
Already have an existing Core structure or codebase to ensure faster delivery
*Project Requirements:*
* Core architecture documentation including service boundaries and API contracts
* Setting up the authentication system and integrating it with 6amMart
* Creating the initial Core structure
* Preparing development, testing, and staging environments
* Providing a roadmap for extracting other modules
*Timeline & Proposal:*
A timeframe of 1 to 2 weeks is considered as a proposed estimate. If the project requires more time, please provide your maximum estimated timeline along with your proposed price.
For further review, you can refer to the documentation available on the official website (6ammart.app) or CodeCanyon.