Housekeeping the platform at scale

Nov 8, 20220 likes58 views

Marktplaats is the largest trading platform in the Netherlands, with 8 million monthly unique visitors and 18.7 million live ads. The document outlines the frontend platform aimed at accelerating product development by providing services, tools, and resources for development teams, emphasizing automation in dependency updates and security fixes. Key takeaways include the importance of aligning technologies across teams, automating updates, and reducing maintenance burdens.

Engineering

About me
Eugene Fidelin
Frontend Architect
at Marktplaats | Adevinta BNL
linkedin.com/in/eugef
medium.com/@EugeneFidelin

New ads per day
350K
Visits per day
6.5M
Hits per day
300-400M
Connected ads per day
100K
Marktplaats: Facts & Figures
With over 8 million unique visitors monthly and 18.7 million live ads at any given
time, Marktplaats is the largest trading platform in the Netherlands.

Vision
Product development teams at Marktplaats focus all their efforts on building
the product and nothing else.
Making it happen
We accelerate product development by providing the Frontend Platform:
set of services, tools, components and other resources to enable FE engineers to
effectively deliver secure, reliable and efficient software.

Used by development teams
8
to build services and libraries
40
60
15
that generate production releases per day
Frontend platform adoption

Team autonomy vs dev efficiency
Level of team autonomy
reusability reinventing the wheel
consistency fragmentation
dev support maintenance burden

Frontend Golden path
● Stack: most important technologies that are aligned
and shared across the teams.
● Information support: ADRs, TechRadar, best-practices,
Slack channel, PR reviews.
● Governance: Developed in collaboration with teams,
owned by the Platform org.
Teams can deviate but they have to pay extra costs!
Golden path -
opinionated and
supported path to
build something

Golden path stack
Client-side
● React setup
● Design System
● Translations
Server-side
● Express.js
middlewares
● React SSR
● API clients
● Observability tools
Build and deploy
● Webpack conﬁg
● TypeScript
● Eslint/Prettier
● Jest
● Node.js Docker

Keep teams up-to-date
● Dashboard with live overview of all services, inventory of
outdated dependencies on production.
● Automated dependency updates by Renovate.
● Timely security updates by Snyk.
● Batch ﬁxes and improvements with codemods.
● Information support and developer assistance.

Automated dependency updates
● 24/7 updates for internal NPM packages and Docker
images.
● Bi-weekly updates for trusted 3rd-party NPM packages.
● Minor and patch updates are auto-merged when build is
green. PRs are only created if build fails.
● Major updates always result in a PR and won't be
auto-merged.
● NCU dashboard has overview of pending Renovate PRs
~6 hours to propagate new version to all the services and libraries.

Timely security updates
● Regular updates to ﬁx vulnerabilities in open source
dependencies (direct and transitive).
● All updates always result in a PRs and are not auto-merged.
● For feature PRs run security check for newly added
dependencies.

Batch code changes
● Install/update/remove dependency(s).
● Apply custom jscodeshift codemod.
● Run Putout code transformations to ﬁx code smells.
● Apply Prettier to format the source code.
● Run tests and update Jest snapshots.
● Create PR and optionally auto-merge it.
Codemod - write a
code to rewrite
your code.

Information support
● ADRs - capture an important architectural decisions
made along with its context and consequences.
● Tech Radar - list of Techniques, Tools, Platforms,
Language & frameworks we observe: currently used,
tested, under research or put on hold.
● Dev assistance - Slack channel to provide immediate
help and support. PR reviews to give feedback and
guidance.

Key takeaways
1. Align
the most important
technologies across the
teams to deﬁne the
Golden path.
2. Automate
dependency updates,
security ﬁxes and roll
out of the platform
improvements.
3. Accelerate
the teams by reducing
the maintenance
burden and providing
support.

Credits
Articles:
● How We Use Golden Paths to Solve Fragmentation in Our Software Ecosystem
● Software Sprawl, The Golden Path, and Scaling Teams With Agency
Images:
● Cover image by pikisuperstar on Freepik
● Robot images by macrovector on Freepik

The document discusses the challenges and strategies involved in managing large scale frontend web applications, particularly in high-traffic environments like e-commerce sites. It highlights the complexity of JavaScript architecture, the importance of build tools, and the roles of various teams such as architects, guides, gatekeepers, and lifeguards in ensuring successful development and deployment. Key recommendations include establishing strong conventions, automating quality checks, and effectively logging and monitoring code execution.

Node.js Web Apps @ ebay scaleDmytro Semenov

��

