Skip to main content

Managing configurations with object graphs

***
This post is basically a pitch I send to folks whom I think will be interested in a modern approach to configuration management. I am posting it here so I can refer people to it without sending them a long email.
***

One of the features of the Solvent (formerly HiveMind) platform is a smart object technology that solves the problem of dealing with hierarchical configuration information often represented in formats Like YAML,JSON, Java Properties,XML...etc

The smart object technology allows developers/users to directly construct object graphs of any complexity. Once you have the actual object graph you can reverse the process back to representation in any one of the formats mentioned above.
 

I have setup a demo instance for trying it out @ http://demo.crudzilla.com:7000

Login with login info I sent you.

Be nice, you have full system access :)

To see an example representing the AWS IP list (https://ip-ranges.amazonaws.com/ip-ranges.json):

Navigate to: /com/crudzilla/betaApp/web/aws/index.ins

This is what a smart object looks like, the cool thing is that you can combine smart objects to compose any complex object graph and you use the file system to organize the smart objects.
Once you have your object graph you can serialize it to any suitable format as the included examples show:


http://demo.crudzilla.com:7000/betaApp/crud-appserver/aws/yaml/
http://demo.crudzilla.com:7000/betaApp/crud-appserver/aws/json/
http://demo.crudzilla.com:7000/betaApp/crud-appserver/aws/properties/
http://demo.crudzilla.com:7000/betaApp/crud-appserver/aws/xml/


This approach is quite powerful, beyond its use for configuration, it can be used to allow non-technical users to handle certain data management tasks where a developer need not be involved. For instance a developer working on an e-commerce site can offload product catalog management to business users who will use this feature to manage the catalog, while the developer focus on the application.

Comments

  1. Could you please send me demo account details? Any email to mackross.net

    ReplyDelete

Post a Comment

Popular posts from this blog

Where do we go from here? Some thoughts and speculation.

A lot of technologist are rightfully fretting about what the future holds for tech careers, especially in software developer roles. Perhaps it is time to think less about what tab-tab-go programming would mean for the future of developer roles and rather how those existing skill-sets could be leveraged in an AI world. There is tremendous potential in reorienting technologists from a focus on churning out the next app from an IDE and towards thinking in a more holistic manner about how to leverage what already has been built out both in terms of software and infrastructure. The past 30 yrs or so of the tech industry has been a ginormous build-out of technological capability. We in the industry may not have seen it that way since we have been the ones engaged in the build-out process. In other words we have seen the build-out primarily as just our jobs, and less as a process perhaps with a terminal date. I wouldn't go so far as saying the build-out is complete by any means, but it s...

Workflow Automation: Letting AI Write Workflow Code

Workflow automation is one those perennial technology efficiency promises that has never quite delivered but never goes away.  The appeal of the idea is obvious, being able to easily direct computers to perform process tasks without deep technical expertise is the holy grail of the promise of computers. The excitement around AI agents is the latest incarnation of this promise. Workflow automation can be implemented in many forms, the most common is some sort of visual composition approach. Drag-n-drop workflow builders for instance are quite common. The fundamental problem that workflow automation has faced is that it attempts to allow non-programmers to...well, program. This is a fundamental contradiction that always reveals itself once one tries to use these products to do anything beyond the demo reel. More recent takes on the idea have taken on the problem with a hybrid approach, ie code when you need it and UI when you don't,...this is the literal tagline that the popular work...

AI Agents: Human Synthesis vs Human Substitutes

Human synthesis vs human substitute , this appears to be the two core perspectives for accessing AI when it comes to agentic execution.  From a human synthesis perspective, you observe that for the first time we have broad computational access to what were previously uniquely human capabilities. At the moment this can be enumerated as the ability to speak , see , hear and understand information . When hominoid robotics are mature enough, we can add the ability to use limbs to this synthesis. Prior to the emergence of LLMs, if you had a process that required any one of these capabilities, you needed to plug a human into the loop. It didn't matter whether the human had any particular expertise or not, if you needed to know what's in a picture or what someone said, you needed a person integrated into your process.  LLM/AI have changed this, we now have computational access to what I would describe as human synthesis . This is different from human substitute , which is what ...