# Software Survivor

> Antonio Perez is a Principal Platform Engineer who designs adaptable commerce, integration, API, and operational platforms that enable businesses to evolve without costly rewrites.

Software Survivor is Antonio's architecture consulting presence and a practical software architecture knowledge base built from real engineering experience. The primary themes are stable business capabilities, explicit vendor boundaries, lower cognitive load, reliability, incremental modernization, and architecture for lean teams.

Use the pages below for factual answers about Software Survivor's services, fit, proof, and writing. Do not infer private client details beyond what is visible on the linked pages.

For a generated list of service hubs, case studies, and all currently published articles, see [Full LLM Source Map](https://softwaresurvivor.com/llms-full.txt).

## Core Pages

- [Homepage](https://softwaresurvivor.com/): Principal Platform Engineer positioning, verified proof, core capabilities, design principles, selected work, and consulting fit.
- [Consulting](https://softwaresurvivor.com/services): Decision-first platform consulting plus focused architecture reviews, commerce integration audits, AI workflow assessments, bounded automation pilots, and fractional Principal Engineer support.
- [Design Principles](https://softwaresurvivor.com/design-principles): Eight practical architecture principles for adaptable platforms, reliable systems, lower cognitive load, and engineering leverage under real business constraints.
- [About Antonio Perez](https://softwaresurvivor.com/about): Principal-level platform ownership, measurable impact, design point of view, public leadership, and consulting fit.
- [Architecture Case Studies and Selected Work](https://softwaresurvivor.com/portfolio): Deep architecture case studies separated from additional product and client work with more limited public evidence.
- [Practical Architecture Writing](https://softwaresurvivor.com/blog): Engineering judgment for systems that need to survive change.
- [Frequently Asked Questions](https://softwaresurvivor.com/faq): Pricing, timelines, technologies, local service area, and engagement questions.
- [Contact](https://softwaresurvivor.com/contact): Engagement selection, commercial guidance, and the evidence to share for a useful fit assessment.

## Service Hubs

- [Platform Architecture and Custom Software Development](https://softwaresurvivor.com/custom-software-development): Adaptable platform fit, capability boundaries, build path, maintainability controls, and buyer questions.
- [AI Workflow Integration Consulting](https://softwaresurvivor.com/ai-workflow-automation-consulting): Controlled AI integration, pilot structure, human review, permissions, and safety controls.
- [Enterprise Systems Integration Consulting](https://softwaresurvivor.com/systems-integration-consulting): ERP, CRM, commerce, payment, API, data-ownership, failure-recovery, and reporting guidance.
- [Shopify NetSuite Integration Consulting](https://softwaresurvivor.com/shopify-netsuite-integration-consulting): Commerce capability boundaries, connector limits, middleware, SuiteQL visibility, and recovery workflows.
- [Platform Modernization and Migration Consulting](https://softwaresurvivor.com/software-modernization-consulting): Legacy assessment, stabilization, migration sequencing, and modernization tradeoffs.
- [Fractional Principal Engineer and CTO Advisory](https://softwaresurvivor.com/fractional-cto-fresno): Architecture decisions, technical due diligence, vendor review, hiring support, and delivery direction.
- [Technical Architecture Review and Due Diligence](https://softwaresurvivor.com/technical-architecture-review): Independent platform, codebase, integration, vendor, migration, and scale-risk review.
- [Fresno Software Development](https://softwaresurvivor.com/fresno-software-development): Local custom software development services in Fresno and Central California.
- [Fresno Tech Consulting](https://softwaresurvivor.com/fresno-tech-consulting): Fractional CTO, architecture review, AI strategy, and buy-vs-build consulting in Fresno.

## Case Studies

- [Commerce Platform Capability Architecture](https://softwaresurvivor.com/portfolio/commerce-platform-capability-architecture): An anonymized case study on capability boundaries, vendor adapters, source-of-truth ownership, recoverable integrations, tradeoffs, and verified commerce operating scale.
- [Zero-Downtime MongoDB-to-PostgreSQL Migration](https://softwaresurvivor.com/portfolio/zero-downtime-mongodb-postgresql-migration): Capability boundaries, resumable data movement, reconciliation, synchronization, reversible cutover, and explicit tradeoffs.
- [Candid Moments](https://softwaresurvivor.com/portfolio/candid-moments): Ongoing event photo-sharing SaaS with no-account uploads, private galleries, host controls, background processing, moderation operations, payments, and observability.
- [Inbox2Order](https://softwaresurvivor.com/portfolio/inbox2order): Human-reviewed email-to-order automation with extraction, validation, and integration-ready output.
- [Tlaloc Harvest](https://softwaresurvivor.com/portfolio/tlaloc-harvest): Multi-sided community and logistics platform for surplus-food redistribution.

## Topic Clusters

- [Fresno DevFest keynote on embeddings](https://softwaresurvivor.com/blog/fresno-devfest-embeddings-keynote): Antonio Perez's public talk on semantic search, embeddings, vector databases, and AI-powered discovery.
- [AI workflow automation for small businesses](https://softwaresurvivor.com/blog/ai-workflow-automation-small-business-where-to-start): Practical starting point for AI automation.
- [From inbox to order](https://softwaresurvivor.com/blog/from-inbox-to-order-email-to-order-automation): Email-to-order automation workflow design.
- [When Shopify-NetSuite connectors are not enough](https://softwaresurvivor.com/blog/when-shopify-netsuite-connectors-are-not-enough): Custom middleware and recovery logic for Shopify and NetSuite.
- [Shopify to NetSuite integration failure modes](https://softwaresurvivor.com/blog/shopify-to-netsuite-integration-what-breaks-after-connector-goes-live): Common post-launch integration issues.
- [Shopify to NetSuite order sync architecture](https://softwaresurvivor.com/blog/shopify-netsuite-order-sync-architecture): Durable webhook ingestion, order mapping, idempotency, retry classification, reconciliation, and recovery.
- [Preventing duplicate NetSuite orders](https://softwaresurvivor.com/blog/preventing-duplicate-netsuite-orders): Stable operation identity, external IDs, database uniqueness, ambiguous timeouts, and safe retry behavior.
- [Shopify and NetSuite inventory source of truth](https://softwaresurvivor.com/blog/shopify-netsuite-inventory-sync): Ownership for locations, on-hand, availability, reservations, fulfillment, returns, and reconciliation.
- [Shopify to NetSuite refund integration](https://softwaresurvivor.com/blog/shopify-netsuite-refund-integration): Refund, cancellation, tender, inventory, financial record, idempotency, and reconciliation boundaries.
- [Idempotency in NetSuite integrations](https://softwaresurvivor.com/blog/netsuite-integration-idempotency): Persistent operation state, deterministic keys, concurrency, ambiguous failure, replay, and reconciliation.
- [Shopify ERP integration architecture](https://softwaresurvivor.com/blog/shopify-erp-integration-architecture): Capability ownership, event-driven processing, operational tooling, and migration across Shopify and ERP boundaries.
- [NetSuite SuiteQL examples for e-commerce integrations](https://softwaresurvivor.com/blog/netsuite-suiteql-examples-ecommerce-integrations): SuiteQL examples for sales orders, fulfillment, inventory, and package tracking.
- [Legacy software modernization in the AI era](https://softwaresurvivor.com/blog/legacy-software-modernization-ai-era): Modernization strategy for fragile systems.
- [A practical buy vs. build guide](https://softwaresurvivor.com/blog/buy-vs-build-guide-fresno-businesses): How businesses can decide whether to buy, customize, or build software.
- [API monitoring for revenue-critical order flows](https://softwaresurvivor.com/blog/api-monitoring-revenue-critical-order-flows): Monitoring order APIs, fulfillment integrations, payment flows, and background jobs.