Andrii Sliusar "Module Architecture of React-Redux Applications"

Aug 17, 20181 like256 views

This document discusses module architecture for React-Redux applications. It recommends splitting an application into semantically named modules to improve development speed, scalability, and reduced maintenance costs. The modularity level depends on the application scale, with everything identifiable as a separate component separated. Minimal connectivity between modules ensures the architecture remains scalable and readable. Business logic and data models should be extracted and organized by domain. Selectors wire components to the state model in a clear way. Actions are standardized between modules. A modular architecture has pros like scalability and reduced costs, and a potential con of increased number of files/folders.

www.luxoft.com
Andrii Sliusar
Module Architecture
of React-Redux
Applications

www.luxoft.com
What is “Architecture”?
• Architecture - a fundamental agreement and
solutions.
• Architecture - something important.
• Architecture is difficult to change.
• Architecture must be reused.

www.luxoft.com
Why do we need module architecture?
Module architecture is the type of architecture where an application is semantically split
on components.
For what?
• Development speed
• Scaling
• Reduced maintenance costs
• Decrease the input threshold

www.luxoft.com
How to ensure the necessary modularity?
The modularity level depends on the scale of the application.
Everything that can be identified as a separate component / project should be separated.
What should we split?
• Main Components
• Data model
• Business logic

www.luxoft.com
The connectivity problem of React-Redux architecture?
In order for the project to be scalable and readable, it is necessary to ensure minimal
connectivity between modules.

www.luxoft.com
Modular application architecture

www.luxoft.com
Extract business logic and domain

www.luxoft.com
Root folder
The main idea to keep everything as simple as possible on each level of the architecture.
/project
/core
/screens
app.ts

www.luxoft.com
How to organize the architecture of modules?
/screens
/screen1
/actions
/containers
/components
/reducers
/state
index.tsx

www.luxoft.com
What to do with styles?
• Styles are in one folder with a component
• SASS is good, but JS-based styles have more option
• Create themes from the very beginning

www.luxoft.com
Algorithm for creating a React component
1. Create a component (const or class)
2. Add styles in the same folder
3. Create other logic (actions, reducers, ...)
If it becomes more complex
4. Move props connection to container

www.luxoft.com
Why do we need State model?
• It’s a clear way to work with state
• The same data model can be used in DB
• Build domain model from the beginning

www.luxoft.com
Wire selectors with state
• Everything is sorted by domains
• It clear easier to modify state and
selectors
export default class User{
public name:string;
public getName = (state) =>
state.user.name;
}
const mapStateToProps = (state, props) => ({
name: User.getName(state)
});

