This is a near duplication of the previous keynote deck where we talk about three examples of where I really felt the pain of not applying core observability techniques. The three covered are:
- No pre-aggregation
- Arbitrarily wide events
- Exploration over dashboarding
TechSEO Boost 2018: Implementing Hreflang on Legacy Tech Stacks Using Service...Catalyst
One of the challenges faced at enterprise SEO level is often the legacy platforms and tech stacks that you inherit. Finding a cost-effective way of implementing international SEO best practice is often a barrier to internationalisation. Edge technology is creating new opportunities to optimise websites independently of the inherited technological barriers. In this session, SALT.agency’s Dan Taylor will explore their findings from implementing Hreflang using cutting edge technology to remove these barriers.
utomation is becoming more and more important in the world of software testing, especially as more development shops move into agile or agile-like methodologies. However, for testers with no development background the idea of learning how to automate can be intimidating.My goal is simple: to demystify the subject by taking a novice tester with no coding experience through the process of writing a simple automated test using using the Cucumber framework. I will take a volunteer from the audience and transform that person from an ordinary QA professional (or whatever their occupation) into an automation engineer in one short hour.
This will be a live demonstration and we will be working without a net. No animals will be harmed during the show, but be prepared to slay your fear of coding once and for all.
Migrating existing monolith to serverless in 8 stepsYan Cui
The document discusses refactoring a monolithic application to a serverless architecture in 8 steps. It covers identifying service boundaries, organizing code into separate repositories for each service, choosing deployment tools, keeping functions simple and single-purpose, and migrating features to new services incrementally while maintaining compatibility with the existing monolith. The goal is to break the application into small, autonomous services that can be developed and deployed independently for improved scalability, resilience and development velocity.
This document summarizes a presentation about properly computing service level objectives (SLOs) using latency data. It discusses common mistakes like averaging percentiles, and better approaches like using histograms. Log linear histograms are recommended as they provide flexibility in choosing thresholds while being space efficient. Open source libraries like libcircllhist can be used to calculate SLOs from latency data stored in histograms.
The document discusses technical SEO best practices for signaling including using consistent URLs across pages and properties, implementing HTTP status codes properly, and using rel attributes like canonical and hreflang. It emphasizes pointing all signals to a single URL and using status codes properly. The document also thanks various mentors and contributors and lists icon credits.
Historically, SEO was a very technical discipline. Over time, that shifted as Strategists began touting the death of SEO and claiming all you need is great content. Today, SEO is going back to those technical roots. From simple data markup to more complex proprietary technologies like AMP; now more than ever SEOs & marketers have to be technical masters. Learn why it's important to embrace these technical roots, what technologies we should be learning now, and how to stay ahead of the curve.
Challenges of building a search engine like web rendering serviceGiacomo Zecchini
SMX Advanced Europe, June 2021 - With the advent of new technologies and the massive use of Javascript on the internet, search engines have started using Web Rendering Services to better understand the content of pages on the internet. What are the difficulties in building a WRS? Are tools we use every day replicating what search engines do? In this session, Giacomo will drive you on a discovery journey digging in some techy implementation details of a search engine like web rendering service building process, covering edge cases such as infinite scrolling, iframe, web component, and shadow DOM and how to approach them.
Patterns of the Lambda Architecture -- 2015 April - Hadoop Summit, EuropeFlip Kromer
This talk centers on two things: a set of patterns for the architecture of high-scale data systems; and a framework for understanding the tradeoffs we make in designing them.
Building a social network in under 4 weeks with Serverless and GraphQLYan Cui
This document discusses how a social network was built in under 4 weeks using serverless architecture and GraphQL. A small team including 1 full-time front-end developer for mobile, 1 full-time front-end developer for CMS, and 1 part-time back-end developer completed the project in approximately 7, 3, and 4 weeks respectively. AWS services like Cognito, AppSync, DynamoDB, Lambda, S3, and CloudFront were used to build the backend. An AWS organization structure was also implemented for production, staging, and development environments.
This document discusses monitoring and summarizes key points about collecting and analyzing data. It describes collecting log and metrics data using tools like Logstash and Collectd, storing and visualizing data with Graphite, InfluxDB and Grafana, and monitoring applications using JMX. The overall message is that monitoring is important for making fact-based decisions, and collecting data once and sharing it supports various teams like operations, development and business.
How Googlebot Renders (Roleplaying as Google's Web Rendering Service-- D&D st...Jamie Indigo
Roleplay as a fearless Technical SEO who must pass through Google's Web Rendering Service (WRS), a legendary construct, as part of a mission to protect site visibility.
Panel: 'Think like a bot, rank like a boss' from BrightonSEO September 2019
How to bring chaos engineering to serverlessYan Cui
You might have heard about chaos engineering in the context of Netflix and Amazon, and how they kill EC2 servers in production at random to verify that their systems can stay up in the face of infrastructure failures. But did you know that the same ideas can be applied to serverless applications? Yes, despite not having access to the underlying servers, we can still apply principles of chaos engineering to uncover failure modes in our system (and there are plenty!) so we can build a defence against them and make our serverless applications more robust and more resilient!
TechSEO Boost 2017: SEO Best Practices for JavaScript T-Based WebsitesCatalyst
While providing a dynamic and fast user experience, JavaScript-based sites (SPAs/PWAs) are not always “SEO friendly.” Therefore, it is crucial for developers to understand how search engines crawl, parse, eventually render, and index dynamic websites, to make sure bots get the experience they developed and the content of the site.
As companies mature their software development practices, automated acceptance-level testing is becoming more commonplace. In particular, Cucumber and its Gherkin-based equivalents are enjoying widespread use. Through observing and facilitating the adoption and implementation of Cucumber test suites, I have found ways in which the technology has helped teams greatly, but I have also found ways in which it hindered them. I realized that Cucumber and its kin are appropriate tools in fewer situations than the ones in which they are currently employed. In other words, many teams that use such frameworks need to reevaluate whether they are right for the job, and perhaps replace them. I invite all involved in automated acceptance testing to attend as I try to build a compelling case for this notion.
Are you there Page Experience? It's Me, DevTools.Rachel Anderson
This document summarizes a presentation about using Chrome DevTools to test and optimize websites for Google's upcoming Page Experience update. It discusses the components of the update like mobile-friendliness and core web vitals. It provides guidance on using DevTools to test for issues in areas like intrusive interstitials, HTTPS security, and core web vitals metrics. The presentation emphasizes that field data may differ from lab tests in DevTools, and it outlines many resources for further information on the Page Experience update and related topics.
What happens when you combine Mobile First Index, Performance, and JavaScript? You find the critical rendering path. This talk will look at how these 3 major components of search can guide your strategy and tactical ways to improve them.
Google Lighthouse is super valuable but it only checks one page at a time.
Hamlet will show you how to get it to check all pages of a site, and how to run automated Lighthouse checks on-demand at scheduled intervals and from automated tests.
He'll also cover how to set performance budgets, how to get alerts when budgets are exceeded, and how to aggregate page reports using BigQuery and Google Data Studio.
Preparing for CDN failure: Why and howAaron Peters
This document discusses preparing for content delivery network (CDN) failures and how to monitor CDN performance. It provides examples of past CDN outages and failures. It then covers different methods for monitoring CDN performance, including synthetic monitoring and real user monitoring. It emphasizes the importance of measuring failure rates not just speeds. The document also discusses mitigating CDN failures through a multi-CDN approach with dynamic traffic steering based on performance data. It notes some challenges in decision making and with low volume data. Finally, it shares a story about responding to an outage at a company.
Is Docker really the security risk that is generally raged about? Or, is this more about understanding where and when a business should consider adoption new and revolutionary infrastructure?
Automated Duplicate Content Consolidation with Google Cloud FunctionsHamlet Batista
Avoid duplicate content and don’t leave money on the table with unoptimized groups of pages linked by canonical declarations! Particularly in e-commerce, you can increase Google’s confidence by making sure your groups of product URLs are perfectly canonicalized and clear to search engines.
DevОps is usually viewed from a traditional perspective of a collaboration of Dev, Ops, and QA, driven by the change in Culture, People, and Process. But how do you know where you stand and where to move? As in almost any field, data and metrics give you the gauges and instruments. In this talk, we’ll talk about the key measurements for the DevOps transformation process and provide you with 3 metrics you can start measuring tomorrow.
Updates on Offline: “My AppCache won’t come back” and “ServiceWorker Tricks ...Natasha Rooney
My slides from my talk "Updates on Offline: “My AppCache won’t come back” and “ServiceWorker Tricks for Cache”" from Over the Air 2013 held in September in Bletchley Park. We had a good run-through of offline APIs in web, the mysteries of App Cache, and updates on the current status of ServiceWorker.
FirefoxOS Meetup - Updates on Offline in HTML5 Web AppsNatasha Rooney
This document summarizes Natasha Rooney's presentation on offline web apps. The presentation discussed issues with the App Cache API and introduced Service Workers as a new solution. It highlighted that App Cache was not well-suited for separating caching of shell content from dynamic content. Service Workers address this by allowing developers more control over caching and fallbacks. The presentation concluded that Service Workers enable better support for offline apps through features like multiple caches, fallbacks, and promises.
This document appears to be slides from a presentation on concurrency in Ruby applications. The slides discuss different concurrency models including blocking threads, callbacks, reactors, and fibers. They explore when concurrency is useful based on factors like context switching costs. Linear and mixed data dependencies are presented as examples to illustrate different concurrency interfaces and implementations using threads or asynchronous callbacks.
A Deep Dive Into Concurrent React by Matheus AlbuquerqueScyllaDB
Writing fluid user interfaces becomes more and more challenging as the application complexity increases. In this talk, we’ll explore how proper scheduling improves your app’s experience by diving into some of the concurrent React features, understanding their rationales, and how they work under the hood.
This document discusses the importance of monitoring in DevOps. It provides examples of metrics to monitor like response times, errors, user behavior etc. and how to collect and visualize this data. Open source tools like CollectD, Graphite, Logstash, Elasticsearch, Kibana, InfluxDB and Grafana are recommended for collection, storage and visualization of monitoring data. The document emphasizes making decisions based on facts obtained from monitoring and continuous improvement.
Atmosphere Conference 2015: The 10 Myths of DevOpsPROIDEA
Speaker: Seth Vargo
Language: English
Although not officially coined until 2009, DevOps ideals have been explicitly discussed since at least 2006. Recently, however, the term "DevOps" has gained increasing popularity across a variety of fields and industries. DevOps is not a development methodology or technology; DevOps is an ideology. It is a way to facilitate organizational prosperity and growth while increasing each individual employee's happiness along the way. As DevOps has gained in prominence, a gap has been created between the original definition of DevOps and this new "enterprise-ready" buzzword.
For organizations beginning DevOps practices, this talk will provide a 10,000ft view of DevOps and how you can properly implement DevOps practices in your organization. For organizations that are currently practicing DevOps, this talk will cover common pitfalls, ways to sustain a happy culture, and new tips to foster organizational prosperity.
Visit our website: http://atmosphere-conference.com/
Data driven devops as presented at QCon London 2018Baruch Sadogursky
Devops is usually viewed from a traditional perspective of a collaboration of Dev, Ops, and QA, driven by the change in Culture, People, and Process. But how do you know where you stand and where to move? As in almost any field, data and metrics give you the gauges and instruments. In this talk, we’ll talk about the key measurements for the DevOps transformation process and provide you with 3 metrics you can start measuring tomorrow.
This document discusses the power of open data and how making data available online can enable new applications and discoveries. It provides examples of how open government data allowed for the creation of apps like a gas pump inspection checker. The document also discusses how RESTful principles and APIs have allowed systems like Twitter to be used in new ways not envisioned by their creators by opening their data to developers through standardized interfaces. Overall, the key message is that opening data can fuel innovation and discovery at a relatively low cost.
Microservices, Events, and Breaking the Data Monolith with KafkaVMware Tanzu
One of the trickiest problems with microservices is dealing with data as it becomes spread across many different bounded contexts. An event architecture and event-streaming platform like Kafka provide a respite to this problem. Event-first thinking has a plethora of other advantages too, pulling in concepts from event sourcing, stream processing, and domain-driven design.
In this talk, Ben and Cornelia will tackle how to do the following:
● Transform the data monolith to microservices
● Manage bounded contexts for data fields that overlap
● Use event architectures that apply streaming technologies like Kafka to address the challenges of distributed data
Speakers:
Cornelia Davis, Author & VP, Technology, Pivotal
Ben Stopford, Author & Technologist, Office of CTO, Confluent
Tom Capper Mozcon 2021 - Core Web Vitals - The Fast & The SpuriousTom Capper
The document discusses Core Web Vitals (CWV) and optimizations for them. It notes flaws in how CWV are defined and measured. It also summarizes that Google has delayed rolling out the CWV ranking update multiple times and provided clarifying details. The document suggests prioritizing high traffic pages for CWV work. While metrics can be optimized, improvements should not compromise page speed. Overall CWV may matter less for rankings than other factors like discoverability.
Starting Your DevOps Journey – Practical Tips for OpsDynatrace
To watch, please see:
https://info.dynatrace.com/apm_wc_getting_started_with_devops_na_registration.html
Starting Your DevOps Journey: Practical Tips for Ops
In this webinar, Andreas Grabner, Chief DevOps Activist at Dynatrace, shares practical tips that all IT groups from Dev to Ops can use to start their DevOps journey quickly. With experience from hundreds of DevOps deployments, Andi provides insights it would take your team months or years to learn firsthand.
- Learn how everyone on your Ops team can use APM to better understand and monitor SLAs, Performance and End User Impact of their applications.
- Foster better collaboration between Ops and architects by extending basic system monitoring to monolith and microservices architectures.
- Shift-left your testing and QA by working with metrics that you and the architects agreed on up front, resulting in early relevant feedback and faster code deployments.
- Hear why changing the cultural mindset from “fear of change” to “Continuous Innovation and Optimization” is critical for success.
Andi is joined by guest speaker, Brian Chandler, Systems Engineer at Raymond James, who shares commonly used Ops dashboards that increase collaboration across IT teams and pro-actively break down silos!
Majestic Workshop on Backlinks and Link BuildingSante J. Achille
This document discusses strategies for analyzing backlinks and link building. It provides an example of analyzing the backlink profile of a company in the food processing industry to identify new link building opportunities. It also discusses how to use Majestic tools like Link Context to evaluate link quality and find high-quality pages to link to on a given topic.
Sam Newman is a technologist at ThoughtWorks. This talk from FlowCon 2014 goes into the nitty gritty of managing build, test and release of microservices and also covers the often ignored tradeoff between testing before deployment, and testing afterwards.
Web Development Foundation
- backend & frontend
- RESTful API
- MVC and Seperation of Concern
Team Collaboration
- Why do we need unit test & TDD
- git basics and workflow
8 Lessons Learned from Using Kafka in 1500 microservices - confluent streamin...Natan Silnitsky
Kafka is the bedrock of Wix's distributed microservices system. For the last 5 years we have learned a lot about how to successfully scale our event-driven architecture to roughly 1500 microservices.
We’ve managed to achieve higher decoupling and independence for our various services and dev teams that have very different use-cases while maintaining a single uniform infrastructure in place.
In these slides you will learn about 8 key decisions and steps you can take in order to safely scale-up your Kafka-based system. These include:
* How to increase dev velocity of event driven style code.
* How to optimize working with Kafka in polyglot setting
* How to support growing amount of traffic and developers.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1uRYaAR.
Volker Pacher, Sam Phillips present key differences between relational databases and graph databases, and how they use the later to model a complex domain and to gain insights into their data. Filmed at qconlondon.com.
Sam Phillips is Head of Engineering for eBay's Local Delivery team, bringing super fast delivery to customers in the UK and US. Volker Pacher is a Senior Developer at eBay Local Delivery. Before its acquisition by eBay, he was a member of the core team at Shutl helping to transition from a monolithic application to SOA and introducing new technologies, among them Neo4j.
”Everything is a stream“ - This often cited mantra indicates why Reactive Programming is such a powerful tool for handling data flows in almost every part of an application. Reactive Programming has experienced a significant growth in popularity in recent years. But its growing popularity also leads to a Babylonian confusion: the term ”Reactive“ has become overloaded. To understand what Reactive Programming is, this talk surveys the landscape sharpened by trends like Reactive Streams, Reactive Extensions, and Reactive Systems. It then summarizes the basic principles of Reactive Programming by looking at the Reactor library. Finally, it discusses an application of Reactive Programming that lies beyond the standard tutorial examples: an implementation of the BigPipe pattern using Spring 5.
The changing role of testing and test automation in the increasingly fast-paced world of continuous delivery and automated acceptance testing. Learn how, in a DevOps environment, testing activities start with requirements discovery and definition, playing a vital role in not only detecting defects, but preventing them, and ensuring not only that the features are built right, but the right features are built. And learn how test automation needs to happen during, not after, the sprint, and how you can achieve this.
Despite rumors to the contrary, the role of the tester is not diminished with the arrival of automated DevOps, with its ultra-rapid deployment cycles and its emphasis on automation. On the contrary, testers play a vital role in ensuring that the code that gets deployed ten times a day is worth deploying.
Similar to Observability - Experiencing the “why” behind the jargon (FlowCon 2019) (20)
Talk given at Equal Experts internal conference (gEEk) and talks about the patters associated with DevEx and the need for better platform engineering experience if we are expected to build great application engineer experiences.
Building a great internal platform starts with the API Abigail Bangser
The document discusses building internal platforms as products by taking an API-first approach. It recommends starting by identifying high-priority needs, introducing a simple API to address them, and using tools like Kratix to define on-demand services through promises that can then be iterated on over time. Taking this approach can help reduce toil and introduce structure while maintaining flexibility during the initial platform development.
Providing as-a-Service Across Multi-Cluster KubernetesAbigail Bangser
This document discusses challenges that platform teams face in self-hosting the Waypoint continuous delivery server. It begins by explaining how teams get started quickly with self-hosting via the CLI but then face issues as usage grows. This leads platform teams through evolving architectures from a single server to Kubernetes deployment to multi-cluster architectures. Each new approach aims to improve scalability, reliability and manageability but also introduces new challenges. The document suggests that Kratix can help platform teams address these challenges by providing a framework to modularize their Waypoint offering and deliver capabilities over time.
Platforms aren't tools, they are experiences. And Kubernetes isn’t a platfor...Abigail Bangser
Kubernetes took the world by storm and doesn’t appear to be slowing down. Its scalable architecture and extensible API has enabled organisations of many shapes and sizes. That doesn’t make Kubernetes a platform, but it is a fantastic base for one.
Flipping the script: How to take the first step towards internal developer pl...Abigail Bangser
This is a talk about why you should be investing in the API for your internal platform and how you can get started with the existing user experiences in your org to drive the adoption of the new API.
Tutorial Becoming a Kubernetes Developer_ Writing Your First OperatorAbigail Bangser
This is the slide deck used to present: https://kccncna2022.sched.com/event/182F1/tutorial-becoming-a-kubernetes-developer-writing-your-first-operator-abby-bangser-syntasso
It is supported by:
https://abangser.gitbook.io/kubecon2022
This is a journey through three attempts to improve observability which are used to highlight the difference between "better monitoring" and "observability".
Slides used at CRAFT Conf 2018 in Budapest. This is a talk about the cultural shifts and communication needs/challenges associated with moving into the public cloud for the first time.
7 Most Powerful Solar Storms in the History of Earth.pdfEnterprise Wired
Solar Storms (Geo Magnetic Storms) are the motion of accelerated charged particles in the solar environment with high velocities due to the coronal mass ejection (CME).
INDIAN AIR FORCE FIGHTER PLANES LIST.pdfjackson110191
These fighter aircraft have uses outside of traditional combat situations. They are essential in defending India's territorial integrity, averting dangers, and delivering aid to those in need during natural calamities. Additionally, the IAF improves its interoperability and fortifies international military alliances by working together and conducting joint exercises with other air forces.
Best Practices for Effectively Running dbt in Airflow.pdfTatiana Al-Chueyr
As a popular open-source library for analytics engineering, dbt is often used in combination with Airflow. Orchestrating and executing dbt models as DAGs ensures an additional layer of control over tasks, observability, and provides a reliable, scalable environment to run dbt models.
This webinar will cover a step-by-step guide to Cosmos, an open source package from Astronomer that helps you easily run your dbt Core projects as Airflow DAGs and Task Groups, all with just a few lines of code. We’ll walk through:
- Standard ways of running dbt (and when to utilize other methods)
- How Cosmos can be used to run and visualize your dbt projects in Airflow
- Common challenges and how to address them, including performance, dependency conflicts, and more
- How running dbt projects in Airflow helps with cost optimization
Webinar given on 9 July 2024
The Rise of Supernetwork Data Intensive ComputingLarry Smarr
Invited Remote Lecture to SC21
The International Conference for High Performance Computing, Networking, Storage, and Analysis
St. Louis, Missouri
November 18, 2021
Quantum Communications Q&A with Gemini LLM. These are based on Shannon's Noisy channel Theorem and offers how the classical theory applies to the quantum world.
Best Programming Language for Civil EngineersAwais Yaseen
The integration of programming into civil engineering is transforming the industry. We can design complex infrastructure projects and analyse large datasets. Imagine revolutionizing the way we build our cities and infrastructure, all by the power of coding. Programming skills are no longer just a bonus—they’re a game changer in this era.
Technology is revolutionizing civil engineering by integrating advanced tools and techniques. Programming allows for the automation of repetitive tasks, enhancing the accuracy of designs, simulations, and analyses. With the advent of artificial intelligence and machine learning, engineers can now predict structural behaviors under various conditions, optimize material usage, and improve project planning.
Measuring the Impact of Network Latency at TwitterScyllaDB
Widya Salim and Victor Ma will outline the causal impact analysis, framework, and key learnings used to quantify the impact of reducing Twitter's network latency.
TrustArc Webinar - 2024 Data Privacy Trends: A Mid-Year Check-InTrustArc
Six months into 2024, and it is clear the privacy ecosystem takes no days off!! Regulators continue to implement and enforce new regulations, businesses strive to meet requirements, and technology advances like AI have privacy professionals scratching their heads about managing risk.
What can we learn about the first six months of data privacy trends and events in 2024? How should this inform your privacy program management for the rest of the year?
Join TrustArc, Goodwin, and Snyk privacy experts as they discuss the changes we’ve seen in the first half of 2024 and gain insight into the concrete, actionable steps you can take to up-level your privacy program in the second half of the year.
This webinar will review:
- Key changes to privacy regulations in 2024
- Key themes in privacy and data governance in 2024
- How to maximize your privacy program in the second half of 2024
Fluttercon 2024: Showing that you care about security - OpenSSF Scorecards fo...Chris Swan
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge.
You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter.
The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
Blockchain technology is transforming industries and reshaping the way we conduct business, manage data, and secure transactions. Whether you're new to blockchain or looking to deepen your knowledge, our guidebook, "Blockchain for Dummies", is your ultimate resource.
YOUR RELIABLE WEB DESIGN & DEVELOPMENT TEAM — FOR LASTING SUCCESS
WPRiders is a web development company specialized in WordPress and WooCommerce websites and plugins for customers around the world. The company is headquartered in Bucharest, Romania, but our team members are located all over the world. Our customers are primarily from the US and Western Europe, but we have clients from Australia, Canada and other areas as well.
Some facts about WPRiders and why we are one of the best firms around:
More than 700 five-star reviews! You can check them here.
1500 WordPress projects delivered.
We respond 80% faster than other firms! Data provided by Freshdesk.
We’ve been in business since 2015.
We are located in 7 countries and have 22 team members.
With so many projects delivered, our team knows what works and what doesn’t when it comes to WordPress and WooCommerce.
Our team members are:
- highly experienced developers (employees & contractors with 5 -10+ years of experience),
- great designers with an eye for UX/UI with 10+ years of experience
- project managers with development background who speak both tech and non-tech
- QA specialists
- Conversion Rate Optimisation - CRO experts
They are all working together to provide you with the best possible service. We are passionate about WordPress, and we love creating custom solutions that help our clients achieve their goals.
At WPRiders, we are committed to building long-term relationships with our clients. We believe in accountability, in doing the right thing, as well as in transparency and open communication. You can read more about WPRiders on the About us page.
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
Comparison Table of DiskWarrior Alternatives.pdfAndrey Yasko
To help you choose the best DiskWarrior alternative, we've compiled a comparison table summarizing the features, pros, cons, and pricing of six alternatives.
Quality Patents: Patents That Stand the Test of TimeAurora Consulting
Is your patent a vanity piece of paper for your office wall? Or is it a reliable, defendable, assertable, property right? The difference is often quality.
Is your patent simply a transactional cost and a large pile of legal bills for your startup? Or is it a leverageable asset worthy of attracting precious investment dollars, worth its cost in multiples of valuation? The difference is often quality.
Is your patent application only good enough to get through the examination process? Or has it been crafted to stand the tests of time and varied audiences if you later need to assert that document against an infringer, find yourself litigating with it in an Article 3 Court at the hands of a judge and jury, God forbid, end up having to defend its validity at the PTAB, or even needing to use it to block pirated imports at the International Trade Commission? The difference is often quality.
Quality will be our focus for a good chunk of the remainder of this season. What goes into a quality patent, and where possible, how do you get it without breaking the bank?
** Episode Overview **
In this first episode of our quality series, Kristen Hansen and the panel discuss:
⦿ What do we mean when we say patent quality?
⦿ Why is patent quality important?
⦿ How to balance quality and budget
⦿ The importance of searching, continuations, and draftsperson domain expertise
⦿ Very practical tips, tricks, examples, and Kristen’s Musts for drafting quality applications
https://www.aurorapatents.com/patently-strategic-podcast.html
Choose our Linux Web Hosting for a seamless and successful online presencerajancomputerfbd
Our Linux Web Hosting plans offer unbeatable performance, security, and scalability, ensuring your website runs smoothly and efficiently.
Visit- https://onliveserver.com/linux-web-hosting/
Observability - Experiencing the “why” behind the jargon (FlowCon 2019)
1. @A_Bangser @FlowConFR #FlowCon
My slides are / will be available for you at:
@A_Bangser @FlowConFR #FlowCon
Observability -
Experiencing the “why” behind the jargon
Abby Bangser
https://www.slideshare.net/AbigailBangser
7. @A_Bangser @FlowConFR #FlowCon
“measure of how well” means observability is a scale
How easy is it to answer a new question without deploying new code?
Incident
triage
Incident
triage
happening?!
observability observability
observability
13. @A_Bangser @FlowConFR #FlowCon
So you might be thinking… “right, monitoring”
https://bravenewgeek.com/wp-content/uploads/2019/10/monitoring_vs_observability_overlay-1024x539.png
14. @A_Bangser @FlowConFR #FlowCon
So you might be thinking… “right, monitoring”
https://bravenewgeek.com/wp-content/uploads/2019/10/monitoring_vs_observability_overlay-1024x539.png
15. @A_Bangser @FlowConFR #FlowCon
So you might be thinking… “right, monitoring”
https://bravenewgeek.com/wp-content/uploads/2019/10/monitoring_vs_observability_overlay-1024x539.png
16. @A_Bangser @FlowConFR #FlowCon
True observability is discovering new behaviours
https://bravenewgeek.com/wp-content/uploads/2019/10/monitoring_vs_observability_overlay-1024x539.png
18. @A_Bangser @FlowConFR #FlowCon
Characteristics of what generates valuable outputs
https://thenewstack.io/observability-a-3-year-retrospective/
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be exploratory
19. @A_Bangser @FlowConFR #FlowCon
Characteristics of what generates valuable outputs
https://thenewstack.io/observability-a-3-year-retrospective/
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be exploratory
ByTwitter,CCBY4.0,
https://commons.wikimedia.org/w/index.php?curid=76921548
20. @A_Bangser @FlowConFR #FlowCon
Let’s understand a couple of these through examples
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be exploratory
21. @A_Bangser @FlowConFR #FlowCon
Let’s understand a couple of these through examples
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be exploratory
22. @A_Bangser @FlowConFR #FlowCon
The promise of monitoring vs my reality
My rollercoaster journey with understanding metrics and
pre-aggregation starts back in 2016...
23. @A_Bangser @FlowConFR #FlowCon
Monitorama 2016 - an awakening
Lessons include…
➔ It is not just testing that is dead
➔ Wow! There is a world of available data I have no idea about
➔ These tools are so cool...wait, what are these tools?
24. @A_Bangser @FlowConFR #FlowCon
Metrics can track success (and failure) of changes made
https://landing.google.com/sre/sre-book/chapters/monitoring-distributed-systems/#xref_monitoring_golden-signals
25. @A_Bangser @FlowConFR #FlowCon
An ask:
I want to monitor live
systems
An opportunity:
Help create a
client’s first cloud
infrastructure
@A_Bangser @FlowConFR #FlowCon
29. @A_Bangser @FlowConFR #FlowCon@A_Bangser @FlowConFR #FlowCon
Two years and many projects later Hobbsy had a plan
Track latency over 4 weeks and alert when current trends exceed 2 standard deviations
2standarddeviations
30. @A_Bangser @FlowConFR #FlowCon@A_Bangser @FlowConFR #FlowCon
Two years and many projects later Hobbsy had a plan
Track latency over 4 weeks and alert when current trends exceed 2 standard deviations
2standarddeviations
31. @A_Bangser @FlowConFR #FlowCon
To do this at MOO
s / MOO / any company over a few years old /
➔ 40 services
➔ 4 core languages
➔ 3 eras of architectural decisions
➔ 2 transport protocols (http and gRPC)
32. @A_Bangser @FlowConFR #FlowCon
To do this at MOO
s / MOO / any company over a few years old /
➔ 40 services
➔ 4 core languages
➔ 3 eras of architectural decisions
➔ 2 transport protocols (http and gRPC)
...and a partridge in a pear tree
36. @A_Bangser @FlowConFR #FlowCon@A_Bangser @FlowConFR #FlowCon
Our data collection made certain assumptions which
in the end required re-collecting in a different way
37. @A_Bangser @FlowConFR #FlowCon@A_Bangser @FlowConFR #FlowCon
How histograms gets generated in a time series DB
le= 0.05
http_requests_seconds_bucket
le= 0.1 le= 0.5 le= 1 le= 5 le= +inf
* “le” stands for “less than or equal to”
38. @A_Bangser @FlowConFR #FlowCon@A_Bangser @FlowConFR #FlowCon
How histograms gets generated in a time series DB
le= 0.05
http_requests_seconds_bucket
le= 0.1 le= 0.5 le= 1 le= 5 le= +inf
* “le” stands for “less than or equal to”
www.moo.com in 0.25 seconds
39. @A_Bangser @FlowConFR #FlowCon@A_Bangser @FlowConFR #FlowCon
How histograms gets generated in a time series DB
le= 0.05
http_requests_seconds_bucket
le= 0.1 le= 0.5 le= 1 le= 5 le= +inf
* “le” stands for “less than or equal to”
www.moo.com in 0.25 seconds
40. @A_Bangser @FlowConFR #FlowCon@A_Bangser @FlowConFR #FlowCon
How histograms gets generated in a time series DB
le= 0.05
http_requests_seconds_bucket
le= 0.1 le= 0.5 le= 1 le= 5 le= +inf
* “le” stands for “less than or equal to”
www.moo.com/big_file in 5 seconds
www.moo.com in 0.25 seconds
41. @A_Bangser @FlowConFR #FlowCon@A_Bangser @FlowConFR #FlowCon
How histograms gets generated in a time series DB
le= 0.05
http_requests_seconds_bucket
le= 0.1 le= 0.5 le= 1 le= 5 le= +inf
* “le” stands for “less than or equal to”
www.moo.com/big_file in 5 seconds
www.moo.com in 0.25 seconds
49. @A_Bangser @FlowConFR #FlowCon@A_Bangser @FlowConFR #FlowCon
So, while consistent metrics
trending over time was a big
step forward...
In retrospect,
these experiences were
not mature observability
50. @A_Bangser @FlowConFR #FlowCon
Why avoid pre-aggregation?
Because you can never regain the original context and detail,
you can only ever ask predetermined questions
51. @A_Bangser @FlowConFR #FlowCon
Let’s understand a couple of these through examples
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be exploratory
52. @A_Bangser @FlowConFR #FlowCon
Data is not the same as information
Step one is accepting that while sentences may be readable.
<key : value> pairs are more easily queried.
56. @A_Bangser @FlowConFR #FlowCon
So then we backfilled in structure
grok {
match => [
"Request",
"%{URIPROTO:request_uri_scheme}://
%{HOSTNAME:request_uri_host}(?::%{POSINT:request_uri_port})
?%{URIPATH:request_uri_path}(?:%{URIPARAM:request_uri_query})?"
]}
}
57. @A_Bangser @FlowConFR #FlowCon
And of course, from there we wanted more
mutate {
split => { "uri_array" => "/"}
add_field => {
"uri_root" => ["/%{[uri_array][1]}"]
"uri_first" => ["/%{[uri_array][2]}"]
"uri_second" => ["/%{[uri_array][3]}"]
"uri_root_first" => "%{uri_root}%{uri_first}"
"uri_root_second" => "%{uri_root}%{uri_first}%{uri_second}"
}
86. @A_Bangser @FlowConFR #FlowCon
In order to combate tribal knowledge based guessing
when debugging our complex systems, we need:
A low friction way to add fields to your
logs for structure and searchability
Allowing application and user context to
be wrapped in a business context
CustomerID:234567VersionOfApp:2
RequestedUri:www.
87. @A_Bangser @FlowConFR #FlowCon
Let’s understand a couple of these through examples
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be exploratory
89. @A_Bangser @FlowConFR #FlowCon
Hmmm, a warning alert has come in
This is an automated alert based on a warning production service sending a high percent of 500’s in production!
102. @A_Bangser @FlowConFR #FlowCon
Let’s break down what this dashboard shows
Enhanced Images
Original Images
Enhanced Images
Enhanced and resized
Request Counts Response Latency
107. @A_Bangser @FlowConFR #FlowCon
Why ditch the dashboards?
The scar tissue of your past outages is not a sufficient
replacement for the creativity required to investigate your
future incidents
https://www.needpix.com/photo/907639/images-leash-leash-polaroid-free-pictures-free-photos-free-images-royalty-free
108. @A_Bangser @FlowConFR #FlowCon
Let’s revisit those characteristics
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be
exploratory
ByTwitter,CCBY4.0,https://commons.wikimedia.org/w/index.php?curid=80936515
109. @A_Bangser @FlowConFR #FlowCon
Let’s revisit those characteristics
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be
exploratory
ByTwitter,CCBY4.0,https://commons.wikimedia.org/w/index.php?curid=80936515
The only way to ask new questions
is to keep the original raw data
available and queryable
110. @A_Bangser @FlowConFR #FlowCon
Let’s revisit those characteristics
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be
exploratory
ByTwitter,CCBY4.0,https://commons.wikimedia.org/w/index.php?curid=80936515
Make data easy to
add details to and
easy to query
111. @A_Bangser @FlowConFR #FlowCon
Let’s revisit those characteristics
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be
exploratory
ByTwitter,CCBY4.0,https://commons.wikimedia.org/w/index.php?curid=80936515
Empower creative
and shared
exploration based
on business context
112. @A_Bangser @FlowConFR #FlowCon
Let’s revisit those characteristics
➔ raw events
➔ no pre-aggregation
➔ structured data
➔ arbitrarily wide events
➔ schema-less-ness
➔ high cardinality dimensions
➔ oriented around the lifecycle of the request
➔ batched up context
➔ static dashboards don’t work, it must be
exploratory
ByTwitter,CCBY4.0,https://commons.wikimedia.org/w/index.php?curid=80936515
The only way to ask new questions
is to keep the original raw data
available and queryable
Make data easy to
add details to and
easy to query
Empower creative
and shared
exploration based
on business context
113. @A_Bangser @FlowConFR #FlowCon
QA
TWU
Looking back journeys are never clear, so why do we
still expect them to be when we start a new one?
Political
Science Major
Data analysis for
investments
A desire to
learn how to
code
Automation
FTW!
An “analyst”
computer
A “DevOps”
friend
engaged me
in his work
onitorama
An infrastructure
project
Platform
Engineering @
Professional
scuba diver
A (slight)
obsession with
observability
115. @A_Bangser @FlowConFR #FlowCon
➔ All of tech and product is now asking more interesting questions
➔ We are expecting more of our tooling
➔ We are building new awareness about our services and system
Start where you are.
Use what you have.
Do what you can.
- Arthur Ashe