The document outlines eBay's transition to Node.js for web applications, highlighting the journey from various programming languages to the current state, where Node.js supports 200 applications handling 1 billion requests daily. It discusses the benefits of modular architecture, improved startup times, and the development of a vibrant internal community contributing to a shared knowledge base. The document also covers performance optimizations, deployment strategies, and future directions, including plans for platform microservices and enhanced resilience.

CONTINUOUS DELIVERY EN BANQUETREEPTIK

��

This document discusses implementing continuous delivery practices at a bank. It outlines some of the challenges with legacy banking systems including old code, lack of agile processes, and heavy regulation. It then proposes adopting agile, software craftsmanship, and DevOps practices to automate releases, improve quality, and speed up delivery. Key aspects of the proposed continuous delivery program include adopting Scrum, test-driven development, infrastructure as code, automated deployments, and a cloud platform. The results were transforming over 400 applications to reduce time to market from months to weeks and deployment time from months to minutes.

Agave Overview for Candidates [SHARED].pptxLaurenLee185158

��

Agave is a rapidly growing startup specializing in modernizing the construction industry through API integrations, addressing the inefficiencies of outdated software systems. Founded in October 2021 and currently with 11 employees, it has secured over 140 customers and reached a cash-flow positive status, with consistent revenue growth. The company's mission is to facilitate the digitization of construction, enhancing productivity and profitability for contractors by automating work and synchronizing data between various systems.

Advanced Full Stack Development: Scaling, Deployment, and Maintenancesaniakhan8105

��

The document discusses advanced full stack development, emphasizing the importance of scaling, deployment, and maintenance in web applications. It highlights key components such as front-end and back-end technologies, various scaling techniques, and the significance of continuous integration and deployment. Additionally, it covers maintenance practices essential for ensuring application performance and security over time.

Architecting Developer Experience: Fintech and Banking Devportal Case StudiesPronovix

��

This document discusses best practices for architecting developer experience (DX) through developer portals. It outlines the developer journey in 6 stages: discover/research, evaluate, get started, develop & troubleshoot, celebrate, and maintain. For each stage, it provides examples of how banking and fintech portals can support developers through features like API catalogs, documentation, tutorials, support options, feedback mechanisms, and release notes. The goal is to reduce API friction and engage developers at each stage of use to improve overall experience.

APIdays Paris - Architecting Developer eXperience: Banking & FinTech Develope...apidays

��

The document discusses the importance of developer experience (DX) in banking and fintech through the use of effective developer portals. It outlines the stages of a developer's journey, from discovery to maintenance, emphasizing the need for resources, support, and engagement at each stage to reduce API friction. Case studies and best practices are provided to inspire improvements in developer portals to enhance user experience and increase API utilization.

