pibi

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.

Great taste, effortless, no waste, cheap. What else?

I read on your link that average life expectancy in Italy is 83.4, about 4 years more than US (at 78.9). So I don't get your point unless you are speaking about the age structure: https://en.m.wikipedia.org/wiki/List_of_countries_by_age_str...

That said, I'm always wondering why we are conflating so many different 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 in a monolithic system with a microservices architecture. It's just separation of concerns all the way down and a proper abstraction for the communication channel. You don't need to embed your system architecture 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. For example, I'm now settled on Moleculer (https://moleculer.services/). It just works.

(edit: grammar)

less code, standard approach, less bugs.

BTW, I agree with the other comment that this is more common in the north.

That's because we are still studying Greek and Latin on some public school.

I don't see any messages in my network console, so it seems the message form is actually not really sending anything and the app is not a real wolkenkit app. Am I right?

You should not care about the rate, but the value of your work. In other words, it's about trading in value, not time

What's the point of a decentralized exchange if the frontend code can be shutdown at will?