$www.luxoft.com What to do with actions? • They must be standardized • The same const between modules, but different values • They can be processed inside different modules enum ACTION_TYPE { UPDATE_NAME = UPDATE_USER_NAME' } export const updateName = (name: string) => ({ type: ACTION_TYPE.UPDATE_NAME, name }) then import {ACTION_TYPE as USER_ACTION_TYPE} from ‘./actions’;$

www.luxoft.com
Pros and Cons of Modular architecture
Pros:
• Scaling
• Reduced maintenance costs
• Decrease the input threshold
Cons:
• Amount of folders/files

How to: - Design a clean domain model - Model your application's use cases as application services - Connect those well-designed layers to the world outside Protecting your high quality domain model can be accomplished by applying a so-called ports & adapters or hexagonal architecture. Some of the keywords for this talk: aggregate design, domain events, application services, commands, queries and events, layered architecture, ports & adapters, hexagonal architecture.

Advanced Application Architecture Symfony Live Berlin 2018Matthias Noback

This document discusses advanced application architecture, specifically layers, ports, and adapters. It introduces layered architecture as a way to define coupling and cohesion in a codebase. The layers separate domains into infrastructure, application, and domain layers with dependencies only allowed in one direction from higher to lower layers. Ports define interfaces that layers can depend on while adapters implement ports, allowing for decoupling and replacement of components. The document also discusses testing at the unit, integration, acceptance, and system levels to verify the architecture.

Advanced application architectureMatthias Noback

In this workshop we'll take a slice of a pretty standard PHP project and gradually work our way towards an application that has a better architecture. "Better" meaning that: It will be easy to find out what the uses cases of the application are ("screaming architecture") It will be easy to find a place for every piece of the application ("layers") It will be easy to find out how users and other systems can interact with it ("ports & adapters") It will be easy to provide tests and automated acceptance criteria for it ("the testing pyramid") I'm sure you would like your project to have these properties! I'll show you all the little steps that will help you transform your application to this new level.

4. introduction to Asp.Net MVC - Part IIRohit Rao

This document provides an overview of key concepts in ASP.NET MVC including application folders, configuration files, the MVC pipeline, routing, and action method return types. It describes folders for views, controllers, models, scripts, images and more. Configuration files like BundleConfig, FilterConfig and RouteConfig are explained. The MVC request pipeline of routing, controller selection, model binding and view rendering is outlined. Routing and route parameters are also summarized. Finally, different action method return types such as ViewResult, JSONResult and ContentResult are introduced.

Advanced web application architecture - TalkMatthias Noback

This document discusses web application architecture and frameworks. It argues that frameworks should not dictate project structure, and that the code should separate domain logic from infrastructure logic. This allows focusing on the core problem domain without concerning itself with technical details like databases or web requests. It also advocates splitting code into ports that define intentions like persistence, and adapters that provide framework-specific implementations, allowing for independence of the domain logic from any particular framework or technology. This architecture, known as hexagonal or ports and adapters, facilitates testing, replacement of parts, and future-proofing of the application.

Module Architecture of React-Redux ApplicationsAndrii Sliusar

The document discusses module architecture for React-Redux applications. It recommends splitting an application into semantically meaningful modules to improve development speed, scalability, and maintenance. Key aspects of modular architecture include separating components, data models, and business logic into distinct modules. The document provides guidelines for structuring modules and their file organization, implementing Redux state management across modules, and using TypeScript for type safety and interfaces. It also discusses testing modules with Jest and snapshot testing.

Layers, ports and adaptersMatthias Noback

This workshop covers all of the three layers from what is known as a layered architecture: the domain, application and infrastructure layer. Protecting your high quality domain model can be accomplished by applying a so-called ports & adapters or hexagonal architecture. And you'll find out how your application's design really starts to flourish when you use CQRS with Event Sourcing. Some of the keywords for this workshop: aggregate design, domain events, application services, commands, queries and events, event sourcing, projections, eventual consistency, layered architecture, ports & adapters, hexagonal architecture. What you'll learn from this tutorial: * Design a clean domain model * Model your application's use cases as application services * Connect those well-designed layers to the world outside

Advanced web application architecture - PHP BarcelonaMatthias Noback

This document discusses principles of advanced web application architecture. It recommends separating applications into domain logic and infrastructure/framework-specific code by introducing layers. It also recommends defining ports and adapters using a hexagonal/ports and adapters architecture to increase testability and flexibility. This allows infrastructure/framework code to change without affecting domain logic ports, and makes it easier to keep up with changing frameworks. Sources provided discuss this architecture approach in more detail.

A testing strategy for hexagonal applicationsMatthias Noback

This document discusses a testing strategy for hexagonal applications that focuses on testing units in isolation like domain logic and use cases without infrastructure dependencies. It advocates for unit tests of application services, integration tests of port adapters against real databases/services, and system tests of the full deployable application to build testing confidence from the unit to system level. The key aspects of hexagonal architecture that enable this are isolation of domain from infrastructure through ports/adapters and explicit definition of use cases as primary interaction points.

Salesforce lwc development workshops session #4Rahul Gawale

linkerd: The Cloud Native Service MeshDario Simonetti

This document discusses linkerd, an open source service mesh for microservices. It summarizes that a service mesh handles communication between microservices by providing features like load balancing, failure recovery, and observability. Linkerd's approach uses lightweight proxies and integrates with service discovery and control plane tools, providing reliability, security and management of microservices. Potential downsides of a service mesh discussed are memory usage and latency overhead.

JEE session 1Smita B Kumar

Microservices with spring bootMesut Can Gurle

This document discusses microservices architecture and how it compares to monolithic architecture. It notes some advantages of microservices such as independent scalability, fault isolation and faster deployments. However, microservices also introduce more operational complexity. The document recommends Spring Boot as a solution for building microservices due to its features like embedded servers, auto-configuration and production-ready environments without XML configuration. It also describes Spring Boot Actuator which adds monitoring endpoints.

Hierarchical architecturebrigeit

This document discusses four types of hierarchical architecture: main-subroutine architecture, master-slave architecture, layered architecture, and virtual architecture. Main-subroutine architecture reuses subroutines that are developed independently and passed data through parameters. Master-slave architecture supports fault tolerance through slaves providing replicated services to the master. Layered architecture decomposes a system into layers with defined responsibilities and interfaces between layers. Virtual architecture builds upon an existing system to provide virtual abstraction and portability.

Salesforce lwc development workshops session #3Rahul Gawale

Building Autonomous ServicesMatthias Noback

This document discusses building autonomous microservices and provides assignments to practice designing services that are autonomous and event-driven. It introduces a simplified e-commerce domain with Catalog, Purchase, Sales, and Stock services and assigns tasks to modify the services to be more autonomous by subscribing to each other's events, updating internal state, and responding without direct communication. The assignments introduce concepts like process managers, event conversion, and using the reservation pattern to avoid concurrency issues. Questions are also provided throughout to help think through architectural challenges.

Service abstractions - Part 1: QueriesMatthias Noback

1) The document discusses creating an abstraction for querying external systems and APIs to make the code more testable and resilient to changes. 2) It proposes defining an interface for the "question" being asked and a class for the "answer", with an implementation that handles the actual request. 3) This abstraction separates the application logic from infrastructure details, allowing the tests to focus on the domain and easing test setup by using test doubles instead of real external dependencies.

