this post was submitted on 29 Aug 2024
263 points (98.5% liked)

Technology

59192 readers
2433 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 2 months ago* (last edited 2 months ago) (1 children)

Generally the elastic or usage/volumetric type billing structures are used on SaaS/cloud products, not on-prem.

Although it's entirely possible that elasticsearch, and other vendors in the space use that pricing model for their on-prem customers.

Regardless, that's even more of a reason why it would be very difficult to give a quote without being first having a presales meeting with a solution architect or knowledgeable rep.

[–] [email protected] 1 points 2 months ago (1 children)

How about instead of elastic customers moved to Redis or Postgres ?

Does the pricing/licensing suddenly change ? Hmm ?

[–] [email protected] 2 points 2 months ago

Elasticsearch provides a different feature set than Redis or Postgres. I've seen apps that use all 3... but anyway.

It is a little weird to charge per-seat for a search database that is usually integrated into a product, and not used directly by employees. Usually that kind of pricing model is reserved for developer tools like Splunk (notoriously overpriced), or game engines like Unity/Unreal Engine.