ONE-SIZE DOESN'T FIT ALL - EFFECTIVELY (RE)EVALUATE A DATA SOLUTION FOR YOUR SYSTEM, EYNAV MASS, Oribi

•Download as PPTX, PDF•

0 likes•75 views

The document discusses effectively evaluating data solutions for systems. It recommends identifying the business value and needs, such as scale and future costs. It also suggests analyzing expected performance by considering the solution's purpose, resource requirements, and resilience. Additionally, it advises overseeing future plans like the system's scale support, R&D growth plan, and learning curve. The overall document provides guidance on comprehensively evaluating data solutions by examining business value, performance, and future oversight.

Technology

One Size Doesn’t Fit All
Effectively (Re)Evaluate a
data solution for your
system

Hi 👋
Eynav Mass
VP R&D at Oribi
And a happy mother :)

Let’s talk about...
How to effectively
evaluate a data solution
for your system
💡

Let’s talk about - evaluating data solutions
Why bother?
🤔

Let’s talk about - evaluating data solutions

is about:
Codeless Data Insights and
Visualization

is about:
Codeless Data Insights and
Visualization
Export Data
Check out our site for more info: oribi.io

: A BIG-DATA based product
300,000,000 incoming events a day
Auto-Scaled µ-service based architecture
Optimized infrastructure

300,000,000 incoming events a day
Auto-Scaled µ-service based architecture
Optimized infrastructure
: A BIG-DATA based product

From POC to Production
300,000,000 incoming events a day
POC for a new feature at Oribi
PostgreSQL with heavy computation

From POC to Production
300,000,000 incoming events a day
POC for a new feature at Oribi
PostgreSQL with heavy computation
Multiple writes Heavy Read Traffic Scale
+ =

From POC to Production
300,000,000 incoming events a day
POC for a new feature at Oribi
PostgreSQL with heavy computation
💯 Velocity ⛔️ Performance

○ Resources
○ Knowledge / Experience
○ Time
○ Over Motivated Developers :)
○ ...
Reality Check :
Why do we have “non-optimized” data solutions

Let’s talk about - evaluating data solutions Effectively

🎯 Business value
🚀 Performance
⚗️ Overseeing Future Plans
Let’s talk about - evaluating data solutions Effectively

Identify the business value and needs: Scale
Scale

Identify the business value and needs: Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale
Scale

Identify the business value and needs: Scale
Customer Base

Identify the business value and needs: Scale
Usage
Customer Base

Identify the business value and needs: Scale
Usage
3x Scale of active users

Identify the business value and needs: Scale
Ingestion Services

Identify the business value and needs: Scale

Identify the business value and needs
➢ Scale
➢ Go To Market
➢ Product Requirements
➢ Future Costs

Analyze the expected performance
“It worked on the POC...”
“It worked on the staging...”
“It works great on my local...”

Analyze the expected performance
➢ What will be the main purpose of the solution ?

Analyze the expected performance
➢ What will be the main purpose of the solution ?
➢ Where will be the heavy load? Write | Update | Read?

Analyze the expected performance
➢ What will be the main purpose of the solution ?
➢ Where will be the heavy load? Write | Update | Read?
➢ Which types of resource will be needed?

Overseeing Future Plans :
Online Analytics System Development in Alibaba

Overseeing Future Plans
➢ The plans for the system, scale support, technologies

Overseeing Future Plans
➢ The plans for the system, scale support, technologies
➢ The R&D growth plan

Overseeing Future Plans
➢ The plans for the system, scale support, technologies
➢ The R&D growth plan
➢ Learning curve
Oracle HBase + Hadoop

Overseeing Future Plans
➢ The plans for the system, scale support, technologies
➢ The R&D growth plan
➢ Learning curve
➢ Can the solution enrich other features? 1+1 =3

THANK YOU
https://www.linkedin.com/in/eynavmass

Infrastructure code can really benefit from some proven object oriented design principles like SOLID and others. Instead of just thinking about automation, we need to design and build infrastructure software systems that are easy to understand, test and maintain Everyone talks about the fact that infrastructure should be programmatic and treated as a code, but often what this means is just writing a bunch of scripts to automate our deployments. By doing so, aspects like proper documentation, separation to modules , abstraction, even version control that are standard for "regular" software projects are omitted from infrastructure systems. This leads to cumbersome, monolith system - the very thing we are trying to resolve in the software design. I would like to discuss the basic software design principles like SOLID and DRY and how to apply them when automating our deployments, writing docker containers or writing our application stack.

SOLVING MLOPS FROM FIRST PRINCIPLES, DEAN PLEBAN, DagsHub

DevOpsDays Tel Aviv

