This is a small but important release that allows brings the Python runner nearly up to full functionality and an improvement to the client that allows calling Scramjet Transform Hub directly from the browser!
The Python runner now fully supports input and output data, stdio is well handled and well tested.
The new runner now supports:
si inst stop on a python instance no longer kills the sequence unconditionallysi inst health from Python!si inst event and similar operations will now allow event handling and messagingPYTHONPATH dependency resolution.So drop your index.py in your favorite flavor of vi and paste this:
_10from scramjet.streams import Stream_10_10def run(context, input):_10 return Stream.read_from(input).map(lambda s: f"Hello {s}!")
We need to allow Python to work without Scramjet Framework, but this will come in an upcoming release.
Previously the Scramjet API Client would work only from node.js. The main reason for this was using node-fetch as one of the dependencies. We do believe it's a fantastic module and one that should be included in the base Node API long time ago. Since we do want to support node.js 14 and 16 at least until the end of life we needed to find an alternative solution. We managed to find @sapphire-fetch - a simple way to support a proper W3C Fetch API without the hassle of having to deploy multiple modules.
I'm happy to announce that STH will gain a really important feature: you will be able to run stream processors on any Kubernetes cluster. We're working on proper documentation of how to start that up, but currently you will have access to the three execution adapters:
docker - the default for running sequences in a standard server spaceprocess - the adapter running non-separated processes for simple deploymentskubernetes - for deployment in cloud environments and leverage multiple serversThe kubernetes adapter is expected to come early next week, so keep checking. :)
Photo by jggrz