Softwr

E-Commerce · head to head

BigCommerce vs Memcached

BigCommerce logo

BigCommerce

E-Commerce

Hosted e-commerce platform that charges no transaction fee and no surcharge for third party gateways

From
$29.95/month
Free plan
No
M

Memcached

Databases

Distributed memory object caching system

From
Free
Free plan
Yes

The short version

  • Memcached is free; BigCommerce starts at $29.95/mo.
  • Only BigCommerce lists no platform transaction fee; only Memcached lists in-memory key-value cache.
  • Where Memcached falls short: no persistence at all: restart a node and its cache is gone, which every design must assume.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which BigCommerce and Memcached actually diverge.

Attributes where BigCommerce and Memcached differ
AttributeBigCommerceMemcached
Starting price$29.95/monthFree
Pricing modelSubscriptionOpen source, no licence fee; managed cloud billed separately
Free tierNoYes
PlatformsWebLinux, macOS, Windows, Self-hosted
CategoryE-CommerceDatabases

Not yet recorded: founded for Memcached.

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in BigCommerce

  • No platform transaction fee
  • Stencil theme framework
  • Multi-storefront
  • Faceted search
  • B2B capabilities
  • Headless support
  • Built-in tax integrations
  • Multi-currency

Only in Memcached

  • In-memory key-value cache
  • Multithreaded
  • Client-side sharding
  • Predictable memory use

What people use each for

The jobs each tool is most often brought in to do.

BigCommerce

  • A merchant whose volume makes a percentage transaction fee the largest line in the platform decisionnot Memcached
  • A retailer needing several branded storefronts sharing one catalogue and one back officenot Memcached
  • A B2B seller who needs company accounts and customer-specific price lists without custom developmentnot Memcached
  • A team going headless who wants a managed commerce back end rather than a self-hosted onenot Memcached

Memcached

  • Caching expensive database query results to cut loadnot BigCommerce
  • Session storage where losing sessions on restart is acceptablenot BigCommerce
  • Fronting an API whose responses are costly and change slowlynot BigCommerce

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

BigCommerce

  • Plans are gated on annual online sales, so a strong year pushes you into a higher tier and a higher subscription even though your traffic, catalogue and resource usage are unchanged
  • There is a documented ceiling on the number of variants a single product can have, which breaks configurable, made-to-measure and heavily optioned catalogues and forces awkward workarounds such as splitting one product into several listings
  • The application marketplace is much smaller than the largest competitor's, so a specific integration or niche feature is more often a custom build, and custom builds are the line item that quietly exceeds the platform cost
  • Theme customisation past the visual settings means Stencil, Handlebars templates and a local command line workflow, so changes that look small to a marketing team still require a developer and a deployment
  • Migrating out moves products and inventory reasonably well and moves the things that matter badly, since customer passwords cannot be exported in usable form, order history rarely transfers intact, and reviews and URL structure have to be rebuilt with a redirect map you must produce yourself or lose the search traffic

Memcached

  • No persistence at all: restart a node and its cache is gone, which every design must assume
  • No replication or failover, so losing a node loses that share of the cache
  • Only simple key-value, with none of the lists, sorted sets or streams Redis offers
  • Values are capped at 1MB by default, which surprises teams caching large documents

Pricing, plan by plan

BigCommerce

$29.95/month
  • Standard$29.95/mo
    • Unlimited products
    • 2 staff accounts
    • Basic reports
  • Plus$79.95/mo
    • All Standard features
    • Up to 5 staff accounts
    • Advanced reports

Memcached

Free
  • MemcachedFree
    • Full functionality
    • Self-hosted
    • No usage limits

Which should you pick?

Choose BigCommerce if

  • You need no platform transaction fee.
  • You also want stencil theme framework.

Choose Memcached if

  • You need in-memory key-value cache.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Self-hosted.
  • You also want multithreaded.

Questions people ask

Is BigCommerce or Memcached better?
Neither clearly leads. BigCommerce starts at $29.95/month and Memcached at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BigCommerce or Memcached?
Memcached has a free tier; the other does not. Paid plans start at $29.95/month for BigCommerce and Free for Memcached.
Does BigCommerce or Memcached run on more platforms?
BigCommerce runs on Web. Memcached runs on Linux, macOS, Windows, Self-hosted.
Can I use Memcached for free?
Yes. Memcached has a free tier, so you can try it without paying. BigCommerce starts at $29.95/month.
What is BigCommerce best used for?
BigCommerce is most often used for a merchant whose volume makes a percentage transaction fee the largest line in the platform decision, a retailer needing several branded storefronts sharing one catalogue and one back office, a b2b seller who needs company accounts and customer-specific price lists without custom development, a team going headless who wants a managed commerce back end rather than a self-hosted one. Of those, a merchant whose volume makes a percentage transaction fee the largest line in the platform decision and a retailer needing several branded storefronts sharing one catalogue and one back office are not what Memcached is typically brought in for.
What can BigCommerce do that Memcached cannot?
BigCommerce covers No platform transaction fee, Stencil theme framework, Multi-storefront, Faceted search. Memcached covers In-memory key-value cache, Multithreaded, Client-side sharding, Predictable memory use.

Answered from the vendors’ own pages

BigCommerce: Does BigCommerce charge transaction fees?

No, and it does not surcharge third party payment gateways either. Revenue affects the price through plan sales thresholds instead.

Memcached: Is Memcached free?

Yes, open source with no licence fee.

BigCommerce: What happens when I exceed my plan's sales threshold?

You move to the next plan tier. Model this at your projected growth rate, because the increase is driven by revenue rather than by usage.

Memcached: Memcached or Redis?

Memcached is a pure cache: simpler, multithreaded and very predictable. Redis adds persistence, replication and rich data structures, which is why it is the default choice unless you specifically want a cache and nothing more.

BigCommerce: Is the app ecosystem large enough?

It covers the common integrations. For anything niche, assume a development project rather than an install, and price that in before comparing subscriptions.

Memcached: Does Memcached persist data?

No. Everything is in memory and lost on restart, by design.

BigCommerce: How hard is it to leave?

Products export cleanly. Customer passwords, order history, reviews and SEO URLs do not. Build the redirect map before you cut over, not after traffic drops.

Share

Related pages

Other head to heads