(ATS6-DEV04) Building Web MashUp applications that include Accelrys Applicati...BIOVIA

One of the biggest challenges in most corporate environments is providing a way for users to access all the data they need, usually stored in multiple disparate locations, from one interface that they are comfortable with. As web applications have become more popular, RESTful APIs have emerged as the preffered web service format in recent years. Many Accelrys applications now provide RESTful APIs that allow developers to build mashup applications. This session will explore some of these APIs and how to use them to build a simple application.

(ATS6-APP05) Deploying Contur ELN to large organizationsBIOVIA

Clovaを支える技術機械学習配信基盤のご紹介LINE Corporation

Architecting Single Page ApplicationsGuy Nesher

Joining Data From Different Source: Many options, but Which to See?Safe Software

Flux architectureBadr Zaman [Front End , J2EE ]

Flux is an architecture that complements React and uses unidirectional data flow to manage application state. It has four main components: Actions, a Dispatcher, Stores, and Controller Views. Actions are helper methods that pass data to the Dispatcher. The Dispatcher broadcasts payloads to registered callbacks in Stores, which contain application state and logic. Controller Views are React components that retrieve state from Stores and pass it as props to child components.

Architecture Sustaining LINE Sticker servicesLINE Corporation

This document summarizes the architecture of LINE's Sticker Shop backend server. It discusses how the server has shifted from a monolithic Java application to a microservices architecture with 30 services using technologies like Armeria, Central Dogma, Zipkin, and others. Key aspects covered include client-side load balancing, circuit breakers to avoid cascading failures, distributed tracing with Zipkin, and using Central Dogma for stable feature rollouts in 10 minutes or less.

Give your microservices a bus ride with MassTransitAlexey Zimarev

Microservices architecture is still a hot topic but many do not do it right. Challenges like cross-service dependencies, orchestration and load balancing require more and more bike-shedding instead of concentrating on the business capabilities. Using asynchronous messages, many of technical issues can be solved. Learn how to use advanced messaging patterns in your services. Slides are from a workshop given at Progressive .NET Tutorials 2017. Repository is on Github: https://github.com/alexeyzimarev/ProgNet2017.MassTransit

AvalancheProject2012fishetra

This document discusses Avalanche, a workflow development tool. It includes definitions of key concepts like blocks, connections, and workflows. It describes the workbench interface for designing workflows visually and the backend framework that executes workflows. The framework uses Celery for asynchronous task handling and MongoDB for storage. Common algorithms like statistics, set operations, clustering, and outlier detection are supported. Technologies used include Django, jQuery, Bootstrap, Celery, MongoDB, and machine learning libraries. Challenges included browser compatibility, integration of technologies, and complexity of algorithms and Celery.

Cody_Zeng_HPE_Intern_PosterCody Zeng

The document summarizes the development of a new parser tool called the FlexConnector Wizard that improves upon existing logfile parsing methods. It provides an easy to use interface for users to parse logfiles into a Common Event Format readable by ArcSight software. The tool allows users to save and reuse parsing rules, offers a more intuitive layout than existing regex-based tools, and includes features like token filtering testing and import/export functionality. The document also outlines the developer's contributions, including token filtering logic and base regex tokenization, and explains some key terminology used in logfile parsing.