Architecting DX: Banking & FinTech Developer Portals Case Studies (APIDays Pa...Kathleen De Roo

��

The document discusses the importance of developer experience (DX) in banking and fintech through effective developer portals that facilitate API usage and foster user engagement. It outlines the stages of a developer's journey and how to address their needs at each stage, emphasizing the integration of trust signals and self-service support. Case studies and best practices are provided to illustrate how organizations can enhance DX and reduce API friction.

"Platform Engineering in practice — Why and How to start", Serg Hospodarets Fwdays

��

The document discusses the implementation of platform engineering to address various challenges faced by a large organization, including cost-effective software development, reduced time to market, and improved security. It outlines the adoption of DevOps principles and team topologies through tooling demonstrations and strategies to foster a culture of internal customer support and collaboration. Notable achievements include a significant decrease in the time for app deployment and improved operational metrics.

Simplified DevOps Bliss -with OpenAI APIVictorSzoltysek

��

Victor Szoltysek outlines a new approach to simplify DevOps by emphasizing speed, simplicity, and self-serve principles. The document suggests various strategies, such as using GitHub actions for CI/CD, proactive monitoring, automated code quality checks, and leveraging AI for problem resolution to enhance operational efficiency. It advocates for adopting modern practices like trunk-based development and blue-green deployments to foster agility and minimize downtime.

TejaSoft Code Audit Case StudiesRaja Nagendra Kumar

��

Tejasoft, a Bangalore-based company, specializes in technical debt elimination and software optimization, particularly for Java code, boasting extensive experience and a track record of saving clients millions in engineering costs. Their engagement model focuses on direct collaboration with clients to enhance code quality and operational efficiency while providing engineering services such as code refactoring, scalability engineering, and team building. The company has successfully reduced code size and improved performance for notable clients like NDS, IRCTC, and Logix, demonstrating their expertise in transforming complex software systems.

Releasing the Monolith On a Daily BasisAtlassian

��

Vincent Kok, a Development Manager at Atlassian, discusses the challenges and solutions in transitioning from a monolithic architecture to a microservices approach. Key issues addressed include complexity, ownership, testing, and release processes, alongside strategies to improve team culture and efficiency. The focus is on creating a sustainable development environment that fosters quick wins and data-driven decision-making.

Europace's journey to InnerSourceEnrico Hartung

��

The document discusses the implementation of GitHub Enterprise in a network-centric organization focusing on the credit, real estate, and insurance industries. It covers various aspects such as support structures, team collaboration, repository management, and decision-making processes in a multi-team environment. Recommendations include improving documentation, establishing clear guidelines for GitHub usage, and ensuring effective integration of security measures.

YTD Video Downloader Pro Crack [Latest 2025]rpari1867

��

Distributed systems: design, principles and experienciesAndrés Pérez Gil

��

Talk and tutorial as part of Distributed App Developments subject from an official University of Alicante Master degree in development applications and web services. In this session I've shared some historic background how to build cloud native applications and its scalability to create distributed systems, based on industry trends and also with some tips and tricks based on my personal experience. It is recommended to take a look on tutorial attached at the end of the presentation to have an example with a detailed explanation about a distributed app: https://github.com/khnumdev/dist-app-tutorial

ScaleOut your team - Building a technology team for scale in a DevOps cultureAgileSparks

��

This document discusses strategies for scaling a technology team to support high growth and large traffic volumes. Key points include operating distributed infrastructure across multiple data centers; relying on automation, configuration as code, and open source tools; emphasizing continuous deployment with short release cycles; monitoring all systems; and fostering a collaborative culture through open communication and learning opportunities. The team described supports over 25 billion page views per month with over 8 billion recommendations daily across 550 million users globally.

Scaling Autonomy in a FinTech Unicorn - WeAreDevelopers 2019Alvar Lumberg

��

The document discusses scaling autonomy in the fintech company TransferWise, highlighting its growth and the evolution of its engineering and product management practices. Key tenets of autonomy emphasize responsibility and ownership among engineers, the need for efficient team structures, and strong leadership to ensure project management and technological governance. The presentation also addresses challenges such as the need for clear priorities, effective ownership, and centralized support for cross-team initiatives.

An evening with... DevOpsArkhotech

��

The document discusses the principles and benefits of DevOps, highlighting its emphasis on collaboration among development, QA, and operations teams to improve application delivery speed and quality. It compares practices from major tech companies like Amazon, Google, and Facebook, showcasing their automation and continuous deployment strategies. The document concludes with critical factors for adopting DevOps effectively, including transformational leadership, automation, and a culture that fosters collaboration and responsibility.

Slaying Monoliths with Node and DockerYunong Xiao

��

The document discusses the evolution of Netflix's API architecture from a monolithic Java web server to a microservices architecture using Node.js and containers. It describes how the monolith led to scalability and developer productivity issues. The new architecture uses Node.js scripts in containers with process isolation for improved scalability, availability, and developer experience through rapid local development and debugging. Key aspects of the new architecture include service routing, versioning, operational insights, and container management.

Shitlist-driven development and other tricks for working on large codebasesFlorian Weingarten

��

The document addresses productivity challenges at Shopify's scale, identifying issues with deployment speed, coordination among multiple contributors, and unreliable tests. Solutions include implementing small, fast automated deployments, adopting shitlist-driven development to manage code changes, and improving test reliability through tracking and alerting mechanisms. Key recommendations emphasize the need for automation to alleviate bottlenecks caused by human involvement in the deployment process.

Evolution of GitLab FrontendFatih Acet

��

GitLab Frontend and VueJS at GitLabFatih Acet

��

The document presents a talk by Fatih Acet, a senior frontend engineer at GitLab, discussing GitLab's frontend development using Vue.js and its evolution from various technologies. GitLab is an open-source software development tool aimed at streamlining the DevOps lifecycle, which has transitioned to Vue.js for its smaller size, speed, and ease of learning. Future plans include creating a design system called gitlab-ui, improving tool workflows, and expanding the frontend team.

Migrate to microservicesAndrey Trubitsyn

��

The document details the challenges and strategies involved in migrating a large monolithic application to a microservices architecture. Key issues include managing legacy code, component dependencies, and establishing governance for multiple development teams. The proposed plan emphasizes codebase componentization, independent release strategies, and intensive testing to facilitate a smoother transition to microservices.

How Heroku uses Heroku to build HerokuCraig Kerstiens

��

Heroku uses Heroku to build Heroku. It has over 5000 apps, 500+ releases and 200+ deploys per day across 21 teams. Teams use various tools like Github, Trello, Campfire. Quality is ensured by hiring for quality and culture, giving engineers time without deadlines. Small autonomous teams provide quality, ownership, productivity and agility. Heroku enables continuous deployment by having a defined API, parity across environments from dev to prod, and apps that do one thing well with straightforward setup and low barriers.

Development Journey of the Shopware Administrationklarstil

��

The document outlines the development journey of the Shopware administration panel, emphasizing its goals of extensibility, easy data handling, and maintainability. Key features include a component system, templating with Twig, a flexible module structure, and sophisticated data management using a repository factory and criteria system. It discusses concerns around dependency management and the need for a robust application architecture that supports future scalability and modularity.

Streamlining Product HandoversUXDXConf

��

The document outlines five principles for effective product handovers and takeovers used by Zalando, emphasizing early initiation, thorough communication, the creation of a single source of truth, iterative processes, and cautious implementation to prevent disruptions. It details Zalando's innovative tech efforts, including a logistics management system and the integration of physical stores, along with their engineering culture that embraces autonomy and cloud-native practices. The presentation concludes with a focus on assessing system integrations and establishing a long-term architectural vision.

Static site generation using Metalsmith (Node.js)David Boyer

��

David Boyer's presentation discusses static site generation using Node.js, highlighting its advantages such as improved speed, security, and fewer points of failure compared to dynamic sites. He outlines the use of Metalsmith, a static site generator, and explains its functionalities and plugins for building and managing static content. The presentation also addresses the limitations of static sites and suggests hybrid approaches for combining static and dynamic content.

Metrics 4 faster feedbackKris Buytaert

��

1) Devops aims to break down barriers between development and operations teams through a culture of collaboration, automation of processes, and using metrics to improve performance. 2) Automating builds, testing, deployments, and infrastructure management is key to ensure quality and allow teams to deploy changes quickly. 3) Collecting various metrics about code, deployments, systems, applications and business helps teams understand performance, identify issues, and continuously improve. 4) Sharing metrics, experiences, and code openly helps spread best practices and prevents teams from being locked into proprietary solutions.

