Array Driver

INFO

Our array driver is one interpretation of how to build an interface over an in-memory array.

If you don't like the way we organized this, please skip to the custom driver section and implement our driver interface for your own array structure. This can serve moreso as an example of a working custom driver as well.

Iridium's array driver allows you to create forms and table that source their data from an in-memory array.

Getting started

FAQ

• Should I use an array or a GORM driver?
  • We recommend using GORM everytime you can. You can create an in-memory sqllite database if you want a middle ground. Databases manage joins, migrations, persistance, locking, etc. easier than in-memory arrays. If you don't have a solid reason to use an array, we recommend a database everytime.
• Why build an array driver then?
  • For us, we had a set of data that needed to be scanned extremely frequently in our backend and GO only met our performance requirements when this data was stored inside an in-memory array as oppossed to a database. We still needed an interface over that data, so we need some way to read from it into an Iridium resource.