Software architecture, Patterns for ScaleiGbanam

React.js at CortexGeoff Harcourt

A Model-Driven, Component Generation Approach for the Web of ThingsAndreas Ruppen

The Internet of Things took its first steps at the Auto ID Center. Since then, it has evolved to integrate smart devices (sensors and actuators) in pervasive systems able to sense the environment or to act on it. Finally, the adoption of HTTP as a fully-fledged application protocol for the Internet of Things led to the Web of Things. Yet, this is not sufficient to guarantee interoperable, reusable and deployable smart devices and avoid a “things crisis”. Therefore, we investigated how the situation can be enhanced by adopting a Model Driven Architecture for the Web of Things. Its core elements are a meta-model and specialized tools turning instances of the meta-model into executable code (skeletons). With the help of this meta-model we were able to build models to simultaneously take care of the physical and virtual aspects of smart devices as well as of an architecture for events. Compiled into code, these models become components. Since the emphasis is the reusability, the model compilers take special care to divide the Entity of Interest into smaller, reusable parts, forming the building blocks of the Web of Things. Furthermore, the combination of the meta-model and its associated tools provide a methodology guiding the developer throughout the process.

More Related Content

What's hot (20)

A testing strategy for hexagonal applicationsMatthias Noback

Salesforce lwc development workshops session #4Rahul Gawale

linkerd: The Cloud Native Service MeshDario Simonetti

JEE session 1Smita B Kumar

Microservices with spring bootMesut Can Gurle

Hierarchical architecturebrigeit

Salesforce lwc development workshops session #3Rahul Gawale

Building Autonomous ServicesMatthias Noback

Service abstractions - Part 1: QueriesMatthias Noback

(ATS6-DEV04) Building Web MashUp applications that include Accelrys Applicati...BIOVIA

(ATS6-APP05) Deploying Contur ELN to large organizationsBIOVIA

Clovaを支える技術機械学習配信基盤のご紹介LINE Corporation

Architecting Single Page ApplicationsGuy Nesher

Joining Data From Different Source: Many options, but Which to See?Safe Software

Flux architectureBadr Zaman [Front End , J2EE ]

Architecture Sustaining LINE Sticker servicesLINE Corporation

Give your microservices a bus ride with MassTransitAlexey Zimarev

AvalancheProject2012fishetra

Cody_Zeng_HPE_Intern_PosterCody Zeng

Software architecture, Patterns for ScaleiGbanam

A testing strategy for hexagonal applicationsMatthias Noback

Salesforce lwc development workshops session #4Rahul Gawale

linkerd: The Cloud Native Service MeshDario Simonetti

JEE session 1Smita B Kumar

Microservices with spring bootMesut Can Gurle

Hierarchical architecturebrigeit

Salesforce lwc development workshops session #3Rahul Gawale

Building Autonomous ServicesMatthias Noback

Service abstractions - Part 1: QueriesMatthias Noback

(ATS6-DEV04) Building Web MashUp applications that include Accelrys Applicati...BIOVIA

(ATS6-APP05) Deploying Contur ELN to large organizationsBIOVIA

Clovaを支える技術機械学習配信基盤のご紹介LINE Corporation

Architecting Single Page ApplicationsGuy Nesher

Joining Data From Different Source: Many options, but Which to See?Safe Software

Flux architectureBadr Zaman [Front End , J2EE ]

Architecture Sustaining LINE Sticker servicesLINE Corporation

Give your microservices a bus ride with MassTransitAlexey Zimarev

AvalancheProject2012fishetra

Cody_Zeng_HPE_Intern_PosterCody Zeng

Software architecture, Patterns for ScaleiGbanam

Similar to Andrii Sliusar "Module Architecture of React-Redux Applications" (20)

React.js at CortexGeoff Harcourt

A Model-Driven, Component Generation Approach for the Web of ThingsAndreas Ruppen

Thesis Defence: A Model Driven Architecture for the Web of ThingsAndreas Ruppen

The document proposes an extension to the Web of Things called xWoT that uses a model-driven component approach. It introduces the vision of xWoT which is to treat algorithms and events as first-class citizens. The document then describes the background on software components and meta-modeling. It presents the xWoT approach of defining reusable components as building blocks. It also details the xWoT meta-model and how a model compiler can generate code skeletons from xWoT models. Finally, it outlines a three step methodology for entity modeling, data modeling, and implementation.