One of the hardest challenges data teams face today is selecting which tools to use in their workflow. Marketing messages are vague, and you continuously hear of new buzzwords you “just have to have in your stack”. There is a constant stream of new tools, open-source and proprietary that make buyer’s remorse especially bad. I call it “MLOps Fatigue”. This talk will not discuss a specific MLOps tool, but instead present guidelines and mental models for how to think about the problems you and your team are facing, and how to select the best tools for the task. We will review a few example problems, analyze them, and suggest Open Source solutions for them. We will provide a mental framework that will help tackle future problems you might face and extract the concrete value each tool provides. What you’ll learn You’ll learn what signals to watch for to notice you might have MLOps fatigue. How to define the challenge you’re facing and which questions to ask in order to build a “decision tree” for selecting the best-suited tools for the task. A few examples for using this framework in practice on challenges involving data management and automating training/pipeline tasks About 2 years ago we faced a crisis in our DevOps consulting company - the market demand was higher than we could supply. The traditional recruiting process depending on CV and artificial credentials was not working. So we came up with an alternative solution, and since then - we are growing exponentially and diversely. In this talk we will show the practical tools we deployed in order to increase our capacity, and we will show how these tools overcome the inherited bias in the process.

THE PLEASURES OF ON-PREM, TOMER GABEL

DevOpsDays Tel Aviv

The last two decades have been all about SaaS, with advantages that cannot be overstated. Except SaaS isn’t always an option, nor is it always the right choice: businesses in tightly regulated industries, or where information security is paramount, for example, will not - often can not - consider any software that isn’t under their control. For many software enterprises, this leads to the dreaded inevitability of on-premise deployment. Fortunately, the situation today is dramatically different to a scant few years ago, let alone a decade or two: the same technologies that enable SaaS have also radically transformed on-prem deployment. Modern tools like Docker, Consul, ELK and Kubernetes - to name a few - can be leveraged to completely transform the experience for both customers and vendors. In this talk we’ll contrast the challenges and advantages of SaaS and on-prem, see how things have evolved in recent history, and see how modern on-prem deployment can be, if not pleasurable, at least relatively painless.

HOW TO OPTIMIZE NON-CODING TIME, ORI KEREN, LinearB

DevOpsDays Tel Aviv

Github Copilot and tools that help us code better are cool. But I’m lucky if I spend 90 minutes a day writing code. We really need to optimize the hours we spend reviewing code, updating tickets and tracing where our code is deployed. Learn how I save an hour a day streamlining non-coding tasks. This talk is unique because 99% of developer productivity tools and hacks are about coding faster, better, smarter. And yet the vast majority of our time is spent doing all of this other stuff. After I started focusing on optimizing the 10 hours I spend every day on non-coding tasks, I found I my productivity went up and my frustration at annoying stuff went way down. I cover how to save time by reducing cognitive load and by cutting menial, non-coding tasks that we have to perform 10-50 times every day. For example: Bug or hotfix comes through and you want to start working on it right away so you create a branch and start fixing. What you don’t do is create a Jira ticket but then later your boss/PM/CSM yells at your due to lack of visibility. I share how I automated ticket creation in Slack by correlating Github to Jira. You have 20 minutes until your next meeting and you open a pull request and start a review. But you get pulled away half way through and when you come back the next day you forgot everything and have to start over. Huge waste of time. I share an ML job I wrote that tells me how long the review will take so I can pick PRs that fit the amount of time I have. You build. You ship it. You own it. Great. But after I merge my code I never know where it actually is. Did the CI job fail? Is it release under feature flag? Did it just go GA to everyone? I share a bot I wrote that personally tells me where my code is in the pipeline after it leaves my hands so I can actually take full ownership without spending tons of time figuring out what code is in what release.

YOUR OPEN SOURCE PROJECT IS LIKE A STARTUP, TREAT IT LIKE ONE, EYAR ZILBERMAN...

DevOpsDays Tel Aviv

From idea to execution, the challenges of publishing an open source project are very similar to initializing a startup when it comes to creating a successful product that people will love and use. Most open source projects are not “taking-off”, although they are really good! This is because developers (which are usually the creators of open source projects) think that writing the code is the hard part and “neglect” the other parts of publishing a good open source project. In this talk, I will use my experience as a contributor to open source and product head of a startup, to go beyond writing the code itself and cover the other central aspects of creating an open source project, like MVP, product/market fit, marketing and more.

Lean Canvas for Internal Product Owners

Keith Klundt

One Terrible Day at Google, and How It Made Us Better

Randy Shoup

DOES16 San Francisco - David Blank-Edelman - Lessons Learned from a Parallel ...

Gene Kim

Lessons Learned from a Parallel Universe David N. Blank-Edelman, Technical Evangelist, Apcera Just within the last ten or so years, we have seen at least two separate communities evolve at the crossroads of development and operations. The first—DevOps—grew up very much in public, the second matured sequestered within the halls of “special” companies like Google and Facebook and is only now starting to gain visibility and traction in the wider world. The DevOps and Site Reliability Engineering (SRE) communities barely speak, yet both have common ancestors and much to offer each other. Let’s look at what they have in common, how they differ, and what are the key things we can learn from both. DevOps Enterprise Summit San Francisco 2016

There are many excellent courses, books and videos that can help you learn Agile and Scrum, but they all tend to ignore some common challenges teams run into. For example, non-functional requirements. How should we deal with them? Technical stories are also a big challenge. Good luck finding concrete, unbiased information on the pros and cons of the different approaches. Forecasting is another great example. How do you estimate or forecast an entire project? This session will cover a number of these "elephants" in the room and provide concrete and unbiased advise on how to deal with them. All recommendations are based on real-world experiences and will include an honest discussion of relevant pros and cons.

