When to use Data API vs RPC API in Workflow Engine NEO: a .NET architect's guide
The article discusses the choice between using the Data API and RPC API in Workflow Engine NEO. It emphasizes that the decision should be based on security and potential impact rather than syntax preference. The author provides insights from customer interactions to guide architects in making informed decisions about API usage.
- ▪Workflow Engine NEO offers two HTTP surfaces: the Data API and the RPC API.
- ▪The choice between these APIs is a security and blast-radius decision.
- ▪The Data API is recommended for integrations that require observing workflow state without affecting runtime behavior.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1475516) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Optimajet Limited Posted on May 19 • Originally published at workflowengine.io When to use Data API vs RPC API in Workflow Engine NEO: a .NET architect's guide #dotnet #architecture #api #saas I am Mike Lukinov, co-founder of Optimajet. Since 2022, I have been closely involved in customer architecture and developer experience work around Workflow Engine by Optimajet. I sit in most customer architecture meetings where Workflow Engine NEO questions repeat.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