.net Based Component Technologiesprakashk453625

The document discusses various .NET component technologies including Component Object Model (COM), Distributed COM (DCOM), ActiveX controls, and .NET components. It also covers related concepts like assemblies, AppDomains, contexts, and reflection. COM is an interface standard introduced by Microsoft in 1993 to enable interprocess communication and dynamic object creation. DCOM extends COM to enable communication across networked computers. ActiveX controls allow embedding functionality in web pages. .NET components provide a programmable interface accessed by client applications.

Architectural peripherals of react by Vadym ZhiltsovLohika_Odessa_TechTalks

Тема доклада «React и его архитектурная периферия» React - мощнейшая библиотека для создания технических интерфейсов, но порой одного реакта не достаточно для полноценной и гибкой разработки. Мы будем обсуждать и сравнивать разные подходы для разработки современных React приложений. В программе: React&Redux, React&Meteor, React&Relay, React&MobX, React&PRPL

Clean sw 3_architectureAngelLuisBlasco

The document discusses architectural principles and patterns for software design, including: 1. Leaving implementation details open as long as possible to maximize optionality in design decisions. 2. Ways to decouple layers include controlling dependencies between code modules, communicating via function calls within a process or inter-process communication between processes. 3. Common architectural patterns discussed include layers, hexagonal architecture, and the clean architecture pattern of only allowing dependencies to point inward.

AngularJSYogesh L

AngularJS is a framework for building client-side web applications. It uses HTML as the template language and extends HTML attributes with directives. AngularJS applications are made up of modules that contain controllers, services, and directives to add dynamic behavior. Data binding in Angular updates the view automatically when the model changes. Key features include directives, two-way data binding, MVC pattern, dependency injection and routing.

Reactjs notes.pptx for web development- tutorial and theoryjobinThomas54

GDG Workshop on React (By Aakanksha Rai)gdgoncampuslncts

Google Developer Group LNCTS: Empowering Innovation and Collaboration Google Developer Group LNCTS is a dynamic and thriving community uniting tech enthusiasts, developers, and innovators from LNCT Group of Colleges, Bhopal. Our mission is to foster a collaborative environment where learning, creativity, and innovation come to life. We strive to bridge the gap between students and cutting-edge technology through a diverse range of engaging activities. From hands-on workshops and hackathons to thought-provoking speaker sessions, our events are designed to provide practical skills, inspire creative problem-solving, and encourage collaboration that leads to impactful projects. At GDG LNCTS, we believe in the power of community-driven growth. By connecting like-minded individuals, we cultivate a culture of shared knowledge and mutual support, empowering students to excel in their technical journeys. Whether you’re looking to sharpen your coding skills, connect with industry experts, or explore the latest advancements in technology, GDG LNCTS offers a platform to learn, grow, and innovate. 🌐 Stay Connected with GDG LNCTS: Instagram: Follow us LinkedIn: Connect with us WhatsApp Community: Join here X: Like our page Join us in shaping the future of technology and making a meaningful impact in the world. Together, let’s innovate, collaborate, and thrive!

Spring - a framework written by developersMarcioSoaresPereira1

Microsoft Entity FrameworkMahmoud Tolba

Microsoft Entity Framework is an object-relational mapper that allows developers to work with relational data as domain-specific objects, and provides automated CRUD operations. It supports various databases and provides a rich query capability through LINQ. Compared to LINQ to SQL, Entity Framework has a full provider model, supports multiple modeling techniques, and continuous support. The Entity Framework architecture includes components like the entity data model, LINQ to Entities, Entity SQL, and ADO.NET data providers. Code First allows defining models and mapping directly through code.

Introduction to react native with reduxMike Melusky

This document provides an introduction and overview of React Native with Redux. It begins with an introduction to React components, props, and state. It then covers building a sample React Native app and advanced concepts like navigation and Redux. The document compares React Native to other native frameworks and provides resources for learning more. It was presented at Philly.NET on March 24, 2018 and discusses topics like React basics, React Native, native navigation solutions, and integrating Redux.

Meteor + ReactTaggart Bowen-Gaddy

Vue vs React In-Depth Comparison of 2 Leading JavaScript FrameworksPixlogix Infotech