Solving trust issues at scale - Omer Levi Hevroni

DevOpsDays Tel Aviv

Securing service to service communication was never easy. Can we build a system that enforce good practices like least privilege and secure by default without affecting devlopement velocity? Apparently yes - and in this talk I’ll share how! Micro-services are social beings: they can’t function without talking with other services. Every microservice has its own domain, and it usually relies on other micro-services to function properly. But this also raises an interesting question: do we trust all of our micro-services? The truth is that not all micro-services are the same: some micro-services are more sensitive - for example, services that handle user data. Others are user-facing and therefore riskier. We cannot treat all services as equal. We need a good and robust mechanism to describe who can talk with who. At Soluto, we are dealing with this challenge for a while. In this talk, I’ll share the journey we went through until we found a solution we’re happy with: a simple and declarative system that allows services to define who can access them. Any dev can request access to any service, and the service owner can review it. In talk, I’ll share how we build this solution, using open source tools like Open Policy Agent, so you can easily build something similar.

Evolving Architecture and Organization - Lessons from Google and eBay

Randy Shoup

Keynote at DevOpsDays Cuba Successful Internet companies are built on a foundation of excellent culture, efficient organization, and solid technology. As a company needs to scale, all of these parts of the foundation need to grow and scale with it. This session covers modern best practices at innovative companies in Silicon Valley for scaling culture, organization, and technology. Driven primarily by the presenter's experience ranging from small Valley startups to Google and eBay, it discusses: * Organizing small, fast-moving engineering teams * Building a scalable system out of smaller microservices * Maintaining a culture of ownership and collaboration * Developing effective engineering processes of continuous integration and continuous delivery

Scaling Your Architecture for the Long Term

Randy Shoup

Testing Small Agile Projects from Agile Vancouver Quality Conference 2014

Lanette Creamer

OWASP Developer Guide Reboot

Andrew van der Stock

Learning from Learnings: Anatomy of Three Incidents

Randy Shoup

The best response to a system outage is not "What did you do?", but "What did we learn?" This session will walk through three system-wide outages at Google, at Stitch Fix, and at WeWork—their incidents, aftermaths, and recoveries. In all cases, many things went right and a few went wrong; also in all cases, because of blameless cultures, we buckled down, learned a lot, and made substantial improvements in the systems for the future. Looking back with the perspective of 20-20 hindsight, all of these incidents were seminal events that changed the focus and trajectory of engineering at each organization. You will leave with a set of actionable suggestions in dealing with customers, engineering teams, and upper management. You will also enjoy a few war stories from the trenches.

DevOps Enterprise Summit 2016

Shaw Innes

Anatomy of Three Incidents -- Commonalities and Lessons

Randy Shoup

Minimal Viable Architecture - Silicon Slopes 2020

Randy Shoup

This presentation introduces the idea of a "Minimal Viable Architecture". As a company and product evolves, its architecture should evolve as well. We talk about the different phases of a product -- from the idea phase, to the starting phase, scaling phase, and optimizing phase. For each phase, we discuss the goals and constraints on the business, and we suggest an appropriate software architecture to match. Throughout the presentation, we use examples from eBay, Google, StitchFix, and others.

Shifting is more than shifting left

PractiTest

Slides from Jesper Ottosen's 2017 Fall OnlineTestConf session – Shifting is more than shift left. Change is happening to the testing activities. Shift-left automates and codifies the testing activities. Shift-right does it for production. This session was about a couple of other trends, changes, and shifts that are happening to testers and test managers. – Shift-Coach, where It’s more about coaching teams. – Shift-SME, where it’s more about business savvy. – Shift-Deliver, where it’s more about the road to production www.onlinetestconf.com

Microservices Summit - The Human Side of Services

Yelp Engineering

Hacker News Meetup April 2014

Dan Quine

Service Architectures At Scale - QCon London 2015

Randy Shoup

Over time, almost all large, well-known web sites have evolved their architectures from an early monolithic application to a loosely-coupled ecosystem of polyglot microservices. While first-order goals are almost always driven by the needs of scalability and velocity, this evolution also produces second-order effects on the organization as well. This session will discuss modern service architectures at scale, using specific examples from both Google and eBay. It covers some interesting -- and perhaps nonintuitive -- lessons learned in building and operating these sites. It concludes with a number of experience-based recommendations for other smaller organizations evolving to -- and sustaining -- an effective service ecosystem.

Strong Consistency in Databases. What does it actually guarantee? - Andy Goo...

DevOpsDays Tel Aviv

