I know you said you didn't like the idea of hashes, so this might be a non-starter for your use case.

But it sounds like a V5 Guid [0] might meet some of the needs for your "operation Ids". The existing "random agent id", and "sequence number" could be used as part of the namespace / salt.

[0] https://www.sohamkamani.com/uuid-versions-explained/#v5-non-...

I don’t have a problem with hashes generally. Correct me if I’m wrong, but this scheme sounds like hashing with extra steps?

I agree this could be done. But diamond types (my library) considers every keystroke to be a new change. If we store a UUID for every keystroke, that’s very inefficient.

Hi, just wanted to let you know we are using this at work. Our flow is:

1) Create OpenApi Spec.

2) Build it out in Mockoon.

3) Share Mockoon endpoint (hosted on aws app runner in a container).

4) Iterate on feedback.

5) Build real thing.

Thanks a lot!

You're welcome :) Always happy to learn about the positive impact of what I built.

If you have any specific feedback or facing an issue, do not hesitate to join our Discord or GitHub Discussions. I will be glad to help!

  Location: Australia, Brisbane
  Remote: Yes
  Part Time / Consultant: 15 - 20 hours a week ($60 / hour)
  Willing to relocate: No
  Technologies: C# / ASP.NET, AWS, SSMS, Serverless
  Résumé/CV: Will reply with CV
  Email: mymailenator at gmail dot com

I have 10 years experience in payments processing (building payment gateways). I have strong C# skills, am a team lead, scrum master (LeSS), and mentor to junior / mid developers.

I am looking for part-time work, if you think I can be helpful to you, then please shoot me an email!