Tag Archives: link

Socks5 proxy for telegram

It’s the easiest one you can install on your VPS server. It’s a docker container. https://github.com/schors/tgdante2 You could use VPN for that but it will send all traffic through your VPN endpoint which is not fast. Socks5 proxy uses much less resources and this one is only applicable for telegram now.

List of resources to prepare for the interview

Mock Interviews interviewing.io (beta), Free Pramp, Free CareerCup, Paid Algorithms Cracking the Code Interview, Book byte by byte, Website and YouTube CS50, YouTube Interview Cake, Website HackerRank, Website LeetCode, Website Operating Systems Operating System Concepts, Book Architecture Design Intro to Architecture and Systems, YouTube Behavioural Intro to Behavioural Interviews, YouTube Original article with explanations: https://medium.freecodecamp.org/software-engineering-interviews-744380f4f2af

What is a Service Mesh? Introductory article from NginX

The original is here — https://www.nginx.com/blog/what-is-a-service-mesh/ Another small introductory article on Istio you can find here. A service mesh is a configurable infrastructure layer for a microservices application. It makes communication between service instances flexible, reliable, and fast. The mesh provides service discovery, load balancing, encryption, authentication and authorization, support for the circuit breaker pattern, and other …

Istio — platform for managing and connecting your microservices. Service mesh

https://istio.io/docs/concepts/what-is-istio/overview.html It’s flexible and modular service mesh made by Google, IBM and Lyft. It is a platform for managing your kubernetes system. It’s responsible traffic management, observability, policy enforcement, service identity and security. It provides features like service discovery, load balancing, A/B experiments, canary deployments, circuit breaking and health checks.

Performance comparison table for javascript frameworks

http://www.stefankrause.net/js-frameworks-benchmark7/table.html Example results are as follows:

Execution context and activation object in details

There are many interesting articles both in Russian and English. You can start with this one — http://dmitrysoshnikov.com/ecmascript/javascript-the-core/#execution-context-stack. In Russian — http://dmitrysoshnikov.com/ecmascript/ru-javascript-the-core/#stek-kontekstov-ispolneniya The short summary Javascript runtime is synchronous and processes Execution Context Stack. It’s bottom Execution Context is global object as everything starts with this. When some function or eval is being called, runtime …

Multiple react applications on one page. Theory

Yes, it can be done. That’s how you render several react apps on one page:

Cool talk on js event loop and call stack

It’s junior-middle level, but animations are nice as well. https://youtu.be/8aGhZQkoFbQ Here’s an article about almost the same but in more details about difference between tasks’ queue (timeouts) and microtasks’ queue (promises and DOM modifications). The main idea is that there are several queues that have different priorities. And microtasks are more important than tasks. https://jakearchibald.com/2015/tasks-microtasks-queues-and-schedules/

React. Benchmarking and optimizing performance

There is a tool called react-addons-perf that should be imported into your project.

import Perf from 'react-addons-perf';

window.Perf = Perf;

import Perf from 'react-addons-perf';

window.Perf = Perf;

After that you can use Perf object in your console. It can tell you about your react performance issues, not including redux. For instance, you can check unnecessary renders or unnecessary change calculations:

Perf.start();
// do whatever you want to measure
Perf.stop();

Perf.printOperations(); // to show DOM manipulations
Perf.printWaisted(); // to show unneeded calculations for components which remained the same afterwards

Perf.start();

// do whatever you want to measure

Perf.stop();

Perf.printOperations(); // to show DOM manipulations

Perf.printWaisted(); // to show unneeded calculations for components which remained the same afterwards

Here’s more on that — https://reactjs.org/docs/perf.html. And …

MVC vs Flux

They are all architecture patterns. M is for model. It stores generic logic for the model like fields and calculations based on the fields like validation and stuff. V is for view. It just renders stuff and passes user interactions (events) to its controller via the controller’s API. C is for controller that ties models …