Skip to main content

3 posts tagged with "events"

View all tags

Release v0.0.92

· 15 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release makes it possible to answer "why did this instance fault?" Incidents move out of the Instances.Incidents jsonb column into their own table with unbounded history, a denormalized HasActiveIncident flag with a partial index, and two new read surfaces — GET .../instances/{id}/incidents/active and GET .../instances/{id}/incidents — reached through a link-only incident block that appears identically on the state body and on metadata.incident for both a single GET and every list item (response shape v9), all while taking incident reads on the three hottest paths to zero (#972). Instance status changes move to a Postgres compare-and-set, replacing distributed locks and redundant transactions around the status flip (#975). Discovery registry reads get a read-through L1/L2 cache under the default http provider, plus a hosted bulk-read window and a now-synchronous POST utilities/discovery/refresh — measured p50 0.182 ms on a hit against 100.7 ms on a registry miss (#976). And sub-state changes relay post-commit instead of waiting on the outbox → pub/sub → inbox path, which on preprod once took 6 min 30 s, with the receiver finally taking the same per-sub-item lock the three terminal paths take (#978). This release runs on component schema 0.0.53.

Release v0.0.88

· 14 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release adds two task types and moves authorization behind a provider seam. ExternalHttpTask (type 22) runs an HTTP call directly in the Orchestrator rather than routing it through the Execution service, sharing the existing HTTP configuration, scripting surface and reserved-header hardening with the remote HTTP task (#880). PythonTask (type 23) executes a main(input) contract across Python.NET, an isolated process, or a hardened Docker/Kubernetes container, with strict JSON in and out, centrally configurable limits and no silent fallback between modes (#921). Caller-role resolution becomes provider-based — default keeps today's in-process behaviour, morph-idm calls an external IDM once per request scope and fails closed — while the grant engine, transition.roles, availableIn[].roles, queryRoles, function.roles and schema x-roles all keep their semantics (#927). All distributed events now ride the transactional outbox: the EventHook infrastructure is removed, subflow terminal events additionally settle the parent immediately as a post-commit command with the Inbox handler as a durable deduplicated backup, and a loss-tolerant Dapr nudge wakes the poll loops after a commit — measured relay gap p99 65.9 ms (#927). Polling a parent with an active subflow gets a cache and a 304 for the first time, terminal settlement gains a durable SettledAt marker, and parent loads shrink to exactly the correlation they act on (#928). This release runs on component schema 0.0.53.

Release v0.0.71

· 11 min read
vNext Team
vNext Team
Burgan Tech Engineering

Overview​

This release makes vNext event-driven and query-friendly. Event-driven workflows let an external pub/sub message start a new instance (workflow-level event) or advance an existing one through a triggerType: 3 transition, correlated by an IEventMapping script (#86). A fluent instance query language (InstanceQuery) replaces hand-written GraphQL filter JSON in script mappings — one builder powers event selectors, GetInstancesTask filter specs, and raw list-endpoint query strings. A new GetInstance task (TaskType = 19) returns a full single-instance projection (#806), and function result caching serves a repeat function call from a Dapr state store with a single cache read. Instance start/transition and function endpoints now accept application/x-www-form-urlencoded bodies (#825); output scripts can set the content-type response header and async operations return 202 Accepted (#819). The State function response gains a master schema HREF backed by a new master schema function (#821) and an always-present interaction directive object for long-poll clients. The component schema also ships a new data-vocab vocabulary (x-context-source / x-context-target) for schema-driven client context binding. This release runs on component schema 0.0.50.