Delivered (Currently Alpha Release)

Coming Next (Upcoming Beta Release)

Mid-Term

Long-Term

Main Roadmap

In Review

Graftcode Portals

[NEW] Added registration / login based on Auth0

pladynski

In addition to Websocket Secure presented in PMF demo, November release introduces full support for direct TCP/IP TLS channel.

Graftcode Gateway

Support for TCP/IP Protocol

With this release Graftcode Gateway on all platforms will be installable without the need to install any prerequisite dependencies.

Removed all dependencies required to install Graftcode Gateway

If you don’t want to publish all your public methods you will be able to use filter to select one or multiple types that should be exposed as grafts. Library with applied filter will have special suffix with short hash of filter and ensure same filter for same lib will always produce same module name.

Grafts Supremacy

Filter types support in Gateway

Graftcode

Redesigning activation mechanism to allow full FREE usage without account for simple use cases and research and no need to connect with our servers to use premium features (allowed capabilities will be embedded permanently within Grafts)

Hypertube

Real FREE usage comes to Hypertube

Graftcode Gateway performance has been improve significantly further surpassing REST and gRPC performance by 70% and reducing cloud resources cosnumption 8-fold!

Significant improvement of performance

New Grafts have enhanced naming conventions for namespaces, classes, fields and methods.

Unified naming conventions

o&nbsp;&nbsp; Now can be passed in-code, via env var or config fileo&nbsp;&nbsp; Ability to easily configure each module separately

Support for new configuration mechanism (Grafts Connection Strings):

Now generating Grafts will fully support invoking async methods including automated translation of async task to calling technology structures like Promise, Task&lt;T&gt; etc..

Significant improvement of async support across all technologies

Align missing support across technologies and improve the Graft classes structure, exceptions forwarding and more to achieve same level of functionality across all supported technologies.

Significant improvement of support for static, instance fields and methods across all technologies

Now you will be able to pass custom logger to imported Graft and it will be used to report all operation on Graft, logs from sending request and retrieving results. Graftcode Gateway will support custom loggers too allowing you to continue logging on server side up to your business logic preserving Span and Trace so all logs will be fully correlated.

Planned

Enhanced logging -  Full support for OpenTelemetry Monitoring and Observability with TraceID and SpanID

With this improvement whenever you pull Grafts with any Package Manager other than Nuget you will not need to explicitly pull the Hypertube dependency (currently you need to manually make i.e. npm install javonet-nodejs-sdk prior to any graft resolution)

Automated resolution of Hypertube Dependency from Graftcode Registry for other than Nuget technologies

With this release we are planning to provide support for HTTP headers for edge client connections based on HTTP/2 or Websocket channels allowing for passing any header related information as well as Authorization header with either JWT, Basic, API Key etc.. and full support of injecting this state into standard HTTP context on called side allowing for Authorization headers functionality

Plugins

Release of the Authorization header support

Now calling technology will be able to use local classes that wrap value types like Date, Color, Point and passing them to target service or runtime will automatically convert them to target technology wrappers by passing value of ticks, Hex, X,Y etc…

Support for using calling technology classes wrapping value types (i.e. Date)

Academy will soon show samples on vue, angular, nextjs, vanillajs and webassembly, svelte, solidjs, Astro, qwik, preact

More frontend frameworks in academy

Adding MCP config in vision portal installation command widget we will make it super easy copy-paste only step to get ready config to paste in your chatgpt, postman or Claude to connect with MCP server exposing your public methods from modules hosted in Graftcode Gateway.

MCP Config in Vision Portal

With this feature your gateways details panel in servicemap and gateways section will start presenting which runtimes are running on specific gateways and what modules are hosted there and in which version.

Modules and Runtimes list for Gateways

With Activity feed in portal you will be notified about each event across your projects, when new gateways are started, once new modules are hosted, new versions released or grafts pulled. Everything will get highlighted right on your dashboard.

Activity Feed - Stay Informed

With this feature you will be able to use not only websocket and TCP/IP but also HTTP/2 multiplexed streams as communication channel for edge clients using Grafts.

Support for HTTP/2 as communication protocol

Surprising its still not there but we are in alpha so everything can happen! With this feature you will be able to manage your account details and same for workspace and project.

Settings section for Account, Workspace and Project

To ensure smoother download and pass through OS gatekeepers for our Graftcode Gateway we are planning to start signing the binaries to increase filter trust.

In Progress

Code Signing for Graftcode Gateway

