-
I think we should briefly document the major architecture design decision, eg code organization, bootstrap sequence, architectural components. This can be very brief. The important thing is to have a …
-
**Summary**
In the port + improvement we made a lot of design decisions re: software architecture. It would be good to take a look at these decisions and make sure they were the right ones.
Specif…
-
# Background
Since this is a bit of a green-field project I wanted to jot down some notes about how to structure the project.
Some guiding principles:
- Should re-use existing code libraries as …
-
New to project, so feel free to ignore, but the following is my proposition seeing little in the way of documentation and some sort of 'in-progress' architecture around build, CI / CD, etc.
Proposa…
-
This project seems really interesting.
But, I found some architecture decisions questionable.
I would like to ask some clarifying questions.
## Monolith vs Plugins
The first thing that came…
-
Features to import/discuss:
- [ ] where should the examples live / repo structure
- [ ] separate the scheduler and the communication mechanism.
- [ ] RosMsgs
- [ ] ZMQ
- [ ] Compatibility with ex…
-
This issue started as a think-through of the interface for generic repositories within our app, but kind of grew from there. I apologize in advance for the moderate brain dump. I'm hoping to treat thi…
-
Several OEPs were authored aspirationally, and then never implemented. Other were partially implemented, but have stalled or diverged from reality. Yet others should be followed by the community, but …
-
**Description**
We need to model TraderX via CALM. This approach will involve defining the architecture of the application in a machine-readable format, ensuring that all architectural decisions and …
dc-ms updated
1 month ago
-