React or Vue—which one should you choose? Both are powerful JavaScript frameworks, but they cater to different needs. React is ideal for large-scale applications with high flexibility, while Vue is lightweight and great for quick development. If you're looking for a comparison on performance, scalability, and ease of use, our latest blog breaks it all down! Stay ahead in web development—read now and make the right choice!

Clean architecture with asp.net coreSam Nasr, MCSA, MVP

This document discusses the principles and structure of Clean Architecture for ASP.NET Core applications. It recommends separating an application into projects for the core domain logic, infrastructure implementation, and user interface. The core project defines interfaces that outer projects implement, avoiding direct dependencies. This allows for independence of frameworks, databases, and user interfaces. The document provides examples of project structure and responsibilities, and resources for further learning clean architecture principles.

Pragmatic Monolith-First, easy to decompose, clean architecturePiotr Pelczar

Designing systems architecture corresponding to business needs in long future is like a reading tea leaves. There is no common way to design systems. Making decision to start project with microservices may make refactoring much harder and introduce too much complexity in the infrastructure layer and finally slow down development. However maintaining a monolith is a tough nut to crack. Let’s see how to build a system starting from well organized monolith with well marked technical and business scopes that enables to make a decision in with way it should be decomposed and how to deliver it. Strategic and tactical techniques from Domain-Driven Design and Hexagonal Architecture will be used. I will show you how to monitor accidential complexity using different tools during CI. I invite you if you are interested in building systems with complex business domains.

Learn Entity Framework in a day with Code First, Model First and Database FirstJibran Rasheed Khan

Learn Entity Framework in a day with Code First, Model First and Database First •Introduction to Entity Framework (EF) •Architecture •What’s new! •Different approaches to work with (Code first, Database first and model first) •Choosing right work model •Pictorial Tour to each model •Features & Advantages •Question & Answer for any help and understanding feel free to contact thank you

Super applied in a sitecore migration projectdodoshelu

This document describes using a business process model and ontology for a Sitecore migration project. It discusses key Sitecore concepts like items, templates, fields and presentation components. An ontology is proposed to model Sitecore concepts and help answer competency questions during content creation. Integrating the business process model with SUPER could provide semantic tools and services to help manage the migration, increasing flexibility and reducing costs and time. Potential disadvantages include challenges developing an accurate ontology and hiding complex IT implementation details.

Introduction to ReactJS UI Web Dev .pptxSHAIKIRFAN715544

React JS is a declarative, efficient, and flexible JavaScript library for building reusable UI components. It uses a virtual DOM which works like a lightweight copy of the real DOM to improve performance by only updating what changes. Components are independent and reusable bits of code that serve the same purpose as functions but return HTML. There are two main types of components - functional components which are simple functions, and class components which can maintain their own state and work together.

Unboxing ASP.NET CoreKevin Leung

React.js at CortexGeoff Harcourt

A Model-Driven, Component Generation Approach for the Web of ThingsAndreas Ruppen

Thesis Defence: A Model Driven Architecture for the Web of ThingsAndreas Ruppen

.net Based Component Technologiesprakashk453625

Architectural peripherals of react by Vadym ZhiltsovLohika_Odessa_TechTalks

Clean sw 3_architectureAngelLuisBlasco

AngularJSYogesh L

Reactjs notes.pptx for web development- tutorial and theoryjobinThomas54

GDG Workshop on React (By Aakanksha Rai)gdgoncampuslncts

Spring - a framework written by developersMarcioSoaresPereira1

Microsoft Entity FrameworkMahmoud Tolba

Introduction to react native with reduxMike Melusky

Meteor + ReactTaggart Bowen-Gaddy

Vue vs React In-Depth Comparison of 2 Leading JavaScript FrameworksPixlogix Infotech

Clean architecture with asp.net coreSam Nasr, MCSA, MVP

Pragmatic Monolith-First, easy to decompose, clean architecturePiotr Pelczar

Learn Entity Framework in a day with Code First, Model First and Database FirstJibran Rasheed Khan

Super applied in a sitecore migration projectdodoshelu

Introduction to ReactJS UI Web Dev .pptxSHAIKIRFAN715544

Unboxing ASP.NET CoreKevin Leung

More from LogeekNightUkraine (20)

Face recognition with c++ LogeekNightUkraine

