Сергей Кибиткин - Meet Magento Ukraine - Что вы никогда не сделаете в Magento

Simple text about monitoring

This document discusses using continuous integration with Docker and Ansible. It describes building and deploying microservices across multiple technologies using Docker containers managed by Ansible playbooks. The process involves cloning repositories, building Docker images, testing, pushing images to a private Docker registry, and deploying containers to environments with Ansible. Benefits include easily managing container environments, portability across machines, and isolated workspaces for each service. Challenges addressed are timeouts, freezes, and long build times.

At Ustream the teams developing the streaming technology stack are also responsible for operating it. This means we have our monitoring and alerting in place (including those based on error logs I mentioned above, but many others too) which alert the engineers themselves. I would like to talk about how we made this transition from the traditional setup where the devs did the coding and the sysops did the operation - what lessons we learned, how we convinced the sysop guys to give us permissions and so on

JUST EAT is an online food delivery company based in the UK that processes around 900 orders per minute at peak times. They have embraced DevOps practices to manage their Windows-based ecommerce platform on AWS. They use a microservices architecture with autonomous teams owning their own features and infrastructure. Key aspects of their approach include using persistent chat, real-time monitoring, alerting and logging to enable rapid debugging in production. Their culture emphasizes that teams are responsible for operating the features they build. They are continually working to improve test coverage and confidence while publishing more tools as open source software.

Lean has a central place in DevOps - it's part of CALMS. And Lean is wider and broader than DevOps. And if we compare them, they reinforce each other.

Slides de la présentation DevOps - Retour d'expérience, au MarsJug le 29 Juin 2011

Прошло время, когда DevOps не был еще модным, началось время карго-культов и безбашенных внедрений. В докладе я расскажу про основные ошибки перехода компании к DevOps из моей практики, покажу как не надо использовать инструменты и как не надо организовывать команды, а также многое другое.

This document describes how a company achieved continuous delivery of software through breaking down bottlenecks, automating processes, and establishing a feature pipeline. The key steps included forming feature teams, deploying features to isolated environments, implementing automated testing and deployment, and removing dependencies on operations for releases. This enabled the goals of lower risk, faster feedback, and releasing multiple times per day while maintaining quality. Ongoing work includes further automating infrastructure configuration and deployments.

The document discusses improving development processes with DevOps practices. It describes current issues like a lack of communication between development and operations teams and differences between development and production environments. It evaluates project maturity levels and suggests organizational changes like shared success metrics for teams. The document recommends implementing infrastructure as code, automating testing, and using a delivery pipeline to improve quality, repeatability and reduce risks. Adopting DevOps practices and tools can help align development and production environments.

#kyiv_dgtd

Development with Apache ISIS

-

Применение рекомендационных систем на основе ML в сфере недвижимости, на примере проектов Homsters.com

с

How to identify what’s causing delays on your website, and what tools to use to identify them? How to use caching to reduce the number of requests to the server and speed up page loading? How to use asynchronous requests to reduce page load times and ensure faster and more efficient data exchange between client and server?

f

Explaining the Best Practices of Magento API Design. Performed by Igor Miniailo at Khmelnytskyi Magento Meetup.

Best Practices in Magento 2 Development using MSI project as an example by Valeriy Nayda at Khmelnytskyi Magento Meetup.

Discovering ways to handle development environments that would make Magento development more productive and efficient. Khmelnytskyi Magento Meetup

This document summarizes the results of benchmark tests performed on a Magento 2 site to evaluate performance in different environments. It shows loading times for various site operations like homepage load, category pages, product pages, search and account pages. Tests were run with standard and increased product/customer counts, different caching configurations, database engines and PHP versions. Loading times generally increased as product/customer volumes grew but were improved by adding Redis caching, database replication and upgrading to PHP 7.

Atwix has transitioned to being a distributed company over the past year. It grew from 15 employees working in one physical office and one person remotely, to over 20 employees working across two physical offices and three people remotely. The company now spans four time zones. A distributed company is defined as a group of individuals who work across time, space, and organizational boundaries connected through communication technology. Some of the key aspects of building a distributed company that were discussed include prioritizing communication, tracking performance metrics, addressing challenges of different time zones and locations, and emphasizing the benefits like increased productivity and employee satisfaction.

The document discusses pricing in Magento 2. It covers the different types of prices that can be implemented including regular price, sale price, taxes, discounts. It also describes how pricing is organized through entities and templates to make it flexible and customizable. Code examples are provided to demonstrate how pricing is calculated and displayed for products.

The document discusses Varnish Cache and its usage for caching content and improving performance in Magento. It describes how Varnish works as a frontend caching proxy and how it can be used to cache pages and parts of pages in Magento. It also discusses how to make cache dynamic and flush pages based on products or categories using the EcomDev_Varnish module.

This document discusses data consistency challenges that development teams face when working on complex enterprise projects using Magento. It outlines three main problems: how to store and share data changes between developers, how to migrate data changes between application instances, and how to bind code revisions to application data. The document evaluates different approaches like shared databases and migration scripts, and recommends best practices for using migrations like creating a global package and writing custom import/export APIs to manage complex application data. The overall goal is to establish a development center that can reliably build and deploy applications with consistent data.

This document provides an overview of Magento 2 including its goals, release approach, modernized technical stack, improved performance and scalability, streamlined customizations, easier installation and upgrades, and high code quality and testing standards. The key goals of Magento 2 are to use a modern technical stack, improve performance and scalability, streamline customizations, simplify external integrations, and make installation and upgrades easier.

Александр Каранда - Meet Magento Ukraine - Реальность нереальных вещей

Антон Капля - Meet Magento Ukraine - Кодогенератор в Magento

This document discusses migrating an online store from another platform to Magento. It provides reasons for migrating such as limited functionality and small communities in other platforms. Popular migrations to Magento include OpenCart, osCommerce and VirtueMart. The document outlines important steps for a successful migration including analyzing the source store, testing the data migration, updating Magento, and final data migration. It emphasizes the importance of planning the migration and testing all aspects of the new store.

Артем Кузнецов - Meet Magento Ukraine - инструменты для отдела поддержки, опыт aheadWorks

Александр Стельмах - Meet Magento Ukraine - Прибыльная e-mail рассылка за 5 шагов

Владимир Галика - Meet Magento Ukraine - Чудесный Новый Мир – почему продвижение в интернете не такое как раньше?