Subject to the CAP theorem, NoSQL distributed systems have mostly chosen availability over consistency. This has been changing, yet many famous databases are still AP only. This talk includes a theoretical overview, and a practical look at the tradeoffs for your application and data between AP and CP modes. Also, how do different levels of consistency actually matter? Distributed data stores are subject to the CAP theorem, and historically NoSQL distributed systems have chosen availability over consistency. This has been changing, yet many famous databases are still AP only. In Eric Brewer's 2012 follow-up article about the CAP theorem he stated: "Availability is obviously continuous from 0 to 100 percent, but there are also many levels of consistency, and even partitions have nuances, including disagreement within the system about whether a partition exists." This talk will include a theoretical overview, but focus on the practical aspects of the theorem. * What are the tradeoffs between AP and CP modes? * How do they affect your application and data? * How do different levels of consistency actually matter?

DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required

Gene Kim

Predictability: No Magic Required Julia Wester, Improvement Coach, LeanKit When you merge onto a freeway and are stuck in bumper-to-bumper traffic, you know right away that its going to be a long trip. Similarly, you can predict the cycle time of your work before it is finished without time consuming, and often incorrect, estimation. Sound like magic? Fortunately for all of us, it's not. This talk explains the basics of queueing theory; demonstrates how allocation models and pull policies affect the cycle time of work; discusses the effects of batch size and variability on queues; and teaches how to successfully monitor your workflow to get leading indicators of effectiveness. With this information, you'll be doing better forecasting, and achieving better outcomes, in no time!

Pricing Pitfalls...and How to Counter Them

Gus Prestera

This deck is from a webinar I conducted (available on YouTube), describing five common mistakes that business consultants make when pricing their services...and more importantly, strategies for countering those traps. I also give you a peek into the Pricing Your Services program, a series of online courses that teaches consultants how to build their pricing system and compete for projects effectively, quickly, and confidently. Visit http://academy.presterafx.com to learn more.

Mobile Testing at Gilt

Gilt Tech Talks

Service Architectures at Scale

Randy Shoup

How do effective large-scale service ecosystems work? Keynote Presentation at Istanbul Tech Talks 2018 How to Design Services * Systems of record * Interface specification * Interface backward / forward compatibility Service Ecosystems * Layered services * "Standardization" through encouragement * Vendor-customer relationships between teams Operating and Deploying Services * Data Migration * Automated Pipelines * Incremental Deployment * Feature Flags

DevOps Ground Zero

Chris Jackson

Planning a data solution - "By Failing to prepare, you are preparing to fail"

Itai Yaffe

Eynav Mass (VP R&D) @ Oribi: When it comes to data solutions, one-size doesn't fit all. Choosing the right best-matching database, or data tools, can be a game-changer for your system. How can you take such a decision effectively? The system, the company, the product, and probably your team - all are evolving, and the best solution for today may not fit tomorrow's needs. In order to pick a data solution for longer term, you should evaluate the optional data tools according to several factors. These factors will reflect the requirements looking forward. At the session, we will discuss these factors, along with sharing some real-life stories and lessons learned, to help you properly plan & prepare your data solutions.

Real-Time Metrics and Distributed Monitoring - Jeff Pierce, Change.org - Dev...

DevOpsDays Tel Aviv

What's hot

The agile elephant in the room

AgileDenver

Solving trust issues at scale - Omer Levi Hevroni

DevOpsDays Tel Aviv

Evolving Architecture and Organization - Lessons from Google and eBay

Randy Shoup

Scaling Your Architecture for the Long Term

Randy Shoup

Testing Small Agile Projects from Agile Vancouver Quality Conference 2014

Lanette Creamer

OWASP Developer Guide Reboot

Andrew van der Stock

Learning from Learnings: Anatomy of Three Incidents

Randy Shoup

DevOps Enterprise Summit 2016

Shaw Innes

Anatomy of Three Incidents -- Commonalities and Lessons

Randy Shoup

Minimal Viable Architecture - Silicon Slopes 2020

Randy Shoup

Shifting is more than shifting left

PractiTest

Microservices Summit - The Human Side of Services

Yelp Engineering

Hacker News Meetup April 2014

Dan Quine

Service Architectures At Scale - QCon London 2015

Randy Shoup

Strong Consistency in Databases. What does it actually guarantee? - Andy Goo...

DevOpsDays Tel Aviv

DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required

Gene Kim

Pricing Pitfalls...and How to Counter Them

Gus Prestera

Mobile Testing at Gilt

Gilt Tech Talks

Service Architectures at Scale

Randy Shoup

DevOps Ground Zero

Chris Jackson

What's hot (20)

The agile elephant in the room

Solving trust issues at scale - Omer Levi Hevroni

Evolving Architecture and Organization - Lessons from Google and eBay

Scaling Your Architecture for the Long Term

Testing Small Agile Projects from Agile Vancouver Quality Conference 2014

OWASP Developer Guide Reboot

Learning from Learnings: Anatomy of Three Incidents

DevOps Enterprise Summit 2016

Anatomy of Three Incidents -- Commonalities and Lessons

Minimal Viable Architecture - Silicon Slopes 2020

Shifting is more than shifting left

Microservices Summit - The Human Side of Services

Hacker News Meetup April 2014

Service Architectures At Scale - QCon London 2015

Strong Consistency in Databases. What does it actually guarantee? - Andy Goo...

DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required

Pricing Pitfalls...and How to Counter Them