This document discusses facial recognition using OpenCV in C++. It describes using Haar cascades, which is an object detection algorithm, to detect faces in images and video streams. It explains that Haar cascades use Haar-like features such as edges, lines, and changes in intensities to rapidly detect faces. Code examples are provided to load an image, detect faces using a pre-trained cascade model, and draw rectangles around the detected faces. Additional code shows how to perform real-time face detection on video camera streams.

C++20 features LogeekNightUkraine

The document discusses new C++20 features including the spaceship operator, modules, ranges library, concepts, and coroutines. It provides examples of using the spaceship operator for comparison, defining modules and importing/exporting functionality between modules, using views and ranges to lazily filter and transform sequences, and using coroutines with co_await, co_yield, and coroutine handles.

Autonomous driving on your developer pc. technologies, approaches, futureLogeekNightUkraine

This document discusses how to develop autonomous driving algorithms using a simulator on a developer PC. It outlines several autonomous driving algorithms like object detection and trajectory planning. It recommends using an LG simulator within Unity for environment modeling, ROS for data transmission, and Autoware as an algorithm framework. The document provides information on simulating sensor data, controlling vehicles in simulation, and testing autonomous driving algorithms within a simulated environment before using real-world testing.

Orkhan Gasimov "High Performance System Design" LogeekNightUkraine

Vitalii Korzh "Managed Workflows or How to Master Data" LogeekNightUkraine

Yevhen Tatarynov "From POC to High-Performance .NET applications"LogeekNightUkraine

The document discusses optimizing the performance of .NET applications that process large amounts of data. It begins with describing the challenge of applications that take a long time to process files over 1GB in size. It then discusses measuring the application performance, identifying potential issues through profiling tools, and making improvements to reduce execution time and memory usage. Specific optimizations discussed include avoiding redundant Linq operations, optimizing bit manipulation methods to use integer operations instead of floating point, and sorting file names using a more efficient algorithm. Through these changes, execution time was reduced by over 88% and memory usage was reduced by nearly 69%.

Oleksii Kuchuk "Reading gauge values with open cv imgproc"LogeekNightUkraine

This document discusses using OpenCV to read gauge values. It describes using Canny edge detection and Hough transformations to detect lines in an image of a gauge. The Hough transform is applied to the edge detected image to find 11 lines representing the gauge. The inclination and speed values are then calculated from the lines' rho and theta parameters. While OpenCV image processing works well for this, preprocessing must be chosen carefully and detection errors can occur.

Oleksandr Kutsan "Using katai struct to describe the process of working with ...LogeekNightUkraine

Kaitai Struct is an open-source tool that allows parsing binary file formats through a declarative file format. It supports generating parsing code for multiple languages from a single declarative file, avoiding the need to implement parsers separately for each language. The file format describes elements like sequences and enums, and can define custom types. Predefined formats are available, and the tool includes utilities for debugging and visualization. While beneficial for its cross-language support and tools, it has some drawbacks like being implemented in Scala and having version stability issues.

Pavlo Zhdanov "Mastering solid and base principles for software design"LogeekNightUkraine

The document discusses SOLID principles and other principles of software design including single responsibility, open/closed, Liskov substitution, interface segregation, and dependency inversion. It provides definitions and examples of each. The SOLID principles aim to create simple, modular, and understandable code by establishing best practices for class design. Additional design principles discussed ensure reusable, cohesive components with stable dependencies and abstractions.

Serhii Zemlianyi "Error Retries with Exponential Backoff Using RabbitMQ"LogeekNightUkraine

This document discusses different approaches to implementing error retries with exponential backoff when using RabbitMQ. It begins with motivation for the problem and an overview of RabbitMQ terminology. Then it demonstrates three approaches: using pure RabbitMQ configuration with no code; using the Spring AMQP module's ExponentialBackoffPolicy; and using the RabbitMQ Delayed Message Plugin which has some limitations. The document provides code examples and comparisons of the different approaches.

Iurii Antykhovych "Java and performance tools and toys"LogeekNightUkraine

This document discusses various tools and techniques for profiling Java applications to analyze performance, including: - Using profilers like Async Profiler to visualize where time is spent in CPU, memory, and other metrics through flamegraphs and call trees. - Collecting metrics from applications, systems, and services through agents, then viewing them in tools like Grafana to monitor for issues and set alerts. - Profiling production, load tests, and benchmarks to understand real-world performance and correlate results. - Combining profiles from distributed systems through techniques like collecting collapsed profiles then viewing them together. - Other commercial and open source profiling options are also mentioned.

