I've seen a lot of Perl applications. I see a lot of misunderstandings around architectural patterns. 99% of Perl tutorials do not cover this topic and limited to "hello world" apps. How to build a really large application? What to choose Monolith or Microservices? How to think about architectural layers? How does GraphQL influence my architecture? I will answer all of these questions.

We start developing a project, we have to write a front-end and a back-end. How can we do this effectively? Will 12 factors help us? What about front-end development? How to use containerization correctly? How do I work with git branches? How to work with configs? What about the logs? Scaling? A million questions. I will tell you how we approach all this, what tools we use, what rakes we have stepped on.

How to develop NodeJS apps effectively? I will tell you all details and share my personal experience on the whole process: from the very start and up to the production stage. You will also learn more about Docker, SDLC and 12 Factor App.

You have complex mathematical models (millions of cells, hundreds thousand of formulas) in Excel. And you need to run it browser and mobile without excel. I will talk about how we created our own spreadsheet engine compatible with MS Excel which allows us to run any Excel model without Excel. We will talk about architecture, algorithms, JavaScript performance optimization.

How to develop NodeJS apps effectively? I will tell you all details and share my personal experience on the whole process: from the very start and up to the production stage. You will also learn more about Docker, SDLC and 12 Factor App.

I've already talked about the working architecture of Web applications, but this is only part of the puzzle of effective development. This time I will show all details and share our personal experience on the whole process: from the very start and up to the production stage. I'll tell you how we approach the ideas of the "12 Factor App", how we use Docker, discuss environment deployment, security, testing, SDLC. Real-life experiences often differ from theory, so I always try to share what works in practice.

If you choose a non-classical approach for offline mode for a mobile application then you can finish with Redux on a server, event sourcing and code reuse between mobile, frontend and backend parts of your application.

You have complex mathematical models (millions of cells, hundreds thousand of formulas) in Excel. And you need to run it browser and mobile without excel. I will talk about creation our own spreadsheet engine compatible with MS Excel which allows us to run any Excel model without Excel. I will talk about Architecture, Algorithms, JavaScript performance optimization.

Areas for discussion: - Frontends frameworks and processes, microfrontends - Integrating FE team with Backend team. Fullstack engineers. Rest vs. Graphql - Interating FE and design teams - FE testing approaches/frameworks. Unit/e2e - Working with Legacy frontend - Frontend CI/CD pipelines - Microfrontends - Isomorphic apps. Crossplatform FE

To be announced

Having 15-year experience in web development, I have tried my hands at dozens of validation libraries but didn’t manage to find the one to handle all my tasks. 5 years ago we decided to create a validator which will better than any other. Now LIVR supports a dozen of programming languages and it is battle tested in hudrends of projects. I will talk about the ideas behind, about architecture, use cases, pros and cons. Will show real examples.

I've seen a lot of NodeJs applications. I see a lot of misunderstandings around architectural patterns. 99% of NodeJS tutorials do not cover this topic and limited to "hello world" apps. How to build a really large application? What to choose Monolith or Microservices? How to think about architectural layers? What is wrong with the majority of JS frameworks? How does GraphQL influence my architecture? I will answer all of these questions.

This will be 6 live hacking demos. We will not do theory, but will see in practice how small and not always obvious errors lead to significant vulnerabilities in your JavaScript application.

We launched more than 60 projects, developed a web application architecture that is suitable for projects of completely different sizes. Here I'll analyze this architecture, will consider the issue of “monolith or microservices”, will show the main architectural errors that developers make.

I will tell you why you need JSON RPC and why I created another library. I'll show non-standard usage scenarios. Also, I'll analyze the architectural patterns that have proven useful and the decisions had to be taken during the development. Moreover, I’ll show what modern JS can offer us for developing libraries.

This will be 8 live demo hacking. We will not analyze the theory, but we will see in practice how small and not always obvious errors lead to global vulnerabilities in your JavaScript application.

I will talk about virtual reality (VR). At what state the technology now, why and how to use it. JavaScript is very popular today it is possible to do almost any time of application with it. And it seems that even VR applications can be build easily with JavaScript and React today. The technology is very yang and it will be great to every JS dev to know about new possibilities.

If you choose a non-classical approach for offline mode for a mobile application then you can finish with Redux on a server, event sourcing and code reuse between mobile, frontend and backend parts of your application.