Mobile Testing at Gilt

Service Architectures at Scale

DevOps Ground Zero

Similar to ONE-SIZE DOESN'T FIT ALL - EFFECTIVELY (RE)EVALUATE A DATA SOLUTION FOR YOUR SYSTEM, EYNAV MASS, Oribi

Planning a data solution - "By Failing to prepare, you are preparing to fail"

Itai Yaffe

Real-Time Metrics and Distributed Monitoring - Jeff Pierce, Change.org - Dev...

DevOpsDays Tel Aviv

Behind The Scenes Data Science Coolblue 2018-03-22

Matthias Schuurmans

How to Use Data Effectively by Abra Sr. Business Analyst

Product School

Moving Fast At Scale

Randy Shoup

Dashlane Mission Teams

Dashlane

A6 big data_in_the_cloud

Dr. Wilfred Lin (Ph.D.)

A glimpse of business intelligence

Argelo Royce Bautista

How do we prioritize our product backlog in Hygger.io?

Alexander Sergeev

In this presentation, I share how we prioritize our backlog while developing Hygger. The process consists of the following blocks: 1) we formulate goals 2) then choose the metrics to track the movement towards these goals 3) we collect ideas from different sources 4) organize them into a clear structure 5) prioritize ideas using Lean Prioritization (or Value/Cost or Value/Effort) 6) do features scoring 7) write tasks for the features And that's it! The features can be taken to work as needed.

Leverage The Power of Small Data

Karyn Zuidinga

How to improve website performance with real user data

AudienceProject

Initiate Edinburgh 2019 - Big Data Meets AI

Amazon Web Services

Over 90% of today’s data has been generated in the last two years, and growth rates continue to climb. In this session, we’ll step through challenges and best practices with data capturing, how to derive meaningful insights to help predict the future, and common pitfalls in data analysis. Come discover how integrated solutions involving Amazon S3, AWS Glue, Amazon Redshift, Amazon Athena, Amazon EMR, Amazon Kinesis, and Amazon Machine Learning/Deep Learning result in effective data systems for data scientists and business users, alike.

Context Matters - Shifting from Reporting to Analysis

MnSearch, The Minnesota Search Engine Marketing Association

National Wildlife Federation- OMS- Dreamcore 2011

nonlinear creations

How Gousto is moving to just-in-time personalization with Snowplow

Giuseppe Gaviani

Presented at Snowplow London Meetup, 8 February 2017 Dejan Petelin, head of data science at Gousto, gave a presentation about their data journey, explaining how data reflects the customer’s voice and the importance of joining up all data sources. The goal is to delight and retain customers – critical for a subscription business like Gousto’s. Gousto is using Snowplow as a unified log, to scale up its data capabilities, listen to its customer and provide them with a more personalized experience. Finally, Gousto is moving to the real-time pipeline to enable just-in-time personalization.

Intro to Data Analytics with Oscar's Director of Product

Product School

Big Data for HR

David Bernstein

David Bernstein of eQuest, the global leader in job-posting delivery and job board performance analytics, discusses how Big Data analysis provides organizations with greater recruitment marketing effectivenss than ever before. By not only delivering predictive information on job postings but by also taking a holistic look at your talent pipeline, Big Data analysis provides the insight organizations need to make better-informed decisions more quickly, reducing time-to-hire, costs and administrative burden.

[Webinar] When It Comes To Cloud, Great Power Brings Great Responsibility

OpsRamp

Rotary Means Business DJS Consulting overview 3-29-16Daniel Spandau

Graphs in Action: In-depth look at Neo4j in Production

Neo4j

Similar to ONE-SIZE DOESN'T FIT ALL - EFFECTIVELY (RE)EVALUATE A DATA SOLUTION FOR YOUR SYSTEM, EYNAV MASS, Oribi (20)

Planning a data solution - "By Failing to prepare, you are preparing to fail"

Real-Time Metrics and Distributed Monitoring - Jeff Pierce, Change.org - Dev...

Behind The Scenes Data Science Coolblue 2018-03-22

How to Use Data Effectively by Abra Sr. Business Analyst

Moving Fast At Scale

Dashlane Mission Teams

A6 big data_in_the_cloud

A glimpse of business intelligence

How do we prioritize our product backlog in Hygger.io?

Leverage The Power of Small Data

How to improve website performance with real user data

Initiate Edinburgh 2019 - Big Data Meets AI

Context Matters - Shifting from Reporting to Analysis

National Wildlife Federation- OMS- Dreamcore 2011

How Gousto is moving to just-in-time personalization with Snowplow

Intro to Data Analytics with Oscar's Director of Product

Big Data for HR

[Webinar] When It Comes To Cloud, Great Power Brings Great Responsibility

Rotary Means Business DJS Consulting overview 3-29-16

Graphs in Action: In-depth look at Neo4j in Production

More from DevOpsDays Tel Aviv

GRAPHQL TO THE RES(T)CUE, ELLA SHARAKANSKI, Salto

DevOpsDays Tel Aviv

