A Resumed Media Job Could Still Download the Original Again
Stored extraction results avoided repeated model work, while a separate contents retry still fetched the file. The stage boundary explained both.
Reviewed by Dmytro Nasyrov on October 27, 2026.
After a failed attempt, a media pipeline can avoid repeating transcription and still download the original recording again.
We found both behaviors in our ingestion work. Treating them as one promise called resume would hide the cost that remained. Our platform extracted searchable speech and slide material from uploaded media. The expensive work included fetching the original file, decoding it and calling models. Each stage had a different durable result. An index rebuild should reuse those results when their version had not changed.
The checkpoint belongs to a stage, not a process
The video ingestion helper first checked whether slide detection had already completed and whether the sound had already been cut. When both were settled, it reconstructed its outcome from stored rows. That branch returned before obtaining the original file through its supplied loader.
A cache checked after downloading the source still pays for the download. A completed stage that is represented only in local memory disappears with the worker. Durable rows and the version's completion markers let a later invocation distinguish completed work from an interrupted process.
if slides_already_checked and sound_already_cut:
return outcome_from_stored_rows
source = obtain_original()
continue_only_unfinished_stages(source)This is a reduced explanation of the historical control flow, not a replacement implementation. The actual helper also preserves the established media classification and handles files without audio. It must not reinterpret a previously processed video merely because a later probe reports a different shape.
Reindexing is not retranscribing
The design separated a version's media extraction from later indexing. Reindexing the same version was intended to reuse the extracted rows rather than run ffmpeg, speech recognition and slide description again. This boundary matters when a reviewer corrects text: a corrected transcript should feed the search representation without spending another recognition call to recreate the old words.
It does not follow that every kind of rebuild is free. A new uploaded version has different source identity. A deliberately retried failed model stage still needs its own retry policy. Deleting a version must clean up durable artifacts so that reuse never points at a removed source.
| Operation | Evidence to inspect |
|---|---|
| Retry interrupted extraction | Which stage marker was committed before the interruption |
| Reindex the same version | Whether stored text and figures are reused |
| Correct an existing transcript | Whether the correction reaches indexing without a new recognition call |
| Build contents after failure | Whether this separate builder fetches the original on each attempt |
| Upload a new version | Whether old artifacts can legally be reused at all |
A different builder crossed the boundary again
The object-storage exercise recorded a limitation outside the main media pass. The contents builder for a recording or video did not retain its input between attempts. When its model timed out, the lecture was copied three times after the media pass had already completed.
For a 2 GB video, the notes describe the consequence as three additional 2 GB downloads. That is a conditional cost example, not a claim that the test measured those exact additional bytes for every large recording. The distinction belongs beside the successful reuse result.
The same run recorded seven contents calls timing out at 360 seconds. A single worker spent six minutes in each such call, leaving the next item waiting behind it. The answering model was not tested in that exercise, so these observations cannot be used as a measurement of the chat's general response quality or availability.
Do not let a retry counter stand in for an ownership model
A retry counter says how many attempts remain. It says nothing about which artifacts survive, which temporary file is owned by the current attempt or whether a later stage can reuse an earlier stage's output. Those were separate questions in this case. We would record the original version, the stage outcome and the resulting durable artifact together. A restart test should interrupt after the durable commit as well as before it. Otherwise it may prove that an empty worker starts cleanly while missing the point where completed expensive work becomes reusable.
A second control should count model calls and source reads independently. A transcript correction can legitimately produce zero new recognition calls while a contents retry still fetches the source. Combining those counters into one successful-recovery metric would make the remaining network cost disappear.
What the historical record establishes
The inspected implementation has an early return that reconstructs completed media work from rows before requesting the original. The dated integration notes also preserve the contents builder's repeated-copy limitation. We have not rerun the medical product's ingestion or failure-injection suite for this article. The boundary is specific: same-version indexing can consume existing extraction results, while another stage may still reacquire the original. Any operational promise about resume should name the stage and the resource it avoids consuming. In our record, a saved transcription call and a saved file download were different claims.
FAQ
Quick answers to common questions about custom software development, pricing, process and technology.
Type to filter questions and answers. Use Topic to narrow the list.
Showing all 14
No matches
Try a different keyword, change the topic or clear filters
-
How long have you been in business?
Pharos Production has been in business since 2013, with over 13 years of experience in custom software development. During this time, we have delivered over 110 applications for 200+ clients across 28 industries, including FinTech, healthcare, crypto and e-commerce. We are rated 5/5 on Clutch based on 107 verified reviews (2026).
-
What services do you provide?
Pharos Production provides six core service categories: AI Development (LLM applications, AI agents, machine learning and computer vision), Blockchain and Web3 (smart contracts, DeFi, tokenization on Ethereum, Solana, TON and other chains), FinTech Development (payment platforms, digital banking, KYC and AML integration), Software Development (mobile apps, web platforms, database design, UI/UX), Security and QA (code audits, penetration testing, smart contract audits, manual and automated testing) and Consulting (architecture design, MVP validation, startup consulting).
-
Where is Pharos Production located?
Pharos Production is headquartered in Las Vegas, Nevada, USA (5348 Vegas Dr, Las Vegas, NV 89108), with an engineering office in Kyiv, Ukraine (44-B Eugene Konovalets Str. Suite 201, Kyiv 01133). We work with clients worldwide and provide remote collaboration across all time zones. Visit our contact page for directions and scheduling options.
-
How big is your team?
Pharos Production has a team of 90+ engineers, including software developers, blockchain specialists, QA engineers, DevOps experts, UI/UX designers, project managers and solution architects. Our founder, Dr. Dmytro Nasyrov, holds a PhD in Artificial Intelligence and leads the technical direction of all projects.
-
What types of customers do you serve?
We serve a wide range of clients, from startups and product companies to mid-sized enterprises and large institutions. Our clients include crypto exchanges, FinTech providers (like Pleenk), healthcare organizations, sportsbook operators (like Pro Gambling), e-commerce platforms and SaaS companies. Pharos Production has worked with 200+ clients across 28 industries since 2013, adapting engagement models to match each client's stage, whether it is MVP validation for a startup or enterprise-scale development for an established business.
-
How is a custom software development company different from an agency?
A custom software development company like Pharos Production assigns one dedicated engineering team that owns your product across multiple release cycles, instead of handing it off once a contract ends. Agencies more often rotate staff between clients and optimize for fast delivery over long-term product ownership.
Pharos Production keeps the same team on your codebase through 2-week sprints, so there is no re-onboarding cost each time you request a new feature.
-
How much does custom software development cost?
Custom software development costs vary based on project scope and complexity. At Pharos Production, typical project ranges are: MVP development ($10,000-$25,000), suitable for startups validating a product idea; full-fledged production ($25,000-$50,000), for established businesses scaling a proven concept; and full-cycle development ($50,000-$80,000+), for complex enterprise-grade systems. These ranges include architecture design, development, QA testing and deployment. Hourly rates range from $50 to $99 depending on role and seniority. Final pricing depends on technology stack, number of integrations and engagement model (staff augmentation, dedicated team or project outsourcing).
-
How long does it take to develop a custom software application?
Development timelines depend on scope and complexity. At Pharos Production, a typical MVP takes 2-4 months, a production-ready application takes 4-8 months and a complex enterprise system can take 8-12+ months. We use an agile methodology with 2-week sprints, delivering working increments after each sprint. Every sprint includes a retrospective, progress report and planning session for the next iteration. This approach ensures transparency and allows businesses to launch faster by prioritizing high-impact features first. Get a timeline estimate for your project.
-
What industries does Pharos Production serve?
Pharos Production serves 28 industries: FinTech, MiCA Compliance, Banking, Insurance, Crypto, Healthcare, Fitness, E-Commerce, Food & Restaurant, On-Demand, Manufacturing, Automotive, Energy, Oil & Gas, Supply Chain, Construction, Real Estate, Gaming, Streaming, Media, Telecom, Education, Aviation, Travel, Logistics, Marketing, Agriculture and Recommender Systems. Our deepest expertise is in FinTech, blockchain and healthcare, where we have delivered compliance-ready platforms (HIPAA, PCI DSS, GDPR) and high-load systems handling thousands of concurrent users. For the latest industry insights, read our guides on FinTech trends in 2026 and the Web3 technology stack.
-
Why hire a software development company instead of building in-house?
Hiring a software development company offers faster time-to-market, lower upfront costs and access to specialized expertise without long-term employment commitments. According to Deloitte's 2024 Global Outsourcing Survey, 57% of companies outsource software development to access skills they cannot hire internally.
Factor In-house team Software development company Time to assemble 3-6 months (recruiting + onboarding) 1-2 weeks Upfront cost High (salaries, benefits, equipment) Lower (project-based pricing) Specialized expertise Limited to who you can hire locally Access to 90+ engineers across blockchain, AI, FinTech Scalability Slow (each new hire takes months) Fast (scale up or down per sprint) Long-term commitment Full-time employment contracts Flexible engagement models Risk High if key engineers leave Company ensures continuity and knowledge transfer For businesses that need blockchain, AI or high-load architecture expertise, outsourcing to a specialized firm like Pharos Production reduces risk and accelerates delivery.
-
What projects does Pharos Production not take on?
Pharos Production focuses on mid-to-large custom software projects with budgets starting at $10,000. We do not take on template-based websites, WordPress theme customization or short-term contracts under one month. We also do not provide non-technical staffing (marketing, sales or design-only roles). Our strongest fit is blockchain, FinTech and healthcare projects where security, compliance and high-load architecture are critical. For smaller projects or MVPs under $10,000, we recommend exploring freelance platforms or no-code tools as a more cost-effective starting point.
-
Why does Pharos Production use agile methodology?
We use agile with 2-week sprints because it reduces the risk of building features that miss the mark. Each sprint ends with a working demo, a retrospective and a plan for the next iteration.
This means clients see progress every 14 days and can adjust priorities based on real results, not assumptions. We chose this approach after years of experience showing that rigid, fixed-scope contracts lead to scope creep, missed deadlines and products that do not match market needs by launch day.
-
When should you NOT hire a custom software development company?
Custom development is not the right choice in every situation. You should not hire a custom software company if: your problem is fully solved by an existing SaaS product (e.g. Shopify for e-commerce, Salesforce for CRM); your budget is under $10,000 and timeline is under 4 weeks; you need a simple landing page or marketing website (WordPress or Webflow is faster and cheaper); or you are still validating the idea and have not spoken to potential users yet.
In these cases, off-the-shelf tools or no-code platforms offer better ROI. Custom development makes sense when you need unique workflows, regulatory compliance, high-load architecture or competitive differentiation that packaged software cannot provide.
-
What kind of projects has Pharos Production delivered?
Here are three anonymized examples from our recent delivery history:
FinTech startup - payment platform (MVP)
Scope: mobile app + backend API with bank-grade encryption. Team: 4 engineers, 1 QA. Timeline: 10 weeks. Budget: $38,000. Result: launched on schedule, processed $2M+ in transactions within the first quarter.Healthcare provider - patient portal (Full product)
Scope: HIPAA-aligned web platform with EHR integration, appointment scheduling and telemedicine. Team: 6 engineers, 1 DevOps, 2 QA. Timeline: 6 months. Budget: $120,000. Result: 15,000+ active patients, zero compliance violations in two annual audits.Crypto exchange - trading engine (Complex)
Scope: high-load matching engine handling 50,000+ orders per second, multi-chain wallet infrastructure on Ethereum and Solana. Team: 8 engineers, 2 QA, 1 security auditor. Timeline: 11 months. Budget: $340,000. Result: 99.97% uptime, passed three independent security audits.See more projects: NoMoreBets, Pulse, Sagas, Gambit Stream and Pleenk. For the full portfolio, visit our case studies. Learn more about the technology behind these projects in our guide to stablecoins and crypto infrastructure.
Dmytro Ihnatov is the Lead Backend Developer at Pharos Production. He documents backend architecture and research experiments from the team's work on a professional learning platform for aesthetic medicine.
