Identifiez-vous pour voir le profil complet de Amine
ou
Nouveau sur LinkedIn ? Inscrivez-vous maintenant
En cliquant sur Continuer pour vous inscrire ou vous identifier, vous acceptez les Conditions d’utilisation, la Politique de confidentialité et la Politique relative aux cookies de LinkedIn.
Paris, Île-de-France, France
Identifiez-vous pour voir le profil complet de Amine
Amine peut vous mettre en relation avec plus de 10 personnes chez Teads
ou
Nouveau sur LinkedIn ? Inscrivez-vous maintenant
En cliquant sur Continuer pour vous inscrire ou vous identifier, vous acceptez les Conditions d’utilisation, la Politique de confidentialité et la Politique relative aux cookies de LinkedIn.
539 abonnés
+ de 500 relations
Identifiez-vous pour voir le profil complet de Amine
ou
Nouveau sur LinkedIn ? Inscrivez-vous maintenant
En cliquant sur Continuer pour vous inscrire ou vous identifier, vous acceptez les Conditions d’utilisation, la Politique de confidentialité et la Politique relative aux cookies de LinkedIn.
Voir les relations en commun avec Amine
Amine peut vous mettre en relation avec plus de 10 personnes chez Teads
ou
Nouveau sur LinkedIn ? Inscrivez-vous maintenant
En cliquant sur Continuer pour vous inscrire ou vous identifier, vous acceptez les Conditions d’utilisation, la Politique de confidentialité et la Politique relative aux cookies de LinkedIn.
Voir les relations en commun avec Amine
ou
Nouveau sur LinkedIn ? Inscrivez-vous maintenant
En cliquant sur Continuer pour vous inscrire ou vous identifier, vous acceptez les Conditions d’utilisation, la Politique de confidentialité et la Politique relative aux cookies de LinkedIn.
Identifiez-vous pour voir le profil complet de Amine
ou
Nouveau sur LinkedIn ? Inscrivez-vous maintenant
En cliquant sur Continuer pour vous inscrire ou vous identifier, vous acceptez les Conditions d’utilisation, la Politique de confidentialité et la Politique relative aux cookies de LinkedIn.
À propos
Bon retour parmi nous
En cliquant sur Continuer pour vous inscrire ou vous identifier, vous acceptez les Conditions d’utilisation, la Politique de confidentialité et la Politique relative aux cookies de LinkedIn.
Nouveau sur LinkedIn ? Inscrivez-vous maintenant
Activité
539 abonnés
-
Amine Kherbouche a partagé ceci💪Amine Kherbouche a partagé ceci215 !! Et oui 215 collaborateurs, très exactement un an après notre pivot, nous avons triplé de taille et onboardé 145 ingénieurs et développeurs en faisant la promotion de notre culture d'entreprise, de notre environnement technique. Une formidable aventure humaine, avec ses hauts, ses bas, ses trahisons, tout à construire et à faire, mais surtout une opportunité incroyable de s'entourer de talent de tous les horizons et de toutes les nationalités. J'aime mes gars !!! <3
-
Amine Kherbouche a aimé ceciAmine Kherbouche a aimé ceciPresented Capsule at the Claude meetup organised by SLOAI 🎉 Capsule is our internal Agentic Developer Environment at Teads — a platform that gives Claude Code its own isolated, secure sandbox to work autonomously on your repos, without running with your full privileges. Thanks for the warm welcome and the lively Q&A! 🙌 #ClaudeCode #AgenticAI #DeveloperTools #Teads
-
Amine Kherbouche a aimé ceciAmine Kherbouche a aimé ceciI recently spent quite a bit of time chasing a surprisingly tricky issue in our billing pipeline at Gorgias. Everything worked perfectly in real time. Then we replayed historical events. What followed was a deep dive into Apache Flink event-time processing, watermarks, repartitioning, and some behaviors that were much harder to reason about than the documentation would suggest. I wrote up the investigation, the dead ends, the hypotheses, and the fixes we eventually implemented. If you're working with Kafka, Flink, event sourcing, or large-scale historical reprocessing, you might find it useful: https://lnkd.in/ee5WQGJR Thanks to the teammates who helped review the article and challenge some of the assumptions along the way.When Event Time Meets Reality: Lessons from Building Billing on Apache FlinkWhen Event Time Meets Reality: Lessons from Building Billing on Apache Flink
-
Amine Kherbouche a aimé ceciAmine Kherbouche a aimé ceciEveryone wants a full remote or hybrid role. But very few candidates truly understand what it means to interview for one. Remote work is not just a benefit. It is a trust-based operating system. And trust is not given because your CV looks strong. Trust is built through the way you communicate, prepare, follow up, clarify, and create confidence in others. I have seen too many strong candidates lose momentum in a process not because they lacked technical skills, but because they didn’t show the behaviours required to succeed in a remote-first environment. They came unprepared. They had not done the homework. They struggled to explain clearly why the company, why the role, why now. They gave long, unstructured answers in a 30-minute interview. They communicated in a way that felt too casual, too passive, or not sharp enough for the level of autonomy expected. In a remote or hybrid company, your communication is part of your performance. When people cannot observe how you work every day, they rely on signals. How clearly do you explain your thinking? How concise are you when time is limited? How well do you structure ambiguity? How proactive are you in creating alignment? How quickly do you follow up? How much ownership do you show without being chased? How much confidence do you create in the people evaluating you? This is especially true in high-performance environments. The best remote candidates understand that being good at the job is only one part of the equation. You also need to show that you can operate with autonomy, communicate with precision, build trust asynchronously, and reduce uncertainty for the people around you. Being sharp, concise, and structured is not a “nice to have.” It is a must-have. Being proactive is not a bonus. It is a trust-building mechanism. Preparation is not about pleasing the interviewer. It is about showing that you respect the opportunity, the company, and the time of everyone involved. Because in remote-first teams, the cost of poor communication compounds fast. A vague update creates confusion. A lack of follow-up creates doubt. A passive attitude creates friction. A poorly structured message slows everyone down. A candidate who cannot communicate clearly in an interview will raise questions about how they will communicate once hired. This does not mean you need to be perfect. It means you need to be intentional. Do the homework. Understand the company. Know the product. Prepare your examples. Structure your answers. Be clear on your motivations. Show ownership. Follow up properly. Make it easy for the team to trust you. Because when you interview for a remote or hybrid role, you are not only being assessed on your hard skills. You are being assessed on whether people can trust you when nobody is watching. And in the best teams, that bar is high… #RemoteWork #TechRecruitment #CandidateExperience #InterviewTips #CareerAdvice #Hiring #CommunicationSkills #Trust #FutureOfWork
-
Amine Kherbouche a réagi à ceciAmine Kherbouche a réagi à ceci16 TB of telco logs in. 367 GB on disk. A customer pulled that number up live on a call last week. One month of logs from their telco workload, sitting in object storage at roughly 2% of the raw size. And no, we don't get there by throwing data away. Zero sampling, full fidelity, every log line queryable. No dropped fields, no rollups. How it actually works: We store everything as Parquet, columnar layout, compressed with zstd. Logs compress absurdly well when you lay them out by column instead of by row. The same field repeated across millions of lines collapses to almost nothing. No fixed schema tax either. Elasticsearch makes you pay for indexing every field whether you search it or not. We index selectively, the fields you actually query, and leave the rest as cheap compressed columns you can still scan when you need them. Storage cost drops by orders of magnitude, and you keep 100% of the data. You don't trade your bill for your fidelity. When someone is staring at an Elasticsearch cluster that's 50x the size of the data that went into it, 16 TB landing at 367 GB is hard to argue with.
-
Amine Kherbouche a aimé ceciAmine Kherbouche a aimé ceciLFG! Having the worlds best company NVIDIA talk about Redpanda Data and NYSE makes me infinitely proud to partner with everyone at Redpanda. Live now.
-
Amine Kherbouche a aimé ceciAmine Kherbouche a aimé ceciLe dernier coup de gueule de Linus Torvalds pour la sortie de la version 7.1-rc4 du noyau Linux devrait faire réfléchir tous les RSSI et professionnels de la sécurité. Son constat ? La liste de sécurité de Linux est devenue "quasiment ingérable". En cause : une inondation de rapports générés par IA. Des centaines de personnes utilisent les mêmes outils automatiques pour remonter les mêmes bugs en masse, sans aucune vérification humaine ni compréhension du contexte. Comme le dit si bien Linus : « Ne soyez pas la personne qui envoie un rapport aléatoire sans réelle compréhension. » Quel est le rapport avec votre gestion des vulnérabilités ? Si votre stratégie de sécurité consiste à ouvrir les vannes et envoyer tous les rapports de scans bruts à vos équipes d'exploitation, vous créez la même crise : - Une surcharge cognitive pour vos ingénieurs, la fameuse "Alert fatigue", - Un "travail de fourmi" pour vérifier chaque alerte manuellement, - Des équipes paralysées par des tunnels de validation trop lourds. Détecter des failles est devenu facile. Savoir les requalifier, les centraliser et isoler les 5% critiques qui impactent réellement votre infrastructure, c’est là que réside la vraie gouvernance. La puissance de la détection n’a de valeur que si elle est guidée par du renseignement contextualisé et directement exploitable.
-
Amine Kherbouche a aimé ceciAmine Kherbouche a aimé ceciI wrote how we scaled the RIB (aka the routing table) in Akvorado (the flow collector we develop and use at Free/AS12322) to handle tens of millions of routes while keeping latency at minimum using "RIB sharding" (partition the RIB into several parts to enable parallel updates).
-
Amine Kherbouche a aimé ceciAmine Kherbouche a aimé ceciRecently, at the Betclic Group x Dev With AI meetup, I shared our journey on building and deploying AI agents specifically designed for Developer Experience (DX). We often talk about AI coding assistants, but the real power comes when you decouple the "agent" from the "chat interface." By deploying agents on our own infrastructure, we’ve enabled our users to consume AI through the tools they already use: 🔹 CLI: For instant, local execution within the terminal. 🔹 CI Pipelines: For automated logic verification and quality gates. 🔹 Webhooks: For event-driven workflows across our ecosystem. By treating AI agents as first-class citizens in our infrastructure, we move beyond simple productivity gains to building systemic guardrails. This allows us to scale development velocity while maintaining high engineering standards
-
Amine Kherbouche a aimé ceciAmine Kherbouche a aimé ceciThe team and I have been working hard. Striving for greatness. And it starts with delivering tangible results to our customers. Because of this GetVocal AI has been recognized in the VivaTech Top 100 Rising European Startups 2026. In the AI Voice and Conversational category, we built a solution around a Context Graph architecture that combines deterministic AI with generative models. It gives enterprises the control, transparency, and reliability they need to automate complex customer conversations. Many are only now starting to talk about these architectural foundations. While we built them three years ago. What makes me most proud isn’t the recognition, it’s the results our customers are seeing: real automation of complex CX conversations while keeping humans in control and improving outcomes. Again, I want to thank our valued customers for trusting us with such a critical part of their operations. And of course, our incredible team and investors (Creandum, Speedinvest, and Elaia) for believing in this vision from day one.
Expérience et formation
-
Teads
****** ***** ************** ********
-
*******
******** ********
-
********
******* ****** ********
-
********** ****** ** ***** ***** ****** ***
-
-
Voir toute l’expérience de Amine
Découvrez son poste, son ancienneté et plus encore.
Bon retour parmi nous
En cliquant sur Continuer pour vous inscrire ou vous identifier, vous acceptez les Conditions d’utilisation, la Politique de confidentialité et la Politique relative aux cookies de LinkedIn.
Nouveau sur LinkedIn ? Inscrivez-vous maintenant
ou
En cliquant sur Continuer pour vous inscrire ou vous identifier, vous acceptez les Conditions d’utilisation, la Politique de confidentialité et la Politique relative aux cookies de LinkedIn.
Recommandations reçues
1 personne a recommandé Amine
Inscrivez-vous pour y accéderVoir le profil complet de Amine
-
Découvrir vos relations en commun
-
Être mis en relation
-
Contacter Amine directement
Autres profils similaires
Découvrir plus de posts
-
vCluster
29 k abonnés
🚀 Platform v4.4 + vCluster v0.28 Released! The second release in our Future of Kubernetes Tenancy Launch Series is here, introducing Auto Nodes — bringing dynamic node provisioning and scaling to any environment. Highlights: ✅ 𝗔𝘂𝘁𝗼 𝗡𝗼𝗱𝗲𝘀 – Dynamic, right-sized infrastructure for virtual clusters. Extend our Private Nodes tenancy model with automated, on-demand node provisioning across any cloud or on-prem environment. • Private Node-Aware – Builds on Private Nodes to isolate tenant workloads with dedicated, dynamic nodes • Infra Provider Flexibility – Define Node Types with Terraform, KubeVirt, or NVIDIA BCM for any environment • Karpenter-Like Simplicity – Dynamic scaling built into the vCluster binary, without EKS-only limitations ✅ 𝗔𝘂𝘁𝗼 𝗦𝗻𝗮𝗽𝘀𝗵𝗼𝘁𝘀 – Scheduled snapshots with easy configuration and recovery to protect workloads 👉 Read the full changelog: https://lnkd.in/ge3Gc4kY #Kubernetes #vCluster #CloudNative #PlatformEngineering #MultiTenancy #DevOps
21
-
Vitalii Ruzhnikov
Unusual Concepts US • 2 k abonnés
🖥 Kubernetes Bare Metal Perf Lab — Terraform Proxmox 6 VMs (€39/mo, 64 GB RAM) ✨ Ready to scale from one Proxmox VM to six for our future Kubernetes cluster? This is part 9 of the mini-series — where we continue building a reproducible Kubernetes stage/perf lab on a Hetzner EX44 dedicated server (14c / 20t i5-13500, 64 GB RAM, 2× NVMe). Last time, we deep-dived into a Terraform issue with the Proxmox/bpg provider: “Still creating…” hangs, partial state drift, and inconsistent VM clones caused by RTT spikes between the laptop running Terraform and the Proxmox API. We traced it with mtr, identified the root cause, and fixed it by running Terraform from a Hetzner Cloud VPS in the same datacenter as the dedicated server. Now that Terraform runs reliably again, we can finally move to the fun part of this chapter — preparing Proxmox VMs for Kubernetes and Kubespray provisioning. ℹ️ So what do we actually need to change to make Cloud-Init Kubespray-ready? Before we create 3 control-plane and 3 worker VMs, we need to adjust Cloud-Init slightly — nothing complicated, but important: • enable the bridge-related kernel module (br_netfilter) • allow IP forwarding • ensure bridged traffic passes through iptables • disable swap (otherwise kubelet won’t even start) …and apply a couple of small fixes so Kubespray can provision everything cleanly. Even if you switch to Cilium later — these settings won’t hurt. Cilium doesn’t depend on the bridge/iptables path, and keeping them enabled is totally safe. 💡 What you’ll get after this part: • A fully automated 6-VM Kubernetes layout on Proxmox (3 control planes + 3 workers) • Predictable static IPs for every node • Per-node Cloud-Init templates generated via Terraform • Identical VM specs (CPU/RAM/disk/q35/UEFI/virtio) across the cluster • All nodes booting with Kubernetes-ready settings (bridge modules, IP forwarding, no swap, etc.) • Zero manual clicks in the Proxmox UI — everything declarative • A solid foundation for the next step: Kubespray provisioning ℹ️ The longread (link in comments) It walks through everything in detail — Cloud-Init Terraform template, why Kubernetes needs these settings, how node prep works, and full code examples step-by-step. ⚙️ Terraform updates Terraform code was updated as well — now it supports a full multi-node setup out of the box. Cloud-Init templates were moved into separate .tftpl files. Each node gets its own hostname + Kubernetes-ready config. The final layout (3 control planes + 3 workers) is generated automatically via for_each. Static IPs, unique Cloud-Init snippets, identical CPU/RAM/disk profiles — fully declarative and reproducible. ➜ Coming soon Now that the full VM layout is ready, it’s time to discuss how to access all these nodes sitting behind NAT - before we finally deep-dive into Kubespray provisioning (at last!). #DevOps #Kubernetes #Terraform #IaC #Proxmox #Hetzner #HomeLab #BareMetal #Kubespray #CloudInit
72
7 commentaires -
OllyGarden
2 k abonnés
Yuri O. (OllyGarden) and Juliano Costa (Datadog) at SREDAY in Paris. 19 November at 3:00 PM They will present the OpenTelemetry Collector reliability mechanisms: how they work, where they fail, and what to do when data loss is not an option. Topic: Reliability in critical telemetry pipelines If you're at SREDAY in Paris, let's talk OpenTelemetry and production observability challenges. #SREDAY #OpenTelemetry #Observability
16
1 commentaire -
Recklabs
3 k abonnés
Most companies waste 30% of their AWS budget — and don’t even know where it’s going. Not because they’re careless. Because AWS is complex. Here’s where the money usually leaks: • Idle EC2 instances • Overprovisioned RDS databases • Unused EBS volumes • Forgotten snapshots • Misaligned Savings Plans • Dev environments running 24/7 The scary part? Most finance teams only see the bill — not the architectural decisions behind it. FinOps isn’t about cutting costs. It’s about aligning cloud spend with business value. If your AWS bill feels unpredictable month to month, it’s not a finance problem. It’s a visibility problem. 👉 Book a free FinOps audit and find out where your 30% is hiding.
2
-
Meta Motives
134 abonnés
Kubernetes vs Serverless in 2025: which fits your budget & ops? In our latest project, we stress-tested both models at 𝟭𝗕 𝗔𝗣𝗜 𝗰𝗮𝗹𝗹𝘀/𝗺𝗼𝗻𝘁𝗵 (real-world scale): 💸 Cloud spend 🛠️ DevOps hours (one’s 2.3x heavier) ⚡ Latency (~150ms gap—SLA killer?) The battle-tested CTO cheat sheet. Biggest pain at scale for you: cost, speed, or control? 👇 #Serverless #Kubernetes #CloudCost #DevOps
6
-
Sidharth Shukla
SmarDen • 6 k abonnés
I’ve just published a short blog on Terraform (Infrastructure as Code) 🚀 In this blog, I cover: • What Terraform is and why it’s widely used • How it compares with other IaC tools • Key challenges teams face in real projects • Basic installation steps for Linux & Windows If you’re working in DevOps, Cloud, or Platform Engineering, this might be useful. https://lnkd.in/gGe3swdy #Terraform #InfrastructureAsCode #DevOps #CloudComputing #AWS #Azure #GCP #PlatformEngineering #SRE
11
-
Suresh Rajashekaraiah
Mphasis • 4 k abonnés
Scaling with Confidence: Understanding HPA Tolerance Levels As enterprises modernize workloads on Kubernetes, autoscaling is no longer optional — it is a foundational design choice that impacts reliability, performance, and cost efficiency. The Horizontal Pod Autoscaler (HPA) is often the first scaling mechanism architects implement. Yet, the nuance many overlook is tolerance levels — the thresholds that define when HPA should react to metric changes. At first glance, tolerance might feel like a minor configuration detail. But from a solution architect’s perspective, it directly influences: User Experience → avoiding performance degradation during sudden traffic spikes. Operational Efficiency → preventing “flapping” of pods due to overly sensitive thresholds. Cost Management → balancing scale-up responsiveness with scale-down prudence. Why Tolerance Levels Matter HPA works by monitoring resource metrics (CPU, memory, or custom metrics) and adjusting pod counts. However, metrics naturally fluctuate. Without tolerance, HPA would continuously scale pods up and down, creating instability. Low tolerance (too aggressive): pods scale frequently, driving operational noise and higher costs. High tolerance (too relaxed): workloads risk performance drops before scaling reacts. The default tolerance (10%) is often a starting point, but real-world architectures demand tuning based on workload patterns. Architect’s Lens on HPA Tuning As a solution architect, I frame tolerance discussions around three dimensions: 1. Workload Characteristics Latency-sensitive applications (e.g., payments, trading) need faster scale-up → lower tolerance. Batch or background jobs can absorb fluctuation → higher tolerance for efficiency. 2. Business Priorities Enterprises prioritizing customer experience over cost may tune tolerance tighter. Those focusing on FinOps discipline may accept brief latency for smoother, cost-optimized scaling. 3. Operational Resilience Tolerance tuning must integrate with observability. Architects should pair HPA with dashboards, alerts, and predictive autoscaling to preemptively react to patterns. Leadership Insight Tolerance levels aren’t just technical knobs; they represent architectural trade-offs between agility, cost, and resilience. As solution architects, our role is to ensure scaling strategies align with the organization’s operating model — whether that means absorbing costs to protect customer experience or enforcing stricter efficiency controls. Done right, HPA tuning becomes a business enabler: smoothing seasonal demand, supporting product launches, and ensuring operational confidence. 🔹 Takeaway: HPA tolerance is not a “set and forget” parameter. It is an architectural decision point that shapes how your digital platforms handle unpredictability. Solution architects who master this balance demonstrate not only technical depth but also business leadership in scaling strategies.
10
2 commentaires