Stock Photo Platform Development

Stock Photo Platform Development

We develop stock photo services—from MVP to full-fledged platforms with visual content search and flexible licensing. Technically, this intersects three domains: managing large binary objects, searching metadata and visual content, and licensing transactions. Each is nontrivial on its own; together, they demand a well-architected system from the start. If you're considering launching a photo bank, it's critical to set up the right storage, search, and monetization solutions from the beginning—rebuilding later is costly. Our engineers help design a system that handles millions of files and thousands of transactions per day.

How File Upload and Storage Work

Minimum requirements for typical stock uploads: JPEG/TIFF/PNG, at least 4 MP, up to 200 MB. Video: MP4/MOV up to 4K, up to 2 GB. This means direct upload to the application server is out of the question. Instead, we use multipart upload via S3:

Client → presigned URL (S3) → upload directly to S3
S3 Event → SQS → Worker: generate previews, validate, extract metadata
Worker → DB: write asset with status=processing → status=ready

Storage: AWS S3 or any S3-compatible (MinIO for self-hosted). Bucket structure:

• originals/ — source files, private access, only via signed URLs
• previews/ — watermarked, public CDN
• thumbnails/ — multiple sizes (400px, 800px, 1600px), generated on upload

For preview generation we use libvips, which is 4–8x faster than ImageMagick. Watermarks are applied during preview generation, not on delivery—otherwise rebranding would require regeneration. This approach saves up to 60% on infrastructure by using efficient CDN caching.

Why Licensing Is Key

Licenses are the core business logic of a stock platform. Minimal set of types:

File delivery after payment is a one-time signed URL with a TTL of 15–60 minutes, not a direct S3 link. Each delivery is logged with user_id, asset_id, timestamp, and IP.

How Search and Metadata Work

Media file metadata lives in two places: EXIF/IPTC inside the file and in the database. On upload, we parse IPTC tags via ExifTool, save them to the DB, and allow the author to add more manually. Metadata structure:

assets (id, uuid, author_id, title, description, status, license_type, uploaded_at)
asset_tags (asset_id, tag_id)
asset_categories (asset_id, category_id)
asset_metadata (asset_id, key, value)  -- EXIF, IPTC, custom fields

For full-text search we use Elasticsearch with a Russian analyzer (recommendation in Elasticsearch documentation). We index: title, description, tags, categories, author name, IPTC keywords. Boost by field: tags > title > description.

Visual search (similar image search): we generate a perceptual hash (pHash) on upload. Similarity search uses hamming distance on hashes. For advanced implementation—CLIP embeddings via OpenAI API or a local model, stored in a vector DB (pgvector or Qdrant). Color search extracts dominant colors via k-means clustering (Pillow / ColorThief), stores HEX palette, indexes in Elasticsearch as a keyword field with boost.

Subscription and Credit System

Two monetization models often run in parallel. Subscription: X downloads per month, certain resolutions, rollover or reset. Implemented via Stripe Subscriptions + webhooks. On download, we check subscription.downloads_remaining and decrement atomically (Redis DECR). Credits: user buys a pack of credits, spends on download. Different files cost different credits. Transactions in a separate table with balance—never store balance as a mutable field without history.

Author Uploader

The author dashboard is a separate part of the system. Key requirements: batch upload of 50–200 files with progress bars, bulk metadata editing, moderation pipeline (uploaded → under review → approved/rejected), author statistics. For batch upload we use <input multiple> + chunked upload via tus protocol (resumable uploads). Client library—tus-js-client. Server—tusd or custom implementation on Laravel.

SEO and Indexing

Photo pages generate the bulk of SEO traffic. Each asset page: URL /photos/{category}/{slug}-{id} (readable, no hash), Title {title} — stock photo #{id} (unique), Structured data ImageObject Schema.org with contentUrl, author, license, keywords. Related photos: internal links by tags and categories. For catalogs with millions of files, XML sitemap splits into index + separate files by category, updated incrementally.

Performance

Catalog pages are cached at the CDN level (Cloudflare) with Cache-Control: stale-while-revalidate. Previews are served via CDN with immutable cache (filename includes content hash). Search uses Elasticsearch. Lazy loading of previews: Intersection Observer API, placeholder—dominant color from metadata.

What's Included in the Work

We provide a full set of deliverables:

• Architecture documentation (ERD, component diagram, use cases)
• Source code with CI/CD on GitHub Actions + Docker
• Access to infrastructure (AWS, Cloudflare, Stripe)
• Team training (2–3 sessions on operation)
• One month of post-release support (bug fixes, consultations)

Timeline

• MVP (upload, tag search, RF license purchase, Stripe): 8–12 weeks
• Full-featured stock (subscriptions, visual search, author dashboard with moderation, SEO layer): 20–30 weeks
• Integration of CLIP search or duplicate detector adds 2–4 weeks to any stage

The complexity of a photo bank is often underestimated, mistaken for a "catalog with files." The difference becomes evident at the licensing and storage scaling stages. Contact us to evaluate your project—we will help you avoid common pitfalls and accelerate time to market.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.