A few months ago I conducted a survey among the Moleculer users to learn how they use the Moleculer microservices framework in their projects. I also asked them why they love it and what they miss.
I’ve received 131 responses. Here is the result of the survey:
Some answers from the “What do you like about Moleculer?” results:
“Architecture and ease of use , decreasing time to market.”
“Easy to develop with and flexible”
“The best microservices framework ever”
“Flexibility and a proposed coding pattern that solves most problems”
“I like the number of built in features and how moleculer can integrate with others technologies.”
“It’s really fun and easy to write code and since there are certain similarities with VUEjs it was an excellent choice for us. The documentation is really good and for us Moleculer was a huge improvement, we used to write our REST api’s using HAPIjs and once we get familiar with Moleculer it was love at first sight.”
“extreamly complete ecosystem to write microservices solutions out of the box”
“Moleculer has a well considered architecture on the high level. It’s relatively easy to get a new project up’n’running. Moleculer has all of the required infrastructure features for the production ready, robust solutions.”
“Extremely well-thought design and implementation. All the benefits of cloud-native patterns without the expertise and time needed to implement all of them.”
“The modular nature of the framework, the array of standard features for doing microservices out of the box (caching, transport, tracing, logging, all things that we’d need to build!)”
Some answers from the “What do you dislike about Moleculer?” results:
“typescript handling . lot of types are not done, or blocking (I stop using channels because it break my build)”
“Sending back metadata in stream responses is a bit hacky, if it gets returned within deep action calls over multiple nodes”
“Merche-Shirt sizes are too small for fat guys like me.. :D”
“Why not rewrite the idea of VueJS composition api. And why not rewrite it by Typescript ???”
“The name of moleculer makes it infuriating to google solutions to issues :D”
“The documentation needs to be more clear and provide some example on how to use it, since we dont have larger community”
“I would like Moleculer more visible. Like Nest, Next, etc.”
“Documentation on the modules can be improved”
“missing rust port”
“One db per service. We try to create our own repositories to offset this”
“It’s missing a correct recovery system, like saga Typescript support lacking”
Some answers from the “What features would you like to see in Moleculer in the future?” results:
“More flexible api gateway and websocket and tenant for populate scenarios support”
“Better typescript handling”
“Dynamic event subscription”
“TS support, OpenTracing support”
“OpenTelemetry”
“build in locking mechanism, ability to disable service discovery”
“I would like to see most impressive integration modules with front-end frameworks, like nuxt/next”
“Maybe additional complex examples, tips and tricks, tutorials or courses will do a lot for future developers”
In order to make the Moleculer framework even better, I will contact some developers who dislike or are missing features in the Moleculer framework.
Last but not least, I promised I would draw a gift from Moleculer’s shop among the respondents. The lucky responder is Phil Choi and I’ve contacted him for the details. Congratulations Phil!
If you want to learn more about Moleculer then check out our website https://moleculer.services or GitHub.
Follow us on Twitter at @MoleculerJS or join Discord chat.