If you have never used GraphQL before, you probably think that it is just another buzzword that will be forgotten in a few years. You might think: “Why do I need to learn a new way to write APIs when REST already answers all my needs?”. Or, you are excited to learn something new but don’t believe GraphQL is mature enough for production. In this talk, I will remind you of some of the pain points you have probably experienced when using REST. I will then explain what GraphQL is and demonstrate how it solves these pain points. Next, I will discuss the disadvantages of GraphQL. Finally, I will provide some guidelines for choosing between REST and GraphQL. By the end of this talk, you will understand what GraphQL is and when to use it.

MICROSERVICES ABOVE THE CLOUD - DESIGNING THE INTERNATIONAL SPACE STATION FOR...

DevOpsDays Tel Aviv

“The International Space Station has been orbiting the Earth for over 20 years. It was not launched fully formed, as a monolith in space. Instead, it is built out of dozens of individual modules, each with a dedicated role - life support, engineering, science, commercial applications and more. Each module (or container) functions as a microservice, adding additional capabilities to the whole. Not only do the modules need to function together, delivering both functional and non-functional capabilities, they were designed, developed and built by different countries on Earth and once launched into space (deployed in multiple different ways), had to work together - perfectly. Despite the many (minor) reliability issues which have occurred over the decades, the ISS remains a highly reliable platform for cutting edge scientific and engineering research. In this session I will describe the way the space station was developed and the lessons Site Reliability and DevOps Engineers can learn from it.

THE (IR)RATIONAL INCIDENT RESPONSE: HOW PSYCHOLOGICAL BIASES AFFECT INCIDENT ...

DevOpsDays Tel Aviv

Have you ever felt you took every wrong turn possible in the process of mitigating a production incident? Did you go through a 3-hour hell during incident response and felt the incident wasn’t complex enough to justify the horrors you’ve experienced? Did it cause you to question your engineering or problem-solving skills? Well, it’s only partially you. Our brain is wired to make decision-making simpler. In doing so, it exposes itself to biases, heuristics, and other quirks that may seem like “bad decisions” in hindsight. In this talk, through real-life outages, we’ll project those psychological principles onto the world of production monitor, and incident management. As a responder, you’ll learn why those behavioral patterns emerge during production incidents and what can be done to limit their effect, and as a manager, you’ll learn how to enable and encourage a healthy environment to better support those patterns.

PRINCIPLES OF OBSERVABILITY // DANIEL MAHER, DataDog

DevOpsDays Tel Aviv

The word observable entered the English language roughly 400 years ago, but the concepts of what it means to see, comprehend, and understand something have been debated since time immemorial. Starting in the 19th century, a series of postulates and criteria coalesced into control theory, and it is from this body of knowledge that we gained the word “observability”. Today, with the advent of complex, interconnected computer systems, that word has taken on new meanings and connotations—some useful, some detrimental, and some just plain confusing. In this talk, we’ll mix a little history, a touch of philosophy, and a healthy dose of reality, to demystify what observability means to us as professional computer people. We’ll tear through the marketing material and unearth foundational principles that will help us to build better infrastructure, write better software, and promote healthier business practices. Finally, we’ll explore some potential new avenues for discussion and understanding.

NUDGE AND SLUDGE: DRIVING SECURITY WITH DESIGN // J. WOLFGANG GOERLICH, Duo S...

DevOpsDays Tel Aviv

Security people say users are the weakest link. But are they? When complying with security becomes too burdensome, users take shortcuts, find workarounds, and end up jeopardizing security. Blaming users is lazy and easy. Making security usable is time consuming and challenging. How does design research help us understand our customers? What patterns and principles drive secure behavior? How can we build empathy with customers and make the right thing to do the easiest thing to do? This session explores these questions, and provides examples of how design thinking and research can help us be more secure. We will walk through our creation of core user personas, design principles, and how these inform and direct our design choices and intent. Don’t blame your users anymore. Come learn how to be part of a future where usability leads security.

(Ignite) TAKE A HIKE: PREVENTING BATTERY CORROSION - LEAH VOGEL, CHEGG

DevOpsDays Tel Aviv

This is for you, you rockstar, ninja coffee drinking workaholic who doesn’t know what a vacation day looks like. Even though you love your job and are dedicated and are super important, you need a break too. We tend to think that working all the time is an effective practice while the truth is that finding the time for self care and recharging your batteries is beneficial for both you and your company. Additionally, if you’re a leader, you’re responsible for the wellbeing of your team. In this talk I’ll discuss the importance of taking time off of work and creating a positive culture surrounding vacation time.

BUILDING A DR PLAN FOR YOUR CLOUD INFRASTRUCTURE FROM THE GROUND UP, MOSHE BE...

DevOpsDays Tel Aviv

This is a story about taking the cloud infrastructure of a successful company, that is still managed as infrastructure of a startup company, and rebuilding it to support the growing business requirements, especially around disaster recovery and business continuity. In the session I will share Next Insurance’s journey - where we started, where we are now and what we learned on the way so far. I will talk about how we managed to build our proven DR plans, and actually execute them in our DR drills. I will also talk about why we decided that the only way to prove your DR plan works is to continue running your business in the DR account and make it your production account, and go on to build your next DR account. If you are a part of a company that is about to embark on a similar journey, this session might equip you with some very useful insights on how to think about such a challenge, and some very useful and practical tips on how to execute it.

