pibi
Joined 14 years ago
Joined 14 years ago
Fast, battle tested, vue2-like approach, great documentation, good community. The automatic indipendent-scalability as an option is usually the main selling point of these solutions, but honestly I think the real pro is the "composition" approach, which is essential if you want to keep a clean and well-organized codebase. On this regard, I found moleculer pretty great even for large teams.
But yeah, it's ridiculous still conflating the two after all these years of full-stack Javascript developments.
That said, I'm always wondering why we are conflating so many things when talking about microservices: deployment and scalability, multi-repo and code structure, integration tests and distributed transactions, and so on. I mean: you can definitely build your application as a monolithic process with a microservices' architecture. It's just separation of concerns all the way down and a proper abstraction for the communication channel between the "modules". You don't need to embed your deployment structure in your repos and your code. These are "framework" problems. Just use one that abstracts all the deployment details until it's time to push the code to prod, and you have to split your code in different containers. This is why I'm now settled on Moleculer (https://moleculer.services/). It just works.
var isOdd = require("is-odd");
console.log(isOdd([1])); // TRUE!!Also, I can replicate my validations at many levels down the stack: from the client to API-GW to the database model. All with a single definition.
We were using kdb before, but clickhouse is more scalable, way cheaper and much more easy to grasp for a newbie.
It's also very quick, you can have your cup of coffee within a couple dozen of seconds. Not very hot in this case, but still very tasteful.