Monday, April 23, 2007

New Storage engines in 5.1

SolidDB
  • Transactional, ACID compliant Engine

  • Optimistic and Pessimistic Concurrency Control (Innodb uses Pessimistic)

  • Configurable Durability

  • Support transaction isolation on a per table basis



  • PBXT
  • Transactional not fully ACID compliant

  • Recovers from a crash faster then myISAM

  • Designed for Heavy INSERT usage


  • Memcache Engine
  • Tables with Key Pairs

  • Insert into memcache through mysql and use the memcache client to select against it. Incredibly fast on insert, very nasty bug in memcache client C-API that more then 100 connections, lockups occure.

  • Multiple mysql servers can share the same data

  • Monitoring memcache servers with table data in mysql


  • AWS Engine
  • Store data in S3 - cheap way to store data not really going to use

  • Alpha


  • HTTP Engine
  • Generic web service Engine

  • SELECT - GET INSERT - HTTP PUT UPDATE-DELETE/PUT DELETE; all mapped to generic web service arch.

  • Read from a Google spreadsheet then read in the database
  • 2 comments:

    RIck said...

    Hello,

    ..."very nasty bug in memcache client C-API that more then 100 connections, lockups occure."

    What exactly is the bug, and is it known?

    Dathan Pattishall said...

    According to Brian A. it is known and will be fixed by next week.