THE THREE DISCIPLINES OF CI/CD SECURITY, DANIEL KRIVELEVICH, Cider Security

DevOpsDays Tel Aviv

CI/CD pipelines are quickly becoming the path of least resistance for would-be attackers into sensitive internal systems, gaining access to critical data, with minimal effort. In the InfoSec world when we talk about CI/CD security often times this focuses on specific aspects of securing your pipeline - scanning the code, protecting secrets, securely managing code deployments, or even authentication and authorization mechanisms, but we rarely talk about all of these together. After years of being in the trenches and realizing that the attack surface is growing and the threat landscape becoming more and more complex, it has become increasingly apparent that security teams need to adapt and modify strategies to keep up with the new reality of CI/CD protection, without compromising developer velocity. In this talk I would like to propose a new way of thinking about CI/CD security - that encompasses the three disciplines that comprise CI/CD security - security in the pipeline, of the pipeline, and around the pipeline. Partial coverage of any or all of these disciplines simply will not cut it with the continuously evolving risk landscape. Security engineers need to address each of these aspects in their entirety to provide the full scope of coverage that modern organizations need, and I will take a deep dive on the challenges each introduce, and the approaches and techniques for mitigating them based on adversarial sec research.

CONFIGURATION MANAGEMENT IN THE CLOUD NATIVE ERA, SHAHAR MINTZ, EggPack

DevOpsDays Tel Aviv

Configuration Management is at the core of Ops. It’s the biggest enabler of any compute operation, small and big. In the past decade, we have switched from thinking about the machines we are configuring, to think about the software and services we are controlling. With that change of mindset, so did the tools we are using. Traditional tools like Puppet, chef, salt and Ansible are slowly declining while new tools such as Terraform, Pulumi, Helm and Kustomize are on the rise. In this talk I will try to describe the pain-points and the opportunities of this transformation as well as suggesting a future direction based on tools developed at the big-tech companies (Mainly facebook and google).

SOLVING THE DEVOPS CRISIS, ONE PERSON AT A TIME, CHRISTINA BABITSKI, Develeap

DevOpsDays Tel Aviv

We all know how hard it is to find DevOps engineers, and creating a diverse team despite gender and ethnicity bias? Nearly impossible. At this talk we will show our tools and methods implemented in the Develeap hiring process that overcome this inherited bias. About 2 years ago we faced a crisis in our DevOps consulting company - the market demand was higher than we could supply. The traditional recruiting process depending on CV and artificial credentials was not working. So we came up with an alternative solution, and since then - we are growing exponentially and diversely. In this talk we will show the practical tools we deployed in order to increase our capacity, and we will show how these tools overcome the inherited bias in the process.

OPTIMIZING PERFORMANCE USING CONTINUOUS PRODUCTION PROFILING ,YONATAN GOLDSCH...

DevOpsDays Tel Aviv

Everyone wants observability into their system, but find themselves with too many vendors and tools, each with its own API, SDK, agent and collectors. With the increasing complexity of modern applications, continuous profiling methods and tools are gaining popularity among the Developer and Engineering communities. In this session, we cover what continuous profiling entails and why you should implement a profiler into your tech stack (if you haven’t done so already). We’ll then bring theory to practice and demonstrate a real-life scenario using gProfiler, a free open-source continuous profiling tool, covering Linux servers on multiple architectures (such as Graviton).

HOW TO SCALE YOUR ONCALL OPERATION, AND SURVIVE TO TELL, ANTON DRUKH

DevOpsDays Tel Aviv

“Being oncall sucks. But it doesn’t have to!” We all heard this one before. Why is it though, that oncall still remains the biggest scar for many? What can a modern Engineering org do to rein the oncall dragons, and actually help people grow as professionals as they go oncall? In this talk, I will present the main reasons why oncall is difficult in modern orgs, and describe ways to mitigate these hardships. The idea is that oncall is often the ‘backroom’ of an org, where all the technical and organizational debt take their toll. Be it unwieldy systems or broken processes between teams, oncall checks all the ‘weak boxes’. Therefore, the only way to win at oncall is to sort out your debts, starting with the organizational ones. I will dive into the detail of the oncall rotation at Snyk as the org scaled from 1 to 220 people, what worked well about it, and what was less than perfect. I will discuss the decisions made to turn oncall into a building block of the org, and show a path to rein oncall in your organization as well.

FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

DevOpsDays Tel Aviv

Do you know what it feels like to navigate as someone who can’t distinguish between green and red - looking at those badges that tell you whether something is broken or a-okay? I’ll give you a quick look into what it feels like with some examples from the monitoring tool Icinga Web 2. We all tend to forget, that not everyone sees the world like we do. In this talk I’ll be walking you through different views in Icinga Web 2 with side-by-side comparisons for the default views and how different kinds of vision impairments affect those. The talks also features a few suggestions on how to improve colour schemes and making websites and webapps better to navigate with screen readers!