Marko.js - Unsung Hero of Scalable Web Frameworks (DevDays 2025)Eugene Fidelin

��

Marko.js is an open-source JavaScript framework created by eBay back in 2014. It offers super-efficient server-side rendering, making it ideal for big e-commerce sites and other multi-page apps where speed and SEO really matter. After over 10 years of development, Marko has some standout features that make it an interesting choice. In this talk, I’ll dive into these unique features and showcase some of Marko's innovative solutions. You might not use Marko.js at your company, but there’s still a lot you can learn from it to bring to your next project.

Testing: do more with less (JSNation 2024)Eugene Fidelin

��

The document discusses effective strategies for testing Node.js web applications, APIs, and backend-for-frontend (BFF) services with a focus on ensuring high quality and reliability in production. It emphasizes the use of DORA metrics to measure deployment success and suggests adopting a 'testing trophy' approach to prioritize and manage different types of tests. Additionally, various testing tools and methodologies, including integration tests and minimal end-to-end tests, are recommended to enhance testing efficiency and performance.

More Related Content

Similar to Housekeeping the platform at scale (20)

"Platform Engineering in practice — Why and How to start", Serg Hospodarets Fwdays

��

Simplified DevOps Bliss -with OpenAI APIVictorSzoltysek

��

TejaSoft Code Audit Case StudiesRaja Nagendra Kumar

��

Releasing the Monolith On a Daily BasisAtlassian

��

Europace's journey to InnerSourceEnrico Hartung

��

YTD Video Downloader Pro Crack [Latest 2025]rpari1867

��

Distributed systems: design, principles and experienciesAndrés Pérez Gil

��

ScaleOut your team - Building a technology team for scale in a DevOps cultureAgileSparks

��

Scaling Autonomy in a FinTech Unicorn - WeAreDevelopers 2019Alvar Lumberg

��

An evening with... DevOpsArkhotech

��

Slaying Monoliths with Node and DockerYunong Xiao

��

Shitlist-driven development and other tricks for working on large codebasesFlorian Weingarten

��

Evolution of GitLab FrontendFatih Acet

��

GitLab Frontend and VueJS at GitLabFatih Acet

��

Migrate to microservicesAndrey Trubitsyn

��

How Heroku uses Heroku to build HerokuCraig Kerstiens

��

Development Journey of the Shopware Administrationklarstil

��

Streamlining Product HandoversUXDXConf

��

Static site generation using Metalsmith (Node.js)David Boyer

��

Metrics 4 faster feedbackKris Buytaert

��

"Platform Engineering in practice — Why and How to start", Serg Hospodarets Fwdays

��

Simplified DevOps Bliss -with OpenAI APIVictorSzoltysek

��

