Ignite for Configuration Database

classic Classic list List threaded Threaded
5 messages Options
Clay Teahouse Clay Teahouse
Reply | Threaded
Open this post in threaded view
|

Ignite for Configuration Database

Hello All,

What are the pros and cons of using ignite as an asset and configuration database?

thanks,
Clay
dmagda dmagda
Reply | Threaded
Open this post in threaded view
|

Re: Ignite for Configuration Database

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 <[hidden email]> wrote:
Hello All,

What are the pros and cons of using ignite as an asset and configuration database?

thanks,
Clay
Clay Teahouse Clay Teahouse
Reply | Threaded
Open this post in threaded view
|

Re: Ignite for Configuration Database

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 <[hidden email]> 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 <[hidden email]> wrote:
Hello All,

What are the pros and cons of using ignite as an asset and configuration database?

thanks,
Clay
dmagda dmagda
Reply | Threaded
Open this post in threaded view
|

Re: Ignite for Configuration Database

Clay, thanks for clarifying. That's Ignite's use case. I'm aware of some companies that use Ignite similarly but cannot disclose the names. 

How are you planning to query data - SQL, compute tasks any other APIs? 

-
Denis


On Wed, Jan 8, 2020 at 4:29 PM Clay Teahouse <[hidden email]> wrote:
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 <[hidden email]> 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 <[hidden email]> wrote:
Hello All,

What are the pros and cons of using ignite as an asset and configuration database?

thanks,
Clay
Clay Teahouse Clay Teahouse
Reply | Threaded
Open this post in threaded view
|

Re: Ignite for Configuration Database

Thanks Denis for the feedback.

Currently the plan is to use either mostly rest API and in some cases SQL.

On Wed, Jan 8, 2020 at 6:39 PM Denis Magda <[hidden email]> wrote:
Clay, thanks for clarifying. That's Ignite's use case. I'm aware of some companies that use Ignite similarly but cannot disclose the names. 

How are you planning to query data - SQL, compute tasks any other APIs? 

-
Denis


On Wed, Jan 8, 2020 at 4:29 PM Clay Teahouse <[hidden email]> wrote:
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 <[hidden email]> 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 <[hidden email]> wrote:
Hello All,

What are the pros and cons of using ignite as an asset and configuration database?

thanks,
Clay