pibi

My goto for this kind of task is moleculer: https://moleculer.services/

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.

Intl could be considered a JS API, honestly.

But yeah, it's ridiculous still conflating the two after all these years of full-stack Javascript developments.

I'm working with microservices all the time. Even when working solo. It's easy to focus on a single domain while developing a single part of the system, just like coding modules or classes.

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.

Well, it's all about the data responsibility: who is the owner of the data, how others can access the data. Once you have defined these, you see that you can "share the access" with other microservices (for example read only mode on a view), as long as the ownership and the access rules are preserved.

Clarify the microservice architecture concept with "how you are going to deploy your system", as per your example, is exactly what I'm trying to explain to my teams since the microservice architecture inception. There are too many concepts conflating into the "microservice" term: code architecture(separation of concerns), source code organization, deployment, etc. This is very confusing, which is the reason why it's now common to say that microservices are "hard".

Actually useful is subjective. What's the carbon footprint of all the gpu rigs in the world used to play video games? Is that useful for you?

I love the fact that this small code is still wrong:

  var isOdd = require("is-odd");

  console.log(isOdd([1])); // TRUE!!

It's really not that hard-to-read or to-write. I have instructed dozens of young developers on that with almost no-supervision and no-issue. It's really pretty straightforward.

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.

Years of daily intraday market data. We have an ingestion engine written in c# and a nodejs backend to run the queries (with an in-house driver built on top of the HTTP APIs)

Actually not, but we are ingesting a whole day of EOD market data (thousands of symbols, millions of timesales, billions of books events) in less than a couple of hours. This is 4x faster than the pace of the realtime market (not counting the extended hours due to the limited volume).

Great software. We are managing terabytes of stocks data and realtime market scanners queries across all market (billions of books and timesales) with hundreds of concurrent requests.

We were using kdb before, but clickhouse is more scalable, way cheaper and much more easy to grasp for a newbie.

Hey, thanks. I'm aware there are so-called alternatives (Banana Blossom, Tofish and such). Unfortunately, from my experience they don't taste like fish yet.

After "seapiracy" I don't really think we are addressing the biggest issue here. I would like to know if there's anything like that for fish. I would buy anything that tastes like tuna but it's fully vegetable, or any other fishes. Just give me the same taste on my sushi, please.

Kamira works at 3 bars. It can make one or two espresso at the same time, but no more than that. The design is the opposite of a Bialetti's Moka, where the water is pouring into the coffee from the bottom. On a Kamira, the water is coming from the top, preserving the oils and the cream to being burnt.

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.

Italian here: I'm a proud owner of a Kamira (https://en.espressokamira.net/).

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

Normal life expectancy is lower than that in the United States

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...

I'm mostly a solo developer now, and I'm working with microservices all the time. It's very good to focus on a single domain while developing a single part of the system, just like coding modules or classes.

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)

Already gone? here is the archived link: https://web.archive.org/web/20200128085806/http://chinamedia...

That's my mantra since 5 years now. Swaggerize-express or swole for the routing, but also swaggering-mongoose or objection's schema loaded from the yaml file for the database model. As a plus, validation is available out of the box.

less code, standard approach, less bugs.

Also the "parlo arabo?" is listed on treccani: http://www.treccani.it/vocabolario/arabo

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

Ah ah, good call

Italian here, we use Arab for pretty the same sentence.

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

This is exactly the reason why I'm stuck with Deezer. The random selection, which is called Flow, it's just a never-ending stream of music from the track I tagged and similar songs.

I was head injured at shotput by a classmate. Every person who met me at the time thought I had a motorcycle accident, which I think it's way more common.

Really? Not apples or bread? We have valleys known only for their unique apples, like the Mela Renetta from Friuli. Don't let me started talking about the apples from Trentino. So, maybe you are talking about apples in the south of Italy. About bread: I see where you are coming from, best breads I eaten are coming from bakeries on the mountains. They just taste so good. But please, remember that bread in Italy is just a support for the main tastes, like the olive oil.

https://www.wolkenkit.io/#getting-started-test-drive

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?

Yep, I remember I discovered node (was @v0.1.20 or so) when I was working with Jaxer, 2008 maybe.

UK, US, Malaysia, even India pays well (if you look carefully).

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

While we work to integrate with Coinbase, the Paradex app will be temporarily unavailable, starting today, May 23, at 3pm ET.

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

I cannot speak about Toptal, but Upwork works pretty good. You just have to avoid silly jobs,be focused and perservere.

Disclaimer: I'm italian, working remote, strong focus on nodeJS and fintech, estimated revenue for 2018 (first year of freelancing full-time, not fully from Upwork): 360K$, working 220 days per year