TejaSoft Code Audit Case StudiesRaja Nagendra Kumar

��

Releasing the Monolith On a Daily BasisAtlassian

��

Europace's journey to InnerSourceEnrico Hartung

��

YTD Video Downloader Pro Crack [Latest 2025]rpari1867

��

Distributed systems: design, principles and experienciesAndrés Pérez Gil

��

ScaleOut your team - Building a technology team for scale in a DevOps cultureAgileSparks

��

Scaling Autonomy in a FinTech Unicorn - WeAreDevelopers 2019Alvar Lumberg

��

An evening with... DevOpsArkhotech

��

Slaying Monoliths with Node and DockerYunong Xiao

��

Shitlist-driven development and other tricks for working on large codebasesFlorian Weingarten

��

Evolution of GitLab FrontendFatih Acet

��

GitLab Frontend and VueJS at GitLabFatih Acet

��

Migrate to microservicesAndrey Trubitsyn

��

How Heroku uses Heroku to build HerokuCraig Kerstiens

��

Development Journey of the Shopware Administrationklarstil

��

Streamlining Product HandoversUXDXConf

��

Static site generation using Metalsmith (Node.js)David Boyer

��

Metrics 4 faster feedbackKris Buytaert

��

More from Eugene Fidelin (14)

Marko.js - Unsung Hero of Scalable Web Frameworks (DevDays 2025)Eugene Fidelin

��

Testing: do more with less (JSNation 2024)Eugene Fidelin

��

Testing: Do More With Less (AdvancedJS 2024)Eugene Fidelin

��

The document discusses a practical approach to testing Node.js web applications and APIs, focusing on improving deployment confidence and performance through effective testing strategies. It introduces DORA metrics to measure aspects like deployment frequency and change failure rate, and advocates for a 'testing trophy' methodology involving unit, integration, and end-to-end tests. Key takeaways include prioritizing integration tests, minimizing end-to-end tests, and utilizing various tools to enhance testing efficiency.

Node.js BFFs - our way to the better/micro frontendsEugene Fidelin

��

Marktplaats is the largest online marketplace in the Netherlands, receiving over 8 million monthly visitors. The company transitioned from 3 large monolithic frontends tightly coupled to backend services to over 25 loosely coupled microservices with corresponding backend for frontend services. This improved time to market for features, code maintainability, and developer autonomy and happiness. Key aspects of their architecture include infrastructure for routing requests to frontends, a build process for deploying frontends as packages, extensive testing, and monitoring of performance and errors.

Node.js BFFs: our way to better/micro frontendsEugene Fidelin

��

The document discusses the evolution and implementation of micro frontends (MFs) and backend-for-frontend (BFF) patterns in modern web development, highlighting their advantages over traditional monolithic frontends. It details architectural changes, development practices, testing strategies, and the benefits of decentralized teams, while also noting some challenges such as potential fragmentation and CI/CD pipeline bottlenecks. The improvements in time-to-market, maintainability, and team autonomy are emphasized as significant outcomes of this approach.

AngularJS in practiceEugene Fidelin

��

The document provides a detailed overview of AngularJS fundamentals, including core concepts like modules, directives, controllers, and dependency injection. It highlights best practices and common pitfalls for developing AngularJS applications, emphasizing the importance of separating concerns, using promises, and optimizing performance with tools like Grunt. Additionally, it discusses testing strategies using frameworks like Karma, Jasmine, and Protractor for ensuring application reliability.

Redis persistence in practiceEugene Fidelin

��

Безопасность Drupal сайтовEugene Fidelin

��

Документ освещает вопросы безопасности сайтов на платформе Drupal, включая потенциальные уязвимости, такие как SQL-инъекции и XSS, а также важные меры по их предотвращению. Он подчеркивает, что обеспечение безопасности — это непрерывный процесс, требующий участия всех, кто имеет доступ к сайту, и предоставляет рекомендации по защите Drupal-сайтов. В заключение, автор призывает разработчиков активно следить за обновлениями безопасности и участвовать в код-ревью для минимизации рисков.

Разработка и deploy Drupal сайтов с помощью Features.Eugene Fidelin

��

Документ описывает решение проблемы хранения конфигурации модулей в базе данных Drupal с помощью модуля Features, который позволяет переносить настройки в код. Он также упоминает основные функции модуля, такие как установка, контроль изменений и возможность интеграции с системами контроля версий. Кроме того, документ содержит рекомендации по созданию и управлению features для упрощения процесса разработки сайтов.

Работа с Views в Drupal 7Eugene Fidelin

��

