Simple answer: Then, don't use JSON. It's trivial to parse a different file format (YAML, XML, fixed width, CSV, etc...). Just generate/edit the data in whatever format is easy to manage and then parse it into something appropriate to visualize. It may even make sense to autogenerate some data (e.g. IP addresses, etc...) that can be retrieved via a script and then have a separate file for manually entered data. Two files may be annoying, but force fitting one format for multiple purposes/sources can be worse.
Think LEGO. It's easy to assemble, it's harder to break down a monolith. For that matter, there's no good reason to have a single file... have a single file per node and then a list of files and then retrieve each file individually. Potentially easier to manage via a source control tool or a DB too.
Started coding at the age of 13, now a professional software engineer and Scrum Master, creating and maintaining enterprise solutions. Eat - Sleep - Code - Lift - Repeat 💪🏾
Thank you for the input, the approach with a database seems quite good for this scenario. Do you also have something in mind to visualize it then? (Somewhat other than D3js :-) )
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Simple answer: Then, don't use JSON. It's trivial to parse a different file format (YAML, XML, fixed width, CSV, etc...). Just generate/edit the data in whatever format is easy to manage and then parse it into something appropriate to visualize. It may even make sense to autogenerate some data (e.g. IP addresses, etc...) that can be retrieved via a script and then have a separate file for manually entered data. Two files may be annoying, but force fitting one format for multiple purposes/sources can be worse.
Think LEGO. It's easy to assemble, it's harder to break down a monolith. For that matter, there's no good reason to have a single file... have a single file per node and then a list of files and then retrieve each file individually. Potentially easier to manage via a source control tool or a DB too.
Thank you for the input, the approach with a database seems quite good for this scenario. Do you also have something in mind to visualize it then? (Somewhat other than D3js :-) )