WordPress Microservices Migration
Budget: $250 – $750 USD
I’m ready to break our monolithic WordPress-based marketplace into a true microservices platform. The goal is to keep the existing features intact while giving the product space to scale and deploy independently on AWS.
Here is the core of what I need done:
• Design an overall microservices architecture that lifts the WordPress logic out into independently deployable services, fronted by a single GraphQL API.
• Implement those services on AWS using Lambda for compute, Amazon S3 for static assets and media, and Amazon RDS for the relational data that still makes sense to keep together.
• Provide a clean GraphQL schema that mirrors everything customers and admins can do today—account actions, catalog queries, checkout, and payments—so the front-end (and any future mobile apps) can talk to a single gateway.
• Supply infrastructure-as-code (CloudFormation or Terraform) so environment spin-up is reproducible, plus CI/CD scripts for zero-downtime rollouts.
• Migrate the current live data and ensure parity tests prove nothing was lost or broken.
Hand-off is complete when code, documentation, and deployment scripts are in my Git repo and I can launch a staging copy from scratch.
If you’ve split WordPress or similar PHP apps before and are comfortable wiring Lambda, S3, and RDS behind a GraphQL layer, let’s talk.
To Apply
Please include:
Examples of similar microservices projects
Recommended architecture for this project
Tech stack suggestion (Laravel / Node / etc.)
Estimated timeline
Any suggestions to improve scalability
Here is the core of what I need done:
• Design an overall microservices architecture that lifts the WordPress logic out into independently deployable services, fronted by a single GraphQL API.
• Implement those services on AWS using Lambda for compute, Amazon S3 for static assets and media, and Amazon RDS for the relational data that still makes sense to keep together.
• Provide a clean GraphQL schema that mirrors everything customers and admins can do today—account actions, catalog queries, checkout, and payments—so the front-end (and any future mobile apps) can talk to a single gateway.
• Supply infrastructure-as-code (CloudFormation or Terraform) so environment spin-up is reproducible, plus CI/CD scripts for zero-downtime rollouts.
• Migrate the current live data and ensure parity tests prove nothing was lost or broken.
Hand-off is complete when code, documentation, and deployment scripts are in my Git repo and I can launch a staging copy from scratch.
If you’ve split WordPress or similar PHP apps before and are comfortable wiring Lambda, S3, and RDS behind a GraphQL layer, let’s talk.
To Apply
Please include:
Examples of similar microservices projects
Recommended architecture for this project
Tech stack suggestion (Laravel / Node / etc.)
Estimated timeline
Any suggestions to improve scalability
Related categories:
PHP
WordPress
MySQL
Amazon Web Services
Aws Lambda
Amazon S3
GraphQL
Microservices
Terraform
CI/CD