Документ описывает работу с модулем Views в Drupal 7, который позволяет создавать динамические списки объектов и настраивать их отображение. Объясняются основные функции, такие как добавление и редактирование views, работа с полями, фильтрами и сортировками, а также контекстные фильтры. Также упоминаются расширенные возможности и ресурсы для получения дополнительной информации.

Работа с полями (fields) в Drupal 7Eugene Fidelin

��

Документ описывает работу с полями (fields) в Drupal 7, включая их типы, настройки и способы использования. Приведены примеры кода для сохранения и загрузки данных полей, а также информация о группах полей и рендеринге значений. Также предоставлены ссылки на дополнительные ресурсы и контакты автора.

Работа с материалами (nodes) в Drupal 7Eugene Fidelin

��

Документ описывает работу с материалами (nodes) в Drupal 7, включая создание, редактирование и удаление материалов, а также их хранение в базе данных. Приведены основные таблицы БД, методы API для обработки материалов и какие хуки могут быть использованы для изменения функциональности. Также упомянуты расширенные возможности работы с сущностями, мультиязычностью и шаблонами материалов.

Работа с БД в Drupal 7Eugene Fidelin

��

Документ описывает работу с базами данных в Drupal 7, включая поддерживаемые СУБД и методы выполнения SQL-запросов. Представлены примеры запросов на выборку, обновление, вставку и удаление данных, а также использование API для работы с переменными и кешем. Указаны ссылки на дополнительные ресурсы и контакты автора.

Фичи н-н-нада? Или почему стоит использовать модуль Features.Eugene Fidelin

��

Доклад Евгения Фиделина охватывает использование модуля Features в Drupal для управления изменениями на сайте и переноса настроек из базы данных. Подробно рассматривается процесс создания и интеграции изменений, включая разработку контентных типов и внедрение систем контроля версий. Также обсуждаются преимущества модуля, такие как ускорение разработки и снижение времени неактивности сайта при обновлении.

Marko.js - Unsung Hero of Scalable Web Frameworks (DevDays 2025)Eugene Fidelin

��

Testing: do more with less (JSNation 2024)Eugene Fidelin

��

Testing: Do More With Less (AdvancedJS 2024)Eugene Fidelin

��

Node.js BFFs - our way to the better/micro frontendsEugene Fidelin

��

Node.js BFFs: our way to better/micro frontendsEugene Fidelin

��

AngularJS in practiceEugene Fidelin

��

Redis persistence in practiceEugene Fidelin

��

Безопасность Drupal сайтовEugene Fidelin

��

Разработка и deploy Drupal сайтов с помощью Features.Eugene Fidelin

��

Работа с Views в Drupal 7Eugene Fidelin

��

Работа с полями (fields) в Drupal 7Eugene Fidelin

��

Работа с материалами (nodes) в Drupal 7Eugene Fidelin

��

Работа с БД в Drupal 7Eugene Fidelin

��

Фичи н-н-нада? Или почему стоит использовать модуль Features.Eugene Fidelin

��

Recently uploaded (20)

Rapid Prototyping for XR: Lecture 3 - Video and Paper PrototypingMark Billinghurst

��

Proposal for folders structure division in projects.pdfMohamed Ahmed

��

Rapid Prototyping for XR: Lecture 5 - Cross Platform DevelopmentMark Billinghurst

��

AI_Presentation (1). Artificial intelligenceRoselynKaur8thD34

��

Modern multi-proposer consensus implementationsFrançois Garillot

��

Multi-proposer consensus protocols let multiple validators propose blocks in parallel, breaking the single-leader throughput bottleneck of classic designs. Yet the modern multi-proposer consensus implementation has grown a lot since HotStuff. THisworkshop will explore the implementation details of recent advances – DAG-based approaches like Narwhal and Sui’s Mysticeti – and reveal how implementation details translate to real-world performance gains. We focus on the nitty-gritty: how network communication patterns and data handling affect throughput and latency. New techniques such as Turbine-like block propagation (inspired by Solana’s erasure-coded broadcast) and lazy push gossip broadcasting dramatically cut communication overhead. These optimizations aren’t just theoretical – they enable modern blockchains to process over 100,000 transactions per second with finality in mere milliseconds redefining what is possible in decentralized systems.

Rapid Prototyping for XR: Lecture 1 Introduction to PrototypingMark Billinghurst

��

Structural Wonderers_new and ancient.pptxnikopapa113

��

Validating a Citizen Observatories enabling Platform by completing a Citizen ...Diego López-de-Ipiña González-de-Artaza

��

Citizen Observatories (COs) are initiatives that empower citizens to engage in data collection, analysis and interpretation in order to address various issues affecting their communities and contribute to policy-making and community development. Thematic co-exploration is a co-production process where citizens actively participate alongside scientists and other actors in the exploration of specific themes. Making them a reality involves addressing the following challenges: Data quality and reliability Engagement and retention of participants Integration with policy and decision-making

