Click on the "Follow" button below and you'll get the latest news from Cadence Blog via email, mobile or you can read them on your personal news page on this site.
You can unsubscribe anytime you want easily.
You can also choose the topics or keywords that you're interested in, so you receive only what you want.
Cadence Blog title: Arrow divert (filled)
Is this your feed? Claim it!
You encrypted the payloads. Here is what you did not encrypt.
The AES-256-GCM DataConverter makes every workflow input, activity result, signal payload, and query response opaque to anyone without your key. That is the good part. The less obvious part: several Cadence data surfaces sit entirely outside the DataConverter path, and they are still plaintext regardless of ...
The 2 MB per-payload limit in Cadence does not come with a helpful error. Your workflow does not receive a graceful degradation notice. It just fails. And if you have never hit the limit before, the stack trace is not obvious about what happened.
The claim-check pattern solves this completely. Instead of compressing a large payload and hoping it fits, you offload it to...
That customer order you passed into your fulfillment activity (the one with the email address, the shipping details, and the internal pricing fields) is sitting in your workflow history as plaintext JSON right now. Anyone with read access to Cadence history can see it. So can anyone with access to your history storage backend. This is not a bug. It is how Cadence works by de...