Hello Denis, I mean a database that hosts the information about sites (e.g., hotels) and devices located the sites (e.g., hardware, software, configuration, labels, geolocation), there can be 1000s of sites with each site having many devices, totaling 100s of 1000s entries. The data is not volatile and we don't have to keep track of the changes in the same database.
thanks Clay On Wed, Jan 8, 2020 at 3:12 PM Denis Magda <[email protected]> wrote: > Hi Clay, > > Could you please elaborate on the technical requirements of this usage > scenario? > > - > Denis > > > On Wed, Jan 8, 2020 at 8:30 AM Clay Teahouse <[email protected]> > wrote: > >> Hello All, >> >> What are the pros and cons of using ignite as an asset and configuration >> database? >> >> thanks, >> Clay >> >
