I will diagnose and optimize your slow API or sql database
Senior Software Architect AI Data APIs and SaaS
About this Gig
If an API is timing out, a SQL workload is slow, or a production workflow cannot support expected volume, I will replace guesswork with a measured investigation. I trace the agreed workload across the request and database paths, document evidence, and implement contained changes when the selected package includes remediation.
Basic - Diagnose: one workload, telemetry, query and request-path review, root-cause findings, and prioritized recommendations. No implementation.
Standard - Optimize: diagnosis plus one contained optimization in a buyer-provided safe environment, tests, before-and-after validation, and change notes.
Premium - Validate: a broader defined workload, multiple contained fixes, repeatable load-test validation, regression tests, documentation, and a recorded walkthrough.
No percentage improvement or platform-wide outcome is guaranteed before inspection. Hosting, third-party fees, new infrastructure, broad rewrites, extensive data cleanup, unrelated workloads, and production deployment unless agreed in writing are excluded. Revisions apply to the agreed workload, not additional endpoints or systems.
Database type:
Centralized database
•
Relational database
Platform:
PostgreSQL
•
SQL Server
Expertise:
Design
•
SQL
•
Performance
•
Query optimization
FAQ
Can you guarantee a specific speed improvement?
No. I establish a baseline, investigate the system, and report measurable results for the agreed workload. The outcome depends on the root cause, access, infrastructure, data, and constraints.
Do you need production access?
Not necessarily. Read-only evidence and a representative non-production environment are preferred. Never send production credentials or sensitive data in chat.
What counts as one workload?
One defined request path, query family, or business operation with agreed inputs, volume, and acceptance criteria. Unrelated endpoints are a separate scope.
Can you work with SQL Server and PostgreSQL?
Yes. The engagement can include query plans, indexes, data-access behavior, API request paths, and application-layer bottlenecks for the agreed scope.
