Hey! I am building Microservices framework with focus on simplicity and potentially targeted to dev environments, it's in veeeeeeery alfa stage, so only WIKI exists reflecting current design and use cases. However I'd like to get some feedback to see if see the whole thing make a sense. Thanks

top 4 comments

sorted by: hot top controversial new old

[–] ICastFist@programming.dev 3 points 22 hours ago (1 children)

How would explain what this is for to someone who doesn't know what this works as an alternative to?

[–] melezhik@programming.dev 3 points 21 hours ago* (last edited 21 hours ago)

Ok. Huge part of building microservices framework is infrastructure automation - like setup nginx load balancing in runtime, build and deploy apps from source code, configuring services, tcp ports, health checks, horizontal scaling (adding new worker nodes), setup logging and monitoring, etc, also this needs to be propagated to all cluster nodes, I am not going to do this from the scratch - Sparky is alike (rough comparison though) ansible but with UI and programmable on Raku, so as Sparky has already addressed the mentioned tasks, it's logical for me to carry on with it. If we take Sparky out of equation, Raku by itself is reach and super flexible language to automate infrastructure, I don't see why can't I use it for that ...

[–] qaz@lemmy.world 3 points 23 hours ago (1 children)

Why did you decide to go with Rakulang?

[–] melezhik@programming.dev 3 points 22 hours ago

The plan is to build the entire system on top of Sparky which is written on Raku and extended by Raku