'production ready' might be a bit misleading, especially when we think about certifiation

[matgnt]

Thanks for this great resource! I'm still digesting the content :-)

One hint: Since Catena-X is mentioned an that this is production ready. I think it would be a good hint to let the users know that it is NOT allowed to be used in Catena-X 'as-is'. The organization who wants to use this, would need to go through a certification process first.

Thanks,
Matthias

[jbuerkel]

Thanks for the feedback Matthias! Great to hear that you like this effort. With "production-ready" I'm referring to technical aspects, i.e. the security controls we've included, resilience posture covering fault tolerance, automated recovery, deployment across multiple AWS availability zones etc.

But you raise a valid point specific to Catena-X regarding certification requirements. To clarify: We use the exact Tractus-X EDC version that is required by Catena-X for a particular major release (currently still Jupiter, in transition to Saturn). My assumption was that Tractus-X EDC is the reference implementation that fully meets in this case CX-0018's requirements. Is this assumption wrong?

We're only covering connectivity in this project as of now, so we of course do not meet requirements for use case-specific standards, DTR, provider base etc. - what would make the most sense from your perspective in terms of wording that we should include in the README? I'm considering to add this to the existing Catena-X info banner near the top.