slack VS fission

Though I am thinking of converting my Python Bolt slackbot (very early in development anyway) over to using slack-go. Mainly wanted to rewrite some of it anyway and use socket-mode.

code looks to be BSD licensed from https://github.com/slack-go/slack/blob/5a6b1b08ff8fa911e85bd582de643f7f0df0f0fb/chat.go

I have created a Slack bot that acts on some slack events to create Jira tickets using Slack Go. It was a hobby project for me but it's being used for some teams on my company.

I have also tried to do this in Go, because I always would try to do something in Go given the opportinity, but the Go Slack API was using the outdated auth system, there was simply no documentation to follow at all. I see this in my second attempt at using Go, having no tools to use, or no instruction to follow. Oh well, maybe the next project...

We use this library github.com/slack-go/slack for the API calls and data model.

The Slack Go SDK is a community SDK and not officially maintained by Slack. This means it doesn't get the same care or attention in terms of documentation and code examples.

I am using Slack-Go (https://github.com/slack-go/slack) to create a modal to allow my users to enter some information.

Does the example in the repository for the Events API not useful? https://github.com/slack-go/slack/blob/master/examples/eventsapi/events.go

I came across the well-maintained slack-go library; I started coding my bot using the provided example. Everything worked fine; The code is producing the expected result. It is time to make another coffee and implements a few extra features.

Fission

This is where I see K8S coming in – teachers can provide dev deployments that are setup for students to learn. Teachers can also provide containers that run automated tests against the student containers for assessment! Plus, we can smooth over some of the git workflow stuff for the ripest of beginners; we can integrate with github to sync their work on our platform to repositories on their github account, so that they can really take ownership of the work they do on the platform. Last, students can graduate their work from development into production very easily, since we can take the base images + student diffs, build a new "prod" image for the student. We can run students' prod work on "serverless" K8S frameworks like fission or OpenFaas to be able to host many low-traffic "production" apps at the same time.

I use https://fission.io/ on Kubernetes to emulate AWS Lambda + API Gateway to run Python functions. I use their YAML Spec functionality to deploy functions. It works well for my use case.

After doing a lot of research, I ended up settling on the Fission.io framework to support this project. Fission is an open-source Serverless framework running in kubernetes. Think AWS Lambdas, but we are in control of every part of the infrastructure. Kubernetes gives us the power to define the environments the containers will be executed in, and any other resources they need. This gives us the control we need to be able to create our very own environment for executing arbitrary JavaScript through the V8 engine. Each function can be isolated as much as we need to and Fission is really great at giving us the ability to quickly create multiple environments.

Nope. I was using https://fission.io/

There are a lot of FaaS service offerings out there namely Lambda, Azure Functions, Google Cloud Functions to name a few. While these offerings run on their respective clouds, there are services like Fission that are open source and allow you to deploy and execute functions on Kubernetes clusters irrespective of where they reside.

Fission

It's super slow (20-50 rps), please try this instead : https://github.com/fission/fission (few hundreds to few thousands rps)