(Ignite) WHAT'S BURNING THROUGH YOUR CLOUD BILL - GIL BAHAT, CIDER SECURITY

DevOpsDays Tel Aviv

Recent years have exposed startups to a major plague - cloud overspend. No vaccine appears to exist, plethora of tools and consultants fail to stop the bleeding. And yet, some companies manage to stay safe. What makes them different? Is it the tools? Is it the mindset? Is it developer training? In this session we will examine the cultural factors involved in sound and responsible financial management in the cloud. We will also look at relevant system design elements and product design elements which enable us to spend wisely while our business runs smoothly. Following this session, you should be better versed in cost-aware system design and some of the cultural and structural requirements to keeping your cloud bill low.

SLO DRIVEN DEVELOPMENT, ALON NATIV, Tomorrow.io

DevOpsDays Tel Aviv

In every development process there is the question, do we invest enough on quality? Do we need to invest more? Every team knows about the dilemma of how many tests is the right amount of tests we should write. Is 80% test coverage is good enough? Maybe 90%? 100%? Should we invest more time in unit testing? Are we wasting too much time on unit-testing? Should we invest time on a faster rollback mechanism? WIIFM “Without data, you’re just another person with an opinion” - W. Edwards Deming SLO Driven Development is a framework that helps the developers focus on impact and balance of every aspect of the dev process. When working currently with SLI, SLA, SLO and error budget you can learn where to invest in the development process. Let’s talk about the importance of good SLOs and how they can help us improve our day2day

ONBOARDING IN LOCKDOWN, HILA FOX, Augury

DevOpsDays Tel Aviv

In this talk, I will share do's and don'ts on how to onboard successfully in a remote or hybrid setup including moving to a leadership role, speaking from my own journey onboarding remotely in the midst of a global pandemic. I will share the tips that worked for me for successful onboarding, how I was able to be productive, impactful, and make a good impression on others. The key issues as an “onbordee” that I will talk about are how to create relationships, make yourself visible in the company, time management, and more. Since I started working in Augury over 100 new employees have joined the company. Each month I give a session that is part of their general onboarding process. This became a crucial step due to the fact that we are now a hybrid company and a lot of people are onboarding remotely or in a hybrid setup for the first time in their lives. I joined the company as a backend developer and a few months into my role, the squad leader position in my squad was up for grabs and I was fortunate enough to grab it :) This is my first official leadership role, which I also needed to onboard into in a hybrid setup. I will share the process that I built for myself on “How to lead”. Also, a word or two on the process we built as a squad on how we work in a hybrid setup, what are we optimizing for when we do meet and how to include new members of the team.

DON'T PANIC: GETTING YOUR INFRASTRUCTURE DRIFT UNDER CONTROL, ERAN BIBI, Firefly

DevOpsDays Tel Aviv

In your ever-changing Infrastructure, some changes are intentional while others are not. Drift is what happens whenever the real-world state of your infrastructure differs from the state defined in your configuration. This can happen for many reasons, sometimes it happens when adding or removing resources, other times when changing resource definitions upon resource termination or failure, and even when changes have been made manually or via other automation tools. While Terraform itself can detect drifts, in most cases, you will be informed about it too late: just before you are about to deploy new changes to your infrastructure. What’s interesting about Terraform though, is that you can apply changes in two separate and distinct steps of “Planning” and “Applying”. This means that you have full visibility of what Terraform is planning on doing beforehand, and if you are satisfied with the changes, you can choose to apply them. So how does this work? When something is changed intentionally, it will appear in the source code, and the Terraform plan will not do anything. However, if any part of the infrastructure has been changed manually, Terraform’s plan will identify this, and alert you to the change. In other words, if your IaC drifted from its expected state, then Terraform’s plan will, in fact, detect it. Applying this simple solution can empower DevOps and developer velocity, with the reassurance and context for unexpected changes in your IaC, in near real-time. This talk will showcase real-world examples, and practical ways to apply this in your production environments while doing so safely and at the pace of your engineering cycles.

KEYNOTE | WHAT'S COMING IN THE NEXT 10 YEARS OF DEVOPS? // ELLEN CHISA, bolds...

DevOpsDays Tel Aviv

(Ignite) OPEN SOURCE - OPEN CHOICE: HOW TO CHOOSE AN OPEN-SOURCE PROJECT, HIL...

DevOpsDays Tel Aviv

(Ignite) HISTORY IS A WHEEL. TECH IS A SPIRAL, ERAN ZIMBLER, Alibaba Cloud

DevOpsDays Tel Aviv

Presenting the concept of spiral history in computer technology, with very little examples. spiral history is a metaphor for how we do the same stuff every few years but they work out a little bit different. “Those who cannot remember the past are condemned to repeat it” or so it is said, in technology and even more specifically in computer science it still holds true, however in computer science it is not exactly repeating and sometimes in our very young field forgetting the past actually helps since what haven’t worked before might work today. 5 minutes for 2 examples of spiral history and i hope you will accept this theory.

More from DevOpsDays Tel Aviv (20)