Provider documentation becomes easier to use when you map every feature to five concerns: identity, permissions, resource shape, incremental synchronization, and notification renewal.
Google Calendar uses calendar and event resources, nextSyncToken for incremental collection changes, and HTTPS watch channels that announce a resource changed without including the changed event body.
Graph documents calendar and event operations alongside delegated and application permissions. Calendar-view delta tracks a chosen date range, while change-notification subscriptions have their own validation and renewal lifecycle.
Compare all-day end dates, time-zone identifiers, recurring masters and instances, cancellation representation, attendee responses, conference data, resource calendars, ETags or change keys, and event ID stability.
For every promised action, record the provider endpoint, access mode, least permission, supported account types, limits, error cases, and real-account test evidence. Recheck official docs when provider behavior changes.
No single protocol gives the same broad, modern SaaS integration surface across Google and Microsoft. Their official APIs remain distinct and require provider-specific adapters.
No. It defines intended behavior. Production readiness still requires conformance tests against every account type and operation the product claims to support.
Not as released connectors. Google Calendar has one feature-flagged development method, calendar.event.create, plus list/get for DewEngine-confirmed creates and the resulting canonical creation event. Provider calendar reads and sync, update/delete, availability, recurrence, watches, and Microsoft Graph Calendar remain planned. The implemented slice has only local fake-provider evidence, not real-account or production conformance.
DewEngine is in development. Real use cases decide what ships first.