Frontend Mix - talk about Node.js, scalability and native web
You have a frontend. You have written the site, but now it is asked to build it into your native application. You mix them up and get a seamless transition. You do not understand how this happened, but they will explain it to you.
You have a frontend. You need a BFF, and you choose Node.js. You customize, develop, profile, and get a result. You do not understand what you did, but they will explain it to you.
You have a frontend. You also need free scaling, so you take Node.js and mix it with Comedy. You do not understand how to work with this, but they will explain it to you.
Viktor Isaev clearly shows why the Comedy framework is powerful
Under the cat there are three useful reports about the insides of Node.JS, tools, native web, and also the perfect demo of multithreading in Node.JS with the Comedy framework.
Andrey Melikhov (Yandex.Money)
Node.js in an enterprise - why and how?
Why large companies choose Node.js as BFF. How to prepare Node.js correctly, what tools will be needed for development, profiling and monitoring on production.
Victor Isaev (SAYMON)
Comedy: Actors for flexible scaling Node.js
The report introduces the Comedy framework and the implementation of actors in Node.js. A story about how to scale individual Node.js modules without changing the code and intelligently manage the load. There will be a lot of code and live demo.
Victor once wrote a post about it - there is a text, if it is more convenient for you to read and not watch, and from there you can copy the necessary commands.
Zar Zakharov (Alfa Bank)
The story of how we in the bank JS-services embedded in the native application
Imagine that you have a native application in which you need to embed a JS application. A report on whether WebView should be used for this and whether there are other legitimate ways to sew the native and JS so that no one suspects anything.
4:30 Why show a mobile application, and talking about the frontend
6:30 Frontline developers deliver tasks twice as fast and twice as many as mobile teams
7:00 Two systems need two mobile developers
9:00 Decisions for native development for front-tenders - ionic, nativescript, react narive
12:15 What technologies does Alpha Lab use?
13:20 Why WebView?
14:20 Why is it good to show the site instead of the missing sections of the application
16:00 The first problem - a single design (it is not)
19:50 The second problem is cross-authorization and swelling tokens.
23:08 The third problem - no one thought about optimizing applications
25:40 Acceleration of loading pages from 4.5 to 1.2 seconds. How?
29:30 Download speed depends on the device. Why is it important?
31:17 The fourth problem is about odd debugging.
35:00 What should I choose for native development, if you are a fender?
In December, we will hold a mitap for javista - subscribe to our Habrablog, so as not to miss the reports. And if you live in Petersburg - come and listen live.
And also, please vote in the survey on how you are more comfortable to watch reports on the browser.
')
Source: https://habr.com/ru/post/431920/
All Articles