Documentation: Documentation - Diagram of the stack

[manez]

It would be great to have a visual diagram of how of how the components fit together. There is an example here but I don't know how much use it will be as a model for how we should approach this one.

[ruebot]

@daniel-dgi do you want to tag team this in yEd? Or, do you just want to use what you've done in yEd for the ATONEMENT presentations? Or, some combination thereof?

[ruebot]

Place holder for now... this slide.

[DiegoPino]

yED++ easy to use, easy the share diagrams.

[bradspry]

I'm interested in collaborating with y'all on this.

[DiegoPino]

@bradspry++, i'm finishing the logical diagram (data flow) today. Will share that with you (today late, late night) and would love to have a parallel diagram working only on stack tech components, if that sounds good for you.

[bradspry]

@DiegoPino Yes, I think this activity represents a great approach for really learning how it all works.

[DiegoPino]

@Islandora-CLAW/7-x-2-x-committers and @Islandora-CLAW/7-x-2-x-sprinters

Before this WIP gets lost in my Hard drive (sitting here for a few days already), i would love to share it with you. It's not fully finished (missing routes, etc) and it also need some reordering + making a more simple version one (without all the routes), so basically it's a draft (not even sure if useful) so Sorry!!

There is an editable yED graph file (using free app from http://www.yworks.com) and an exported JPG

https://drive.google.com/file/d/0B4LcIeJDX_k3bzVpcDdLaHppRzQ/view?usp=sharing
https://drive.google.com/file/d/0B4LcIeJDX_k3SzNaX1RDbVF6akk/view?usp=sharing

Any help on this (even comments) would be very appreciated, i will try to make a more resumed diagram in the next days. Thanks

[ruebot]

@manez @DiegoPino should we say this is resolved with the CLAW Lessons? Or should we have a stand alone diagram?

[DiegoPino]

@ruebot i have a new simplified diagram (from fedoraCamp). Will sent to you.

[ruebot]

[DiegoPino]

Adds a missing activeMQ connection. We will need to update this to add microservices

[acoburn]

Can I suggest that you replace "ActiveMQ" with "Message Broker"? Eventually, it should be as "swap-out-able" as Blazegraph is for Fuseki or MySQL is for MariaDB.

Also, I'd be really careful when specifying "topics" -- these are dangerous because they don't guarantee message delivery and in several well-defined circumstances you can get messages dropped. While topics are nice for being able to have multiple simultaneous subscribers, you can achieve the same thing dynamically with queues. That is, if Fedora messages are initially pushed onto a single queue, you can broadcast those messages to other queue-based endpoints really easily. Here's an example: https://gitlab.amherst.edu/acdc/repository-extension-services/tree/master/acrepo-connector-broadcast

[whikloj]

Resolved?!?!? with https://github.com/Islandora-CLAW/CLAW/commit/672e31bc81b734163dc5382edcdb27d05d35287f

[ruebot]

Until we update the diagram again! :dart: