Graph Dependency Management Framework [closed] - graph

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 days ago.
Improve this question
What framework could be used for graph dependency management?
Here is my challenge, we have a set of entities in child-parent formation organized in an hierarchy which could easily be described as a DAG. Each entity has a certain state which influences the parent state.
We are looking for a framework that could rapidly compute the entire graph state upon each change to a node state or upon addition/removal of any dependency, i.e edge in the graph.
Persistent solution would be preferable.
We looked into some graph db solutions, seems a bit overkill

Related

Any thing about How to Design Components mentioned in How to Design Programs? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I've just started reading How to Design Programs (2nd edition) on htdp.org
There are several notes in this book mentioned next volume called How to Design Components (e.g. the 3rd note in part one), however, I just can't google anything about the 2nd volume book.
I'm wondering why it is so hard to find any information about the latter volume. Has it finished? If it has not finished yet, how can I get information about the book?
The first author provides more information on his website:
We have decided to provide the draft of "How to Design Classes" (pdf)
on an "as is" basis for now. You are free to download and print it.

Map/Diagram PL/SQL Call Stacks [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I've recently inherited a collection of PL/SQL packages/procedures. Most operations involve one procedure calling another procedure which calls a third procedure, etc. I'm sure it made sense originally, but I'm struggling to get a good overall view.
Does anyone know of any software that maps/diagrams out the permutations of procedure call stacks in a visual way?
Found out about a view called dba_dependencies from http://www.dba-oracle.com/d_dba_dependencies.htm which appears to contain a raw form much of what I'm looking for. (The one drawback is it shows what packages are called by a specific package, not what procedures in a package are called by a specific procedure in a package.)

Broadcast peer-to-peer network [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
Can someone suggest some ways to implement a high-level design for 'broadcast peer-to-peer network'?
Sounds like you're simply describing the internet. No limit on nodes, nodes can join/leave anytime, redundant routing makes the network robust, load balancing can ensure you're not using some nodes too much.
Your last requirement... consistency... that really has nothing to do with the network. What you're looking for is an eventually consistent data store, and without knowing more about your specific requirements, it's not possible to give you much more of a specific answer. There are many tradeoffs you need to choose related to the data size, latency, atomicity, sharding, replication factor, etc.

I have specific tabular data, how can I represent this with Polymer with 2 way binding? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
Are there any components built with polymer that allow displaying of tabular data? I would like something that compares with current UI grids out there.
I am interested in infinite scrolling and 2 way binding to json data in particular.
One good place to look for such things is the Component Kitchen
Looking there I found aha-table. It doesn't appear to have infinite-scrolling, but it lists pagination as a feature.
Not a completely useful answer but here's what I'm aware of:
Seems that the team plans to add what you're looking for - https://github.com/Polymer/core-list/issues/20
This might help you do something now - https://github.com/polymer/core-layout-grid

Design Pattern for Components that depend on each other [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
We are building a "configurator" application for conveyors. Basically user comes in and picks a model, then start picking the parts they want. Some components have dependencies on other components. E.g. if I pick Part A, then I am required to select 1 or more Part B's. It is somewhat similar to configuring a PC at Dell.com. The app will also provide suggestions on parts/components.
Based on this info, I am researching if there is an existing pattern(s) that would allow us to make this easy to maintain and design. Any thoughts, ideas? Are there any open source projects that have similar functionality I can borrow ideas/patterns?
I am mostly interested in how to define "rules" between components without hardcoding the rules/dependencies.
Thanks for any help.
Not that it should matter, but we are building this in .NetFramework 3.5/Asp.Net
Without a good reason to do otherwise, I'd keep it simple and each part would have a list of dependent parts.

Resources