Confronting highly intensive CPU operations throughput using different worker threads configurations.
I’ve come to know lately that there is the possibility of making JavaScript execute in parallel, I gave Node.JS worker threads a try, and I’m excited about the results I got.
It would have made everything simpler knowing these before.
The activities we do to stay healthy are not spoken of for good manners, to avoid annoying the interlocutor. We tend to avoid talking about our sex life with the family because it’s terribly embarrassing. We don’t tell someone we’ve just met that he has parsley in his teeth.
But there isn’t any reason to don’t talk about the following things. Personally speaking, I can’t imagine how much even knowing just one of the following concepts would have changed my perspective. …
This article is based on a REAL use case scenario for a database-intensive application, with a focus on performance. The experimental results I’ve come across can help you choose one or the other.
Straightforwardly, the same application has been realized twice using different languages: JavaScript (Node-JS) and Java (Spring-Boot) with performance measuring executed in varied environments.
All the code including deploy (Docker-Swarm) and testing environment (JMeter) is available at https://github.com/GaetanoPiazzolla/spring-boot-vs-node-js free for you to play with and customize.
Index:
- Application and test description — what are we measuring and how
- Results and conclusion
APPLICATION AND TEST DESCRIPTION
We will evaluate the performance of four REST JSON endpoints:
Give the context of a WEB application fault
They found the hanging body on a sunny Monday afternoon. The screen was still displaying the last assigned task regarding a bug fix — misty, convoluted sentences without significance.
In the career of a developer this is a common part: the will to take an end to our pain. Suicide is never the answer — maybe we can reduce suffering related to bug fixing tasks using HAR files.
Content of the story:
- What HAR these — a definition about HAR files and how them can help us fixing and reporting a bug;
- Generate a secure HAR file — using your…
After some experience in the field I have found several aspects that have made me turn up my nose — and I have found some maneuvers to straighten it back.
In the next six sections there is my point of view about the 6 main DOWNSIDES of microservices development — and what I think could be done to reverse some of them to UPSIDES.
1 — KNOTTED REMOTE CALLS
In the past year, I’ve gone through a very tough interview for Amazon AWS. In this article, I’ve described my experience.
I would like to describe it all, starting from the review of my curriculum vitae, the “codility ”algorithm online code challenge, the phone screening interview, the onsite interview (with 5 different people about various topics), and the final call.
I will not report the precise questions that they asked me, but some general information about interviewing for Amazon, the evolution of the long and hard process, and some advice that I wish I had known before interviewing.
Unfortunately, I did not manage to pass the interview, but I’ve managed to learn a lot, about interviewing, about Amazon, about myself. I…
Any user can edit values in the storage — let's encrypt them.
We found out that some users were editing malevolently the client storage to view hidden functionalities of our application.
Even if it’s not a best practice to rely on exposed data as WebStorage for these cases, we didn’t have the time for a refactor — so we decided to encrypt the values making them uneditable and unreadable.
It’s possible to edit local and session storage using any web browser developer tools:
An HTML text area field with syntax highlighting, in which changes are streamed immediately to all connected clients.
The ingredients for the recipe are really cheap: we need a total of 300 lines of JS code, 40 lines of HTML, a sprinkle of 100 CSS lines; bake with npm, and here is the result:
FAANG companies ( Facebook, Amazon, Apple, Netflix, and Google) use tools like the one above (which I called “Direct Code”, not so original I know) while interviewing candidates.
There are lots of already made applications that do the same thing; I decided to build one on my own to understand what are the difficult tasks and issues at play while developing something like this.
…
In the latest release, a terrible bug was included. Lots of precious user information was lost. With Kibana we recovered everything.
Step 1) 😎 Deploy a cool new feature
Step 2) 😱 Panic after 4 days when someone tells you that the new code impacted another piece of the application, causing the override with nulls of several fields in the user table
Step 4) 💾 Recover some data from a past database dump
Step 5) 😱 Panic AGAIN when you notice that 6k user’s row are still missing data
Step 6) 🔎 Discover that using Kibana luckily you can manually recover user information written on Log
Step 7) 😱 Panic SOME MORE when you think that you have to do this…
I’ve come to know lately that the IMG tag has 3 attributes that if set correctly can greatly improve the loading time of a web page. Check them out!
This article is a summary of the article by smashing magazine, with focus on what I think are the most important features therein listed.
1- Lazy Loading
With this simple attribute on the IMG tag, clients will load the image when specified, eagerly or lazily.
<img src="image.jpg"
alt="Description of the image"
loading="lazy" / "eager"
width="500"
height="500">It’s a good strategy to avoid clogging the clients with several requests, loading the critical elements of the…
Gaetano Piazzolla
Tech. leader and passionate developer.
