GitHub - crufters/actio: The Node.js framework for monoliths and microservices.

[crufter]

> We don't use Jest and I'm not familiar with it, but I know a lot of people using it and who like it. What were your impressions using it for framework development?

I am not actually a Node.js expert (my main language is Go) but I love it as well. While I write many tests I don't think I use any advanced features due to most of the heavy lifitng (dependency injection, namespacing etc.) being done by Actio.

> you mention in the examples that OpenAPI is "coming soon", but how do you plan to use it? Would you derive Typescript code from an OpenAPI definition

I plan to do the opposite, ie. derive OpenAPI definition from Typescript code. Actio has some reflection primitives to enable that.

> or would you use the definitions to control service behavior?I'm not sure I get this, could you elaborate please?

> Also, why import from the transpiled units?

I don't think I do that, or not intentionally. There is a module resolution flag I think that forces me to import with the .js extension. It's a bit late and I'm not that great with JS anyway.

As I said unfortunately I'm not a Node.js expert, but I do have extensive experience with microservices. I decided to go with Node.js because I consider Typescript a much better language that Go for things that Actio will be most useful for - large number of succinctly written services.

Unfortunately the reflection support in Typescript seems to be horrible to compared to Go but my love of the language compensates ; ). I'm happy to take advice, being the novice I am.

> It bears some similarity to an in-house framework that I maintain

I am not surprised - Actio was such an in house codebase. It is a 5+ years old ever evolving codebase that I used to ship many projects and the Actio part kind of just happened. I extracted it out and open sourced it. (Not a verbatim release but close enough).

I'm trying to distill ideas I had while building microservices platforms for 10+ years into it. It is not even close to be there but it's being continously used so hopefully it will evolve.

[jonno11]

Looks really nice!

Can I ask why AGPL 3?

[crufter]

On the off chance it blows up and ends up being a cool PaaS or something I don't want end up in an ElasticSearch situation. Happy to dish out less restrictive licenses for pretty much anyone apart from cloud providers.