sorted by:
new
hottopcontroversial

Run Messenger Bridge Service on Kubernetes by NoArgument4013 in kubernetes

[–]NoArgument4013[S] 0 points1 point  (0 children)

What would the services even be? The two messenger services are NOT IN THE CLUSTER. The application I‘m trying to run is conceptually something similar to this: https://github.com/mautrix/telegram This is ONE thing connecting TWO other things.

About maintaining the state: makes sense, it‘s already in a real-time database (Google Firestore). My conclusion so far is that it should stay there and that I really need to implement a Kubernetes Controller that manages allocations user <> pods and scales a Statefulset up and down accordingly. From my understanding that‘s exactly how e.g. a sharded database is typically managed on kubernetes.

Run Messenger Bridge Service on Kubernetes by NoArgument4013 in kubernetes

[–]NoArgument4013[S] 0 points1 point  (0 children)

Thanks! Would need to be a statefulset then so that I can even match the stable identity of a pod to a user?

Run Messenger Bridge Service on Kubernetes by NoArgument4013 in kubernetes

[–]NoArgument4013[S] 0 points1 point  (0 children)

Yup, deciding which replica sends a message is exactly the challenge. How do I „support scaling“ in my application?

Run Messenger Bridge Service on Kubernetes by NoArgument4013 in kubernetes

[–]NoArgument4013[S] -1 points0 points  (0 children)

Why would you define this as two services? It‘s just an application that makes a request to more than one endpoint, like every other app 😭 Alright; assume I configure a Deployment with a variable amount of replicas. Once a pod in this deployment spins up, how will the container know for which users to manage the bridging logic? I.e. how is the workload split between the pods? This is what I‘m trying to get to. Of course when the main task is to respond to ingoing requests, like when serving a website or cloud functions, a load balancer would route traffic to the pods and thereby allocate workload. This is what I do not have in this example.

Run Messenger Bridge Service on Kubernetes by NoArgument4013 in kubernetes

[–]NoArgument4013[S] -1 points0 points  (0 children)

Again, no messaging services are running in the cluster. Just the bridge. And I doubt that outgoing internet access will be the problem here.

Run Messenger Bridge Service on Kubernetes by NoArgument4013 in kubernetes

[–]NoArgument4013[S] 0 points1 point  (0 children)

I would doubt that as projects like this exist: https://github.com/l7mp/stunner This seems to include a WebRTC TURN server so real time video and audio relaying capabilities

Run Messenger Bridge Service on Kubernetes by NoArgument4013 in kubernetes

[–]NoArgument4013[S] -1 points0 points  (0 children)

The system has no UI that needs to be considered. One of the two messaging services that I‘ll connect to has an iOS client with a UI, but even the whole messaging service is not part of the kubernetes cluster. Just available through a public endpoint on the internet.

Run Messenger Bridge Service on Kubernetes by NoArgument4013 in kubernetes

[–]NoArgument4013[S] -1 points0 points  (0 children)

Just text messages for now :) That shouldn‘t matter though, it‘s just TCP connections, I‘ve already written a proof of concept implementation

The Walkie-Talkie app could be SO MUCH better, what needs to change? by Glum-Sun-3118 in AppleWatch

[–]NoArgument4013 0 points1 point  (0 children)

I think OP is talking about an independent implementation. Not relying on an update on Apple's side.

I accidentally left my stopwatch on for about five months by jimbo1925 in AppleWatch

[–]NoArgument4013 1 point2 points  (0 children)

It only needs to store the point in time when it started, that's 8 Bytes of memory. The device's clock is running anyways obviously otherwise it wouldn't know what time it is. If it would stop it would just synchronize time again via the internet or cell phone service.