Eugene Bova "Dapr (Distributed Application Runtime) in a Microservices Archit...LogeekNightUkraine

This document provides an introduction to Dapr (Distributed Application Runtime), an open-source project initiated by Microsoft for building distributed applications. It discusses Dapr's architecture, building blocks like service invocation, pub/sub, state management and secrets APIs. It also covers hosting environments, SDKs, performance, pros and cons and deployment in Kubernetes with annotations.

Aleksandr Kutsan "Managing Dependencies in C++"LogeekNightUkraine

The document discusses various approaches for managing dependencies in C++ projects. It covers different types of dependencies like compile-time, compile and runtime, and only runtime dependencies. It then analyzes approaches for handling compile-time dependencies, including storing dependency sources with the project, fetching sources during compilation, fetching pre-built binaries, and relying on pre-installed system dependencies. The document also discusses dependency management challenges for different project types and environments like embedded systems. It advocates for separating dependency management from the build system and recommends using dedicated package managers like Conan or Nix.

Yevhen Tatarynov "My .NET Application Allocates too Much Memory. What Can I Do?"LogeekNightUkraine

The document discusses optimizing a .NET application that was allocating too much memory. The author used various profiling tools to measure the application's memory usage and identify issues. Through 15 iterations of code changes and memory snapshots, they were able to reduce the peak memory load by 30%, total memory usage by 97%, and execution time by 57%. The optimizations included avoiding boxing, reusing objects, using StringBuilder instead of strings, and not allocating memory for unused data.

Alexandr Golyak, Nikolay Chertkov "Automotive Testing vs Test Automatio"LogeekNightUkraine

The document discusses automotive testing versus test automation. It provides an agenda for a meeting covering topics like career paths in automotive testing, test theory, and test environments. The speakers will share specifics and challenges of automotive testing and validation, and discuss test automation frameworks and examples. They aim to answer questions about working in automotive testing, how to enter the field, its future, and automotive testing in Ukraine.

Michal Kordas "Docker: Good, Bad or Both"LogeekNightUkraine

This document discusses Docker in the Java universe. It provides an overview of Docker and containers, how they help solve issues with deploying Java applications across different environments, and some best practices for writing Dockerfiles for Java applications. It discusses how Docker images are built in layers and the benefits this provides. It also demonstrates some simple Java applications built as Docker images and run in containers.

Kolomiyets Dmytro "Dealing with Multiple Caches, When Developing Microservices"LogeekNightUkraine

This document discusses dealing with multiple caches when developing microservices. It identifies several types of caching architectures including embedded, client-server, reverse proxy, and sidecar caching. It notes that caches are used to improve performance, autonomy, availability, and reduce costs. The document also provides examples of how caching could be implemented in a microservices architecture with different services.

Shestakov Illia "The Sandbox Theory"LogeekNightUkraine

The document discusses sandboxes and managing development environments for microservices. It introduces the Carnotzet tool, which uses Docker and Maven to create isolated and reproducible sandboxes for microservice dependencies. Carnotzet packages dependencies as Docker images, uses hierarchical configuration to manage overrides, and provides a Java API and Maven plugin to create and interact with sandboxes. This allows development teams to easily evolve sandboxes and isolate experiments from production environments.

Dmytro Kochergin “Autotest with CYPRESS”LogeekNightUkraine

Cypress is an open source JavaScript testing framework for testing web applications. It allows for running automated tests directly in the browser without any build step required. Some key features of Cypress include time travel debugging, automatic waiting, running tests headlessly on CI, and generating screenshots and videos. The document discusses using Cypress to test an application and some issues faced, such as tests not restarting on file save and emulating a mobile browser. It provides solutions for some problems like uploading files and handling CORS errors. Overall reproducing test data across environments remains an unresolved challenge.

Ivan Dryzhyruk “Ducks Don’t Like Bugs”LogeekNightUkraine

This document discusses software testing techniques and best practices. It covers test design techniques like equivalence partitioning and boundary value analysis. It emphasizes the importance of tests being fast, isolated, repeatable, self-validating, and thorough. The testing pyramid hierarchy of tests is explained. Test-driven development and various test utilities are also outlined. The conclusions emphasize that tests help increase confidence in code, prevent accidental breaks, and ensure documentation remains relevant.