With this feature <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Graftcode.com">Graftcode.com</a> will show you all the details per each critical use case where you can apply graftcode.

Use Cases Dedicated Landing Pages in HomePage

Our Academy will start presenting sample projects with frontend, jwt authentication, stateless backend, and queue between microservices, exposed public api and dependency injection and mixed modules in specific services so you can easily apply graftcode into your project. All of that with great OpenTelemetry support. Sample will show also signalR like bi directional connection and streaming sample.

Sample Real Production Project in Each tech pair

With this quick start guide will show you how to work in stateless with complex objects. It works now but good sample is worth more than promise ;)

Examples with complex objects in stateless in arguments and results as part of quick start guide

tool for generating graft for local library without hosting it on graftcode gateway it will support polyglot monolith workflows to get locally command to install package via graft to allows future decomposition or to host multi tech in one process

CLI for generating grafts

We are planning to start publishing official forks of know containers for python, ruby, php, node, netcore, jvm with predownloaded Graftcode gateway to simplify your dockerfiles even further.

Official docker images with Graftcode Gateway

We are planning to work on standardizing and providing centralized interception/middleware of network related events like: connection lost, timeout, target memory recycled, host not availableGraftcode Network ExceptionsClient-side Exceptions (thrown in the generated Graft client):<ul><li>GraftConnectionRefusedException – Thrown when the remote Graftcode Gateway cannot be reached or is not listening on the configured endpoint (service down, incorrect host/port, or firewall blocking).</li><li>GraftConnectionTimeoutException – Connection attempt to the remote Graftcode Gateway timed out.</li><li>GraftUnknownHostException – DNS resolution failed for the target hostname.</li><li>GraftConnectionResetException – Connection was forcibly reset by the remote peer (common after service restart, crash, or load balancer drop).</li><li>GraftReadTimeoutException – Timeout occurred while waiting for a response from the remote method.</li><li>GraftWriteTimeoutException – Timeout occurred while sending the invocation request.</li><li>GraftTlsHandshakeException – TLS/SSL handshake failed (applies to wss:// endpoints).</li><li>GraftCertificateValidationException – Server certificate validation failed (expired, self-signed, hostname mismatch, or untrusted CA).</li><li>GraftWebSocketUpgradeFailedException – Failed to upgrade the HTTP connection to WebSocket.</li><li>GraftProtocolViolationException – Received malformed or invalid binary data according to the IIP/Hypertube protocol.</li><li>GraftInvocationTimeoutException – Remote method execution exceeded the configured timeout on the server side.</li><li>GraftDeserializationException – Failed to deserialize the response received from the remote service.</li></ul>Gateway-side Exceptions (thrown by Graftcode Gateway gg):<ul><li>GraftPortBindingException – Failed to bind to the configured port (port already in use).</li><li>GraftPermissionDeniedException – Insufficient permissions to bind to a privileged port (&lt; 1024).</li></ul>Base Class Recommendation All network exceptions inherit from GraftNetworkException for unified handling and easy distinction between transient and permanent errors.

Centralized and standardized exceptions for network related events

With this feature graftcode will hold on client side the id of remote memory for which the stateful connection was maintained in case of reconnecting the channel and getting connected either to different node or recycled memory in target node appropriate exceptions will be raised to let the client rebuild required objects in target memory.

Auto discovery of restoring or loosing stateful connection

Allow configuring cors for graftcode gateway so it’s sent for http/2 preflight options or validated for websocket

Add cors parameter to Graftcode gateway

Support for Swift and Dart

With this feature Graftcode Gateway will allow you to indicate the minimal or mandatory minimal version of the grafts to interact with the service and will cause the exception in case user tries to connect using older version of graft.

Completed

Min or Must Have Min Graft Version on Gateway

Method comments will be passed to grafts and MCP tool definitions.

Grafting Methods Comments

With this new grafts will forward the obsolete and deprecated attribute on methods to ensure user is notified in advance about upcoming breaking changes to API.

Propagate Obsolete and Deprecated Attributes to Grafts

With this feature you will be able to specify which fields of expected result object you would like to retrieve in the by value unary call in stateless connection. That capability will allow you to leverage Graftcode across scenarios previously addressed with GraphQL.

Support for Projection in Stateless Unary Calls to Provide Selective Retrieval by Value

With this feature for more loosly bounded invocations you will be able to use from your grafts HTTP/3 QUIC as underlying protocol for communication from edge clients achiving uninterrupted parallelization of remote invocations to your backend.