[om-list] codefarms (was Re: strategy

[OneModel general list]

Some discussion about a programming library and OM, with Jiri Soukup's 
permission.

(Here are some of his urls, from other/prior emails:
www.soukup.ca
www.codefarms.com
.)


> On Apr 19, 2016, at 09:27, Luke Call wrote:
>
> Postgres has been a rock-solid workhorse for a long time and I don't have a performance problem.  The bidirectional stuff is just another query or so, but will be driven by feedback per feature priorities.  I have some notes on what I'm going to do there but it hasn't become the top priority or even close.  The app isn't in c++.
>
> In fact, it might be able to scale to a billion entities per instance without having to reconsider the database, and then maybe it can scale by simply having more instances, and/or using a nosql system (like cassandra or other).
>
> Another programmer has suggested a graph database because of efficiency of certain types of queries.  But I won't seriously consider that either until real users run into real performance issues.  Everything has tradeoffs.
>
> My current priorities, rather, are features and funding.
>
>> On 04/18/16 13:09, Jiri Soukup wrote:
>> Unless I am mistaken, you represent knowledge as a set of object
>> "connected" by multiple relations, and this knowledge must be stored.
>> The faster you can traverse, grow, and modify this knowledge, the better
>> will be the performance of your system.
>>
>> What I have is a more advanced library of data structures than using SQL
>> or STL, more complex relations and traversals, including bi-directional
>> relations that nobody else can handle.
>>
>> Data structure built with these relations is transparently stored and restored,
>> so the implementation of storage is completely covered, and not only that:
>> The performance is roughly order of magnitude better than when using other
>> existing approaches.
>>
>> Because my library and data structures are schema driven, maintaining
>> and evolving the system is extremely simple and safe which, I believe,
>> is the main benefit of our system. It supports a truly agile development style
>> of many people without losing the control and while keeping everything safe.
>> Jiri