Rapid Prototyping for XR: Lecture 4 - High Level Prototyping.Mark Billinghurst

��

Introduction to Python Programming Languagemerlinjohnsy

��

May 2025: Top 10 Read Articles in Data Mining & Knowledge Management ProcessIJDKP

��

Data mining and knowledge discovery in databases have been attracting a significant amount of research, industry, and media attention of late. There is an urgent need for a new generation of computational theories and tools to assist researchers in extracting useful information from the rapidly growing volumes of digital data. This Journal provides a forum for researchers who address this issue and to present their work in a peer-reviewed open access forum. Authors are solicited to contribute to the Journal by submitting articles that illustrate research results, projects, surveying works and industrial experiences that describe significant advances in the following areas, but are not limited to these topics only.

Abraham Silberschatz-Operating System Concepts (9th,2012.12).pdfShabista Imam

��

Deep Learning for Natural Language Processing_FDP on 16 June 2025 MITS.pptxresming1

��

This gives an introduction to how NLP has evolved from the time of World War II till this date through the advances in approaches, architectures and word representations. From rule based approaches, it advanced to statistical approaches. from traditional machine learning algorithms it advanced to deep neural network architectures. Deep neural architectures include recurrent neural networks, long short term memory, gated recurrent units, seq2seq models, encoder decoder models, transformer architecture, upto large language models and vision language models which are multimodal in nature.

FSE_LLM4SE1_A Tool for In-depth Analysis of Code Execution Reasoning of Large...cl144

��

Generative AI & Scientific Research : Catalyst for Innovation, Ethics & ImpactAlqualsaDIResearchGr

��

Invited keynote at the Artificial Intelligence Symposium on AI-powered Research Innovation, taking place at ENSEM (L'École Nationale Supérieure d'Électricité et de Mécanique), Casablanca on June 21, 2025. I’ll be giving a keynote titled: "Generative AI & Scientific Research: Catalyst for Innovation, Ethics & Impact". Looking forward to engaging with researchers and doctoral students on how Generative AI is reshaping the future of science, from discovery to governance — with both opportunities and responsibilities in focus. #AI hashtag#GenerativeAI #ScientificResearch #Innovation #Ethics #Keynote #AIinScience #GAI #ResearchInnovation #Casablanca 1. Thinking, Creative Thinking, Innovation 2. Societies Evolution from 1.0 to 5.0 3. AI - 3P Approach, Use Cases & Innovation 4. GAI & Creativity 5. TrustWorthy AI 6. Guidelines on The Responsible use of GAI In Research

Industry 4.o the fourth revolutionWeek-2.pptxKNaveenKumarECE

��

System design handwritten notes guidanceShabista Imam

��

International Journal of Advanced Information Technology (IJAIT)ijait

��

International journal of advanced Information technology (IJAIT) is a bi monthly open access peer- reviewed journal, will act as a major forum for the presentation of innovative ideas, approaches, developments, and research projects in the area advanced information technology applications and services. It will also serve to facilitate the exchange of information between researchers and industry professionals to discuss the latest issues and advancement in the area of advanced IT. Core areas of advanced IT and multi-disciplinary and its applications will be covered during the conferences.

NEW Strengthened Senior High School Gen Math.pptxDaryllWhere

��

Bitumen Emulsion by Dr Sangita Ex CRRI Delhigrilcodes

��

Rapid Prototyping for XR: Lecture 3 - Video and Paper PrototypingMark Billinghurst

��

Proposal for folders structure division in projects.pdfMohamed Ahmed

��

Rapid Prototyping for XR: Lecture 5 - Cross Platform DevelopmentMark Billinghurst

��

AI_Presentation (1). Artificial intelligenceRoselynKaur8thD34

��

Modern multi-proposer consensus implementationsFrançois Garillot

��

Rapid Prototyping for XR: Lecture 1 Introduction to PrototypingMark Billinghurst

��

Structural Wonderers_new and ancient.pptxnikopapa113

��

Validating a Citizen Observatories enabling Platform by completing a Citizen ...Diego López-de-Ipiña González-de-Artaza

��

Rapid Prototyping for XR: Lecture 4 - High Level Prototyping.Mark Billinghurst

��

Introduction to Python Programming Languagemerlinjohnsy

��

May 2025: Top 10 Read Articles in Data Mining & Knowledge Management ProcessIJDKP

��

Abraham Silberschatz-Operating System Concepts (9th,2012.12).pdfShabista Imam

��

Deep Learning for Natural Language Processing_FDP on 16 June 2025 MITS.pptxresming1

��

FSE_LLM4SE1_A Tool for In-depth Analysis of Code Execution Reasoning of Large...cl144

��

Generative AI & Scientific Research : Catalyst for Innovation, Ethics & ImpactAlqualsaDIResearchGr

��

Industry 4.o the fourth revolutionWeek-2.pptxKNaveenKumarECE

��

System design handwritten notes guidanceShabista Imam

��

International Journal of Advanced Information Technology (IJAIT)ijait

��

NEW Strengthened Senior High School Gen Math.pptxDaryllWhere

��

Bitumen Emulsion by Dr Sangita Ex CRRI Delhigrilcodes

��

Housekeeping the platform at scale

1. Housekeeping the platform at scale

2. About me Eugene Fidelin Frontend Architect at Marktplaats | Adevinta BNL linkedin.com/in/eugef medium.com/@EugeneFidelin

3. New ads per day 350K Visits per day 6.5M Hits per day 300-400M Connected ads per day 100K Marktplaats: Facts & Figures With over 8 million unique visitors monthly and 18.7 million live ads at any given time, Marktplaats is the largest trading platform in the Netherlands.

4. Vision Product development teams at Marktplaats focus all their efforts on building the product and nothing else. Making it happen We accelerate product development by providing the Frontend Platform: set of services, tools, components and other resources to enable FE engineers to effectively deliver secure, reliable and efficient software.

5. Used by development teams 8 to build services and libraries 40 60 15 that generate production releases per day Frontend platform adoption

6. Team autonomy vs dev efficiency Level of team autonomy reusability reinventing the wheel consistency fragmentation dev support maintenance burden

7. Frontend Golden path ● Stack: most important technologies that are aligned and shared across the teams. ● Information support: ADRs, TechRadar, best-practices, Slack channel, PR reviews. ● Governance: Developed in collaboration with teams, owned by the Platform org. Teams can deviate but they have to pay extra costs! Golden path - opinionated and supported path to build something

8. Golden path stack Client-side ● React setup ● Design System ● Translations Server-side ● Express.js middlewares ● React SSR ● API clients ● Observability tools Build and deploy ● Webpack conﬁg ● TypeScript ● Eslint/Prettier ● Jest ● Node.js Docker

9. Keep teams up-to-date ● Dashboard with live overview of all services, inventory of outdated dependencies on production. ● Automated dependency updates by Renovate. ● Timely security updates by Snyk. ● Batch ﬁxes and improvements with codemods. ● Information support and developer assistance.

10. NCU dashboard. Services

11. NCU dashboard. Libraries

12. NCU dashboard. Dependencies

13. Automated dependency updates ● 24/7 updates for internal NPM packages and Docker images. ● Bi-weekly updates for trusted 3rd-party NPM packages. ● Minor and patch updates are auto-merged when build is green. PRs are only created if build fails. ● Major updates always result in a PR and won't be auto-merged. ● NCU dashboard has overview of pending Renovate PRs ~6 hours to propagate new version to all the services and libraries.

14. Timely security updates ● Regular updates to ﬁx vulnerabilities in open source dependencies (direct and transitive). ● All updates always result in a PRs and are not auto-merged. ● For feature PRs run security check for newly added dependencies.

15. Batch code changes ● Install/update/remove dependency(s). ● Apply custom jscodeshift codemod. ● Run Putout code transformations to ﬁx code smells. ● Apply Prettier to format the source code. ● Run tests and update Jest snapshots. ● Create PR and optionally auto-merge it. Codemod - write a code to rewrite your code.

16. Information support ● ADRs - capture an important architectural decisions made along with its context and consequences. ● Tech Radar - list of Techniques, Tools, Platforms, Language & frameworks we observe: currently used, tested, under research or put on hold. ● Dev assistance - Slack channel to provide immediate help and support. PR reviews to give feedback and guidance.

17. Key takeaways 1. Align the most important technologies across the teams to deﬁne the Golden path. 2. Automate dependency updates, security ﬁxes and roll out of the platform improvements. 3. Accelerate the teams by reducing the maintenance burden and providing support.

18. Credits Articles: ● How We Use Golden Paths to Solve Fragmentation in Our Software Ecosystem ● Software Sprawl, The Golden Path, and Scaling Teams With Agency Images: ● Cover image by pikisuperstar on Freepik ● Robot images by macrovector on Freepik

�ݺ�ߣ

Housekeeping the platform at scale

Recommended

More Related Content

Similar to Housekeeping the platform at scale (20)

More from Eugene Fidelin (14)

Recently uploaded (20)

Housekeeping the platform at scale