You will get your Node.js, Python, or Java service rewritten in idiomatic Go
Project details
You will get your Node.js, Python, or Java service rewritten in idiomatic Go: faster, leaner, and far easier to operate at scale. I am a Staff Backend Engineer with 20+ years of distributed systems experience and a deep working knowledge of Go, Node, Python, and the JVM, so I understand both sides of the migration.
This is the right fit if your service is slow, expensive to host, or hard to maintain in its current language, you are consolidating your backend stack around Go, or your team needs a clean reference implementation to follow when migrating the rest of the system.
What you receive:
• Clean idiomatic Go rewrite of your service
• Same API contract preserved (unless we improve it intentionally)
• Unit tests + parity test suite verifying behavior matches the original
• Side-by-side performance benchmarks so you can quantify the gains
• Multi-stage Dockerfile, structured logging, error handling
• Documented cutover/rollback plan for zero-downtime migration
• 45-minute handover call covering code, ops, and roadmap
I communicate clearly in English, Portuguese, and Spanish.
This is the right fit if your service is slow, expensive to host, or hard to maintain in its current language, you are consolidating your backend stack around Go, or your team needs a clean reference implementation to follow when migrating the rest of the system.
What you receive:
• Clean idiomatic Go rewrite of your service
• Same API contract preserved (unless we improve it intentionally)
• Unit tests + parity test suite verifying behavior matches the original
• Side-by-side performance benchmarks so you can quantify the gains
• Multi-stage Dockerfile, structured logging, error handling
• Documented cutover/rollback plan for zero-downtime migration
• 45-minute handover call covering code, ops, and roadmap
I communicate clearly in English, Portuguese, and Spanish.
Programming Languages
Python, Java, GoCoding Expertise
Performance Optimization, SecurityWhat's included
| Service Tiers |
Starter
$399
|
Standard
$899
|
Advanced
$1,999
|
|---|---|---|---|
| Delivery Time | 7 days | 14 days | 21 days |
Number of Revisions | 1 | 2 | 3 |
Number of Pages | 2 | 5 | 10 |
Design Customization | - | - | - |
Content Upload | - | - | - |
Responsive Design | - | - | - |
Source Code |
Optional add-ons
You can add these on the next page.
Fast Delivery
+$200 - $500
Additional Revision
+$150
Extra service or module migrated
(+ 5 Days)
+$400
Performance benchmark report
(+ 2 Days)
+$200
Knowledge-transfer session (90 min)
(+ 1 Day)
+$200Frequently asked questions
About Alessander
Staff Backend Engineer - Go, Microservices, Distributed Systems
Florianopolis, Brazil - 12:21 am local time
I operate through a US-based LLC, making B2B engagement seamless for North American and European organizations.
What I architect:
- Event-Driven Microservices and Serverless (Golang, AWS Lambda, GCP)
- Internal Developer Platforms (IDP) that cut provisioning from days to minutes
- Observability stacks (Datadog, SOC2) that slash MTTR by 40%
- Cloud Cost Optimization - 30% API latency gains on high-volume ERP systems
- Legacy Modernization - monolith-to-microservices with zero downtime
Core stack: Golang, Java, Python, AWS, GCP, Terraform, Kubernetes, Kafka, PostgreSQL, Redis, Datadog
Google Professional Cloud Architect certification in progress. Postgraduate specializations in Software Architecture and Database Administration.
Open to Staff / Principal / Tech Lead engagements - remote, contract or full-time.
Steps for completing your project
After purchasing the project, send requirements so Alessander can start the project.
Delivery time starts when Alessander receives requirements from you.
Alessander works on your project following the steps below.
Revisions may occur after the delivery date.
Source service analysis
I map your existing service: endpoints, data flows, dependencies, third-party libraries, gotchas, and tests. I document the behavior we need to preserve and any improvements we'll add along the way.
Idiomatic Go rewrite
I rewrite the service in clean idiomatic Go: handlers, services, repositories, structured logging, validation, error handling. I keep the same API contract unless we agreed to improve it.