I gave this talk at Krakow/Poland DevOPS meetup. It was a lightning talk covering subject of High Availability solutions, architecture, planning and deploying.
The document provides an overview of microservices architecture. It discusses key characteristics of microservices such as each service focusing on a specific business capability, decentralized governance and data management, and infrastructure automation. It also compares microservices to monolithic and SOA architectures. Some design styles enabled by microservices like domain-driven design, event sourcing, and functional reactive programming are also covered at a high level. The document aims to introduce attendees to microservices concepts and architectures.
This document provides an overview of an IBM Security QRadar SIEM Foundations course. The course covers topics such as QRadar data flow architecture, deployment options, navigating the user interface, building searches and reports, managing assets and rules. It describes how QRadar integrates various security tools and uses correlation to detect threats. The document highlights how QRadar provides security intelligence through network flow analysis, cognitive analytics, and an open ecosystem.
Connecting Many VPCs: Network Design Patterns at Scale (ARC405) - AWS re:Inve...Amazon Web Services
In this session, we show you how to design connectivity between many VPCs and how new services interact with network architectures. We review common design patterns such as shared services VPCs, transit VPCs, private link, firewalls, and more. We also cover solutions to common challenges, such as VPN sprawl, keeping up with VPC automation, sharing services, and network segmentation at scale for hundreds of VPCs. Please join us for a speaker meet-and-greet following this session at the Speaker Lounge (ARIA East, Level 1, Willow Lounge). The meet-and-greet starts 15 minutes after the session and runs for half an hour.
AWS Core Services Overview, Immersion Day Huntsville 2019Amazon Web Services
The document provides an overview of AWS core services including compute, storage, database, analytics, machine learning, IoT, and mobile services. It discusses AWS' breadth and depth of services across infrastructure, application services, management tools, and developer tools. It also highlights AWS' leadership in cloud computing with the largest customer base and most comprehensive set of services and features.
Kevin Huang: AWS San Francisco Startup Day, 9/7/17
Architecture: When, how, and if to adopt microservices - Microservices are not for everyone! If you're a small shop, a monolith provides a great amount of value and reduces the complexities involved. However as your company grows, this monolith becomes more difficult to maintain. We’ll look at how microservices allow you to easily deploy and debug atomic pieces of infrastructure which allows for increased velocity in reliable, tested, and consistent deploys. We’ll look into key metrics you can use to identify the right time to begin the transition from monolith to microservices.
Resiliency-and-Availability-Design-Patterns-for-the-CloudAmazon Web Services
We have traditionally built robust software systems by trying to avoid mistakes and by dodging failures when they occur in production or by testing parts of the system in isolation from one another. Modern methods and techniques take a very different approach based on resiliency, which promotes embracing failure instead of trying to avoid it. Resilient architectures enhance observability, leverage well-known patterns such as graceful degradation, timeouts and circuit breakers. In this session, will review the most useful patterns for building resilient software systems and especially show the audience how they can benefit from the patterns.
In this session we’ll take a high-level overview of AWS Lambda, a serverless compute platform that has changed the way that developers around the world build applications. We’ll explore how Lambda works under the hood, the capabilities it has, and how it is used. By the end of this talk you’ll know how to create Lambda based applications and deploy and manage them easily.
Speaker: Chris Munns - Principal Developer Advocate, AWS Serverless Applications, AWS
클라우드 네이티브 IT를 위한 4가지 요소와 상관관계 - DevOps, CI/CD, Container, 그리고 MSAVMware Tanzu Korea
최근 IT 시장은 ‘클라우드 네이티브’ 라는 컨셉을 적극적으로 받아들이면서 혁신의 속도를 높이기 위해 여러가지 노력을 기울이고 있습니다. 본 세션에서는 ‘클라우드 네이티브’ 를 이루는 4가지 요소인 DevOps, CICD, Container, MSA 를 간략하게 살펴보고 MSA 가 나머지 클라우드 네이티브 3 요소와 어떻게 상호작용하여 고객 여러분의 비즈니스에 도움이 되는지 알아봅니다. 그리고 MSA 로 이행하기 위한 조직면에서의 요건과 기술 면에서의 요건을 살펴봅니다.
Distributed Transactions is a key concept for Micro Services based Apps and Saga Design Pattern helps out over here. However, developers struggle to shift their mindset from CRUD based design to Event Sourcing / CQRS concept. To solve this problem we are introducing the concept of Event Storming and Event Storming Process map.
Saga about distributed business transactions in microservices worldMikalai Alimenkou
Most of people nowadays think microservices architecture is a great way to build any system. They visit conference talks, read books and review tutorials, where ‘hello world’ applications are built just in several minutes using microservices approach. But the reality is not so wonderful and one of the biggest pain is hidden inside distributed business transactions. In monolith application this topic is almost completely covered with DB level transactions. In distributed world you have to face many issues trying to implement reliable and consistent business logic.
In this talk we will review different types of problems related to distributed business transactions, popular SAGA pattern, frameworks and techniques to simplify your life without compromising quality of the system.
The quest for the insight-driven enterprise has spurned a mass exodus to the cloud. But cloud data ecosystems can be very complex with multiple data storage and processing options.
These slides-based on the webinar featuring leading IT analyst firm EMA, Amazon Web Services (AWS), and Trifacta--will help you: understand technology trends that simplify your analytics modernization journey; learn best practices to operationalize data management on AWS; establish operational excellence leveraging AWS data storage and processing; accelerate time-to-value for analytics projects with data preparation on AWS.
This document discusses architecting applications on AWS for high availability across multiple regions. It begins by reviewing some notable outages and what is covered by typical SLAs. It then provides an overview of initial steps like using auto scaling, ELB, and CloudWatch. It discusses moving beyond a single availability zone to multiple zones. The main topic is setting up applications across multiple AWS regions for redundancy in case an entire region fails. Key services mentioned for high availability architectures are S3, CloudFront, ELB, CloudWatch, and SQS.
Deep Dive on New Amazon EC2 Instances and Virtualization Technologies - AWS O...Amazon Web Services
Learning Objectives:
- Learn how to get started with GuardDuty and build cloud-scale threat defense across your AWS accounts
- Learn how to continuously monitor your applications and services running in the AWS Cloud
- Learn about the types of GuardDuty threat detections and discuss automation opportunities
Building Cloud-Native App Series - Part 2 of 11
Microservices Architecture Series
Event Sourcing & CQRS,
Kafka, Rabbit MQ
Case Studies (E-Commerce App, Movie Streaming, Ticket Booking, Restaurant, Hospital Management)
Most organizations have heard of the cloud, but not everyone is at the same stage on their cloud journey. This SlideShare overviews how to best leverage the cloud, the multitude of options and the typical stages of transition. Also outlined are the steps you can take to get where you want to go on your cloud journey faster and more efficiently.
The document discusses the AWS Cloud Adoption Framework (CAF) which is used to help organizations accelerate their journey to cloud adoption. It outlines the 4 stages of cloud adoption: retire technical debt, project, foundation, and migration/optimization. The CAF focuses on 6 perspectives - business value, people roles and readiness, governance and control, applications and infrastructure, security and risk, and operations. For each perspective, it identifies key stakeholders and questions organizations should consider to develop cloud capabilities. The CAF provides a holistic approach to cloud adoption by addressing business, people, and technical factors.
The document discusses microservice architecture, including concepts, benefits, principles, and challenges. Microservices are an architectural style that structures an application as a collection of small, independent services that communicate with each other, often using RESTful API's. The approach aims to overcome limitations of monolithic architectures like scalability and allow for independent deployments. The key principles include organizing services around business domains, automating processes, and designing services to be independently deployable.
High Availability (HA) Explained - second editionMaciej Lasyk
I gave this talk at one of the biggest Linux conferences in Poland: 11 Liux Session that took place in Wrocław on 5/6-04-2014. It was a lightning talk covering subject of High Availability solutions, architecture, planning and deploying.
Bulletproof Kafka with Fault Tree Analysis (Andrey Falko, Lyft) Kafka Summit ...confluent
We recently learned about “Fault Tree Analysis” and decided to apply the technique to bulletproof our Apache Kafka deployments. In this talk, learn about fault tree analysis and what you should focus on to make your Apache Kafka clusters resilient.
This talk should provide a framework for answers the following common questions a Kafka operator or user might have:
What guarantees can I promise my users?
What should my replication factor?
What should the ISR setting be?
Should I use RAID or not?
Should I use external storage such as EBS or local disks?
Bulletproof Kafka with Fault Tree Analysis (Andrey Falko, Lyft) Kafka Summit ...confluent
We recently learned about “Fault Tree Analysis” and decided to apply the technique to bulletproof our Apache Kafka deployments. In this talk, learn about fault tree analysis and what you should focus on to make your Apache Kafka clusters resilient. This talk should provide a framework for answers the following common questions a Kafka operator or user might have:
-What guarantees can I promise my users?
-What should my replication factor?
-What should the ISR setting be?
-Should I use RAID or not?
-Should I use external storage such as EBS or local disks?
NoSQL Revolution: Under the Covers of Distributed Systems at Scale (SPOT401) ...Amazon Web Services
The Dynamo paper started a revolution in distributed systems. The contributions from this paper are still impacting the design and practices of some of the world's largest distributed systems, including those at Amazon.com and beyond. Building distributed systems is hard, but our goal in this session is to simplify the complexity of this topic to empower the hacker in you! Have you been bitten by the eventual consistency bug lately? We show you how to tame eventual consistency and make it a great scaling asset. As you scale up, you must be ready to deal with node, rack, and data center failure. We share insights on how to limit the blast radius of the individual components of your system, battle tested techniques for simulating failures (network partitions, data center failure), and how we used core distributed systems fundamentals to build highly scalable, performance, durable, and resilient systems. Come watch us uncover the secret sauce behind Amazon DynamoDB, Amazon SQS, Amazon SNS, and the fundamental tenents that define them as Internet scale services. To turn this session into a hacker's dream, we go over design and implementation practices you can follow to build an application with virtually limitless scalability on AWS within an hour. We even share insights and secret tips on how to make the most out of one of the services released during the morning keynote.
Scaling your Kafka streaming pipeline can be a pain - but it doesn’t have to ...HostedbyConfluent
"Kafka data pipeline maintenance can be painful.
It usually comes with complicated and lengthy recovery processes, scaling difficulties, traffic ‘moodiness’, and latency issues after downtimes and outages.
It doesn’t have to be that way!
We’ll examine one of our multi-petabyte scale Kafka pipelines, and go over some of the pitfalls we’ve encountered. We’ll offer solutions that alleviate those problems, and go over comparisons between the before and after . We’ll then explain why some common sense solutions do not work well and offer an improved, scalable and resilient way of processing your stream.
We’ll cover:
• Costs of processing in stream compared to in batch
• Scaling out for bursts and reprocessing
• Making the tradeoff between wait times and costs
• Recovering from outages
• And much more…"
The document discusses MySQL Group Replication, which is a plugin that provides multi-master replication capability for MySQL. It allows data to be replicated between multiple MySQL servers so that they can stay in sync. The replication works by having each server send transaction writesets to other servers through a group communication system, and then each server certifies and applies the changes locally in an asynchronous manner.
I gave this presentation at the Oracle InSync09 Conference in Sydney in May 2009. It's all about Oracle Coherence - Napster for the enterprise - and how you can use it to get the most out of your applications.
Use Coherence like our customers are doing today;
- Sharing web session state across multiple portals
- Caching the results of calls to back end systems
- State management for stateful services, bring the processing to the data
- Process large XML payloads more quickly and efficiently
The document discusses various topics related to optimizing MySQL performance, including database engines, basic settings, useful utilities, and queries. It begins by describing different MySQL storage engines like InnoDB, MyISAM, Memory, NDB and others. It then covers important configuration settings like query_cache_size, innodb_buffer_pool_size, and others. Utilities for MySQL performance analysis and tuning are presented, such as tuning-primer.sh, mysql-tuner.pl, and tools from the maatkit collection. Best practices for query optimization are also covered, such as using ORM frameworks, proper indexing, and making queries concrete. The document concludes by providing contact details for the author.
The document discusses continuous deployment practices at Outbrain, an online content recommendation company. It emphasizes the importance of short feedback loops between code changes and user exposure through practices like deploying new code multiple times daily and testing code changes automatically before deployment. Infrastructure is codified and deployment is automated using tools like Chef to further streamline the process.
Should you read Kafka as a stream or in batch? Should you even care? | Ido Na...HostedbyConfluent
This document discusses whether it is better to process data using a stream or batch approach. It describes how one company evolved their data pipeline from a micro-batch streaming process to a batch approach. The streaming process was very expensive, costing $400,000 per year to run. It also had issues with wasted resources during idle times, slow processing during bursts of data, and long recovery times from outages. The company rearchitected the process to use discrete time windows run in isolated batch jobs. This new batch approach reduced costs by 60% to $160,000 per year and improved processing efficiency and outage recovery times.
Microservices 5 things i wish i'd known code motionVincent Kok
Microservices are hot! A lot of companies are experimenting with this architectural pattern that greatly benefits the software development process. When adopting new patterns we always encounter that moment where we think 'if only I knew this three months ago'. This talk will be a sneak peak into the world of microservices at Atlassian and reveal what we've learned about microservices: how to arrange, configure and build your code efficiently; deployment and testing; and how to operate effectively in this environment. In this talk you will learn how to immediately apply five simple strategies.
Microservices: 5 things I wish I'd known - Vincent Kok - Codemotion Amsterdam...Codemotion
Microservices are hot! A lot of companies are experimenting with this architectural pattern that greatly benefits the software development process. When adopting new patterns we always encounter that moment where we think 'if only I knew this three months ago'. This talk will be a sneak peak into the world of microservices at Atlassian and reveal what we've learned about microservices: how to arrange, configure and build your code efficiently; deployment and testing; and how to operate effectively in this environment. In this talk you will learn how to immediately apply five simple strategies.
This document provides an overview of performance tuning for Java applications. It discusses top-down and bottom-up performance analysis approaches. It also covers choosing the right garbage collector and JVM tuning basics like calculating allocation rates and live data size from GC logs. The document shows examples of tuning JVM settings for latency using CMS and G1 collectors as well as tuning for throughput using ParallelOldGC.
Science Of Saving With AWS Reserved Instances - 9/11/14Cloudability
Choosing the right Reserved Instances isn’t an art, it’s a science. Perfecting that science could save you up to 65% on your AWS bill.
In this presentation, you’ll learn the math and science used by thousands of AWS users to optimize their Reserved Instance portfolios.
Topics include:
- Identifying the right Reserved Instances for your company's usage
- Avoiding common Reserved Instance pitfalls
- Maintaining long-term savings as your usage changes
Using Kubernetes to deliver a “serverless” serviceDoKC
Serverless promises to change the way we consume software. It allows us to potentially pay for only that which we use and can help drive down operational costs to the minimal amount of resources necessary.
Architecting for serverless requires a unique look at app logic and the way it is deployed. It takes a combination of the logical and physical worlds. An architectural pattern has emerged where we can scale ephemeral compute separate from services that need to persist.
We use Kubernetes to deliver exactly this. A “serverless” experience that is driven and enabled by compute pods and storage pods. We also have used our experience running thousands of database clusters on Kubernetes to automate the operational expertise of managing a distributed database.
In this talk, we will take a dive deep into the architecture of our application and share:
* A definition and outline of the challenges of serverless
* How we reworked our logic for a serverless approach
* How we use Kubernetes to gain serverless autoscaling
This talk was given by Jim Walker for DoK Day Europe @ KubeCon 2022.
Présentation du FME World Tour du 13 avril 2017 à QuebecGuillaume Genest
Présentation de l'événement FME World Tour 2017 qui a eu lieu le 13 avril 2017 à Québec. Découvrez les nouveautés de FME 2017 et FME Server 2017. Voyez les trucs et astuces pour optimiser la performance de vos workbench, une solution pour comparer des workspaces ensemble, un portail de chargement et téléchargement de données avec FME Server ainsi que des outils de validation et correction topologique.
This document discusses the history and development of Docker. It notes that Docker was originally created at dotCloud as the engine for their Platform as a Service (PaaS), but in 2013 as PaaS times were hard, Docker was open sourced. Docker was based on LXC and created for a single purpose. dotCloud then pivoted to create Docker Inc. and make Docker their main product. The document also discusses Docker 1.11's integration with runC and systemd, as well as the transition to using the Open Container Initiative specification.
Programowanie AWSa z CLI, boto, Ansiblem i libcloudemMaciej Lasyk
The document describes a session that demonstrates how to program AWS using the AWS CLI, Boto, and Ansible. It provides an agenda for the session that includes a short AWS introduction, demonstrations of the AWS console, AWS CLI, AWS shell, Boto library, Ansible configuration management tool, and Libcloud library. Contact information is also provided for learning more about AWS programming and joining the training organization.
This document discusses Linux security and SELinux. It provides an overview of SELinux and how it works to provide mandatory access control on Linux systems. It discusses how SELinux labels processes and files to confine programs and prevent unauthorized access. It also discusses using SELinux with Docker containers to provide security isolation between containers.
Under the Dome (of failure driven pipeline)Maciej Lasyk
The document discusses various topics related to DevOps including:
1. Different types of shells (login, non-login, interactive, non-interactive, su, sudo su, sudo -i, sudo /bin/bash, sudo -s) and how they affect environment variables and profile files.
2. Stories of organizational "anti-types" that go against DevOps principles like not seeing the need for operations teams.
3. How automation, consistency, and reducing errors leads to stable environments and less unplanned work, allowing teams to focus on delivery.
This document discusses integrating security into DevOps practices through continuous delivery. It proposes including security automation and monitoring at each stage of the software development pipeline from development through production. Specific techniques mentioned include performing continuous security scanning, integrating security testing with other testing stages, automating security tasks using tools like Ansible, and sharing security data and lessons learned across teams to improve processes over time. The overall message is that security should be built into delivery rather than treated separately to avoid slowing software releases while still maintaining quality.
Orchestrating docker containers at scale (#DockerKRK edition)Maciej Lasyk
Slightly different version (original is here http://www.slideshare.net/d0cent/orchestrating-docker-containersatscale). This version was presented during first #Docker meetup in Kraków / Poland.
Orchestrating docker containers at scale (PJUG edition)Maciej Lasyk
Slightly changed version (original is here http://www.slideshare.net/d0cent/orchestrating-docker-containersatscale). This version was presented during Polish Java User Group meetup JavaCamp#13 in Kraków / Poland.
Orchestrating Docker containers at scaleMaciej Lasyk
Many of us already poked around Docker. Let's recap what we know and then think what do we know about scaling apps & whole environments which are Docker - based? Should we PaaS, IaaS or go with bare? Which tools to use on a given scale?
This document contains a list of various tools related to terminals, privacy, communication, productivity, and mobile topics. It discusses terminal emulators like guake and iterm2, VPN services like OpenVPN, messaging clients like IRC and XMPP, note taking apps like Evernote and Geeknote, and more. It concludes by inviting questions about any of the topics mentioned.
How could one create very sophisticated, open - source based monitoring solution that is very scalable and easy to deploy?
I gave this talk during on of the biggest Linux conferences in Poland: 11 Linux Session which took place in Wrocław on 5/6-04-2013
I gave this talk during first Infosec meetup in Kraków/Poland on 13th March 2014. After viewing this presentation you'll know how and why you should use SELinux (or others LSMs).
Is Red Hat / Fedora / Centos ready for lightweight Docker containers? Is Docker secure enough? How about SELinux? How could we deploy Jboss or Django within Docker / RHEL?
I gave this talk at DevOPS meetup in Krakow at 2014-02-26.
How to run system administrator recruitment process? By creating platform based on open source parts in just 2 nights! I gave this talk in Poland / Kraków OWASP chapter meeting on 17th Octomber 2013 at our local Google for Entrepreneurs site. It's focused on security and also shows how to create recruitment process in CTF / challenge way.
This story covers mostly security details of this whole platform. There's great chance, that I will give another talk about this system but this time focusing on technical details. Stay tuned ;)
Performance Budgets for the Real World by Tammy EvertsScyllaDB
Performance budgets have been around for more than ten years. Over those years, we’ve learned a lot about what works, what doesn’t, and what we need to improve. In this session, Tammy revisits old assumptions about performance budgets and offers some new best practices. Topics include:
• Understanding performance budgets vs. performance goals
• Aligning budgets with user experience
• Pros and cons of Core Web Vitals
• How to stay on top of your budgets to fight regressions
AC Atlassian Coimbatore Session Slides( 22/06/2024)apoorva2579
This is the combined Sessions of ACE Atlassian Coimbatore event happened on 22nd June 2024
The session order is as follows:
1.AI and future of help desk by Rajesh Shanmugam
2. Harnessing the power of GenAI for your business by Siddharth
3. Fallacies of GenAI by Raju Kandaswamy
this resume for sadika shaikh bca studentSadikaShaikh7
I am a dedicated BCA student with a strong foundation in web technologies, including PHP and MySQL. I have hands-on experience in Java and Python, and a solid understanding of data structures. My technical skills are complemented by my ability to learn quickly and adapt to new challenges in the ever-evolving field of computer science.
GDG Cloud Southlake #34: Neatsun Ziv: Automating AppsecJames Anderson
The lecture titled "Automating AppSec" delves into the critical challenges associated with manual application security (AppSec) processes and outlines strategic approaches for incorporating automation to enhance efficiency, accuracy, and scalability. The lecture is structured to highlight the inherent difficulties in traditional AppSec practices, emphasizing the labor-intensive triage of issues, the complexity of identifying responsible owners for security flaws, and the challenges of implementing security checks within CI/CD pipelines. Furthermore, it provides actionable insights on automating these processes to not only mitigate these pains but also to enable a more proactive and scalable security posture within development cycles.
The Pains of Manual AppSec:
This section will explore the time-consuming and error-prone nature of manually triaging security issues, including the difficulty of prioritizing vulnerabilities based on their actual risk to the organization. It will also discuss the challenges in determining ownership for remediation tasks, a process often complicated by cross-functional teams and microservices architectures. Additionally, the inefficiencies of manual checks within CI/CD gates will be examined, highlighting how they can delay deployments and introduce security risks.
Automating CI/CD Gates:
Here, the focus shifts to the automation of security within the CI/CD pipelines. The lecture will cover methods to seamlessly integrate security tools that automatically scan for vulnerabilities as part of the build process, thereby ensuring that security is a core component of the development lifecycle. Strategies for configuring automated gates that can block or flag builds based on the severity of detected issues will be discussed, ensuring that only secure code progresses through the pipeline.
Triaging Issues with Automation:
This segment addresses how automation can be leveraged to intelligently triage and prioritize security issues. It will cover technologies and methodologies for automatically assessing the context and potential impact of vulnerabilities, facilitating quicker and more accurate decision-making. The use of automated alerting and reporting mechanisms to ensure the right stakeholders are informed in a timely manner will also be discussed.
Identifying Ownership Automatically:
Automating the process of identifying who owns the responsibility for fixing specific security issues is critical for efficient remediation. This part of the lecture will explore tools and practices for mapping vulnerabilities to code owners, leveraging version control and project management tools.
Three Tips to Scale the Shift Left Program:
Finally, the lecture will offer three practical tips for organizations looking to scale their Shift Left security programs. These will include recommendations on fostering a security culture within development teams, employing DevSecOps principles to integrate security throughout the development
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
The DealBook is our annual overview of the Ukrainian tech investment industry. This edition comprehensively covers the full year 2023 and the first deals of 2024.
How to Avoid Learning the Linux-Kernel Memory ModelScyllaDB
The Linux-kernel memory model (LKMM) is a powerful tool for developing highly concurrent Linux-kernel code, but it also has a steep learning curve. Wouldn't it be great to get most of LKMM's benefits without the learning curve?
This talk will describe how to do exactly that by using the standard Linux-kernel APIs (locking, reference counting, RCU) along with a simple rules of thumb, thus gaining most of LKMM's power with less learning. And the full LKMM is always there when you need it!
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
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
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.
Video traffic on the Internet is constantly growing; networked multimedia applications consume a predominant share of the available Internet bandwidth. A major technical breakthrough and enabler in multimedia systems research and of industrial networked multimedia services certainly was the HTTP Adaptive Streaming (HAS) technique. This resulted in the standardization of MPEG Dynamic Adaptive Streaming over HTTP (MPEG-DASH) which, together with HTTP Live Streaming (HLS), is widely used for multimedia delivery in today’s networks. Existing challenges in multimedia systems research deal with the trade-off between (i) the ever-increasing content complexity, (ii) various requirements with respect to time (most importantly, latency), and (iii) quality of experience (QoE). Optimizing towards one aspect usually negatively impacts at least one of the other two aspects if not both. This situation sets the stage for our research work in the ATHENA Christian Doppler (CD) Laboratory (Adaptive Streaming over HTTP and Emerging Networked Multimedia Services; https://athena.itec.aau.at/), jointly funded by public sources and industry. In this talk, we will present selected novel approaches and research results of the first year of the ATHENA CD Lab’s operation. We will highlight HAS-related research on (i) multimedia content provisioning (machine learning for video encoding); (ii) multimedia content delivery (support of edge processing and virtualized network functions for video networking); (iii) multimedia content consumption and end-to-end aspects (player-triggered segment retransmissions to improve video playout quality); and (iv) novel QoE investigations (adaptive point cloud streaming). We will also put the work into the context of international multimedia systems research.
2. “Anything that can go wrong, will go wrong”
Murphy's law
Maciej Lasyk, High Availability Explained
2/14
3. “Anything that can go wrong, will go wrong”
Murphy's law
Maciej Lasyk, High Availability Explained
2/14
4. “Anything that can go wrong, will go wrong”
Murphy's law
An electrical explosion and fire Saturday at a Houston data
center operated by The Planet has taken the entire facility offline.
The company claimed power to the facility was interrupted when a
transformer exploded. Official reports that three walls were blown
down causing a fire.
Maciej Lasyk, High Availability Explained
2/14
5. “Anything that can go wrong, will go wrong”
Murphy's law
An electrical explosion and fire Saturday at a Houston data
center operated by The Planet has taken the entire facility offline.
The company claimed power to the facility was interrupted when a
transformer exploded. Official reports that three walls were blown
down causing a fire.
Three walls of the electrical equipment room on the first floor
blew several feet from their original position, and the underground
cabling that powers the first floor of H1 was destroyed.
Maciej Lasyk, High Availability Explained
2/14
6. High Availability is in the eye of the beholder
Maciej Lasyk, High Availability Explained
3/14
7. High Availability is in the eye of the beholder
CEO: we don't loose sales
Maciej Lasyk, High Availability Explained
3/14
8. High Availability is in the eye of the beholder
CEO: we don't loose sales
Sales: we can extend our offer basing on HA level
Maciej Lasyk, High Availability Explained
3/14
9. High Availability is in the eye of the beholder
CEO: we don't loose sales
Sales: we can extend our offer basing on HA level
Accounts managers: we don't upset our customers (that often)
Maciej Lasyk, High Availability Explained
3/14
10. High Availability is in the eye of the beholder
CEO: we don't loose sales
Sales: we can extend our offer basing on HA level
Accounts managers: we don't upset our customers (that often)
Developers: we can be proud – our services are working ;)
Maciej Lasyk, High Availability Explained
3/14
11. High Availability is in the eye of the beholder
CEO: we don't loose sales
Sales: we can extend our offer basing on HA level
Accounts managers: we don't upset our customers (that often)
Developers: we can be proud – our services are working ;)
System engineers: we can sleep well (and fsck, we love to!)
Maciej Lasyk, High Availability Explained
3/14
12. High Availability is in the eye of the beholder
CEO: we don't loose sales
Sales: we can extend our offer basing on HA level
Accounts managers: we don't upset our customers (that often)
Developers: we can be proud – our services are working ;)
System engineers: we can sleep well (and fsck, we love to!)
Technical support: no calls? Back to WoW then.. ;)
Maciej Lasyk, High Availability Explained
3/14
13. So how many 9's?
Maciej Lasyk, High Availability Explained
4/14
14. So how many 9's?
Maciej Lasyk, High Availability Explained
4/14
15. So how many 9's?
Monthly: 1 hour of outage means 100% - 0.13888 ~= 99.86112 of availability
Maciej Lasyk, High Availability Explained
4/14
16. So how many 9's?
Monthly: 1 hour of outage means 100% - 0.13888 ~= 99.86112 of availability
Yearly: 1 hour of outage means 100% - 0.01142 ~= 99.98858 of availability
Maciej Lasyk, High Availability Explained
4/14
17. So how many 9's?
Monthly: 1 hour of outage means 100% - 0.13888 ~= 99.86112 of availability
Yearly: 1 hour of outage means 100% - 0.01142 ~= 99.98858 of availability
Availability
Downtime (year)
Downtime (month)
90% (“one nine”)
36.5 days
72 hours
95%
18.25 days
36 hours
97%
10.96 days
21.6 hours
98%
7.30 days
14.4 hours
99% (“two nines”)
3.65 days
7.2 hours
99.5%
1.83 days
3.6 hours
99.8%
17.52 hours
86.23 minutes
99.9% (“three nines”)
4.38 hours
21.56 minutes
99.99 (“four nines”)
52.56 minutes
4.32 minutes
99.999 (“five nines”)
5.26 minutes
25.9 seconds
Maciej Lasyk, High Availability Explained
4/14
18. So how many 9's?
https://jazz.net/wiki/bin/view/Deployment/HighAvailability
Maciej Lasyk, High Availability Explained
4/14
19. HA terminology
RPO: Recovery Point Objective; how much data can we loose?
Maciej Lasyk, High Availability Explained
5/14
20. HA terminology
RPO: Recovery Point Objective; how much data can we loose?
RTO: Recovery Time Objective; how long does it take to recover?
Maciej Lasyk, High Availability Explained
5/14
21. HA terminology
RPO: Recovery Point Objective; how much data can we loose?
RTO: Recovery Time Objective; how long does it take to recover?
MTBF: Mean-Times-Between-Failures; time between failures
(density fnc -> reliability fnc)
https://en.wikipedia.org/wiki/Mean_time_between_failures
Maciej Lasyk, High Availability Explained
5/14
22. HA terminology
SLA: Service Level Agreement;
formal definitions (customer <-> provider)
Maciej Lasyk, High Availability Explained
5/14
23. HA terminology
SLA: Service Level Agreement;
formal definitions (customer <-> provider)
OLA: Operational Level Agreement; definitions within organization;
help us keeping provided SLAs
Maciej Lasyk, High Availability Explained
5/14
24. SLAs..
So what is written in SLAs?
Availability
Downtime (year)
Downtime (month)
90%
36.5 days
72 hours
95%
18.25 days
36 hours
97%
10.96 days
21.6 hours
98%
7.30 days
14.4 hours
99%
3.65 days
7.2 hours
99.5% (EC2, EBS)
1.83 days
3.6 hours
99.8%
17.52 hours
86.23 minutes
99.9% (SoftLayer, IBM)
4.38 hours
21.56 minutes
99.99
52.56 minutes
4.32 minutes
99.999
5.26 minutes
25.9 seconds
Maciej Lasyk, High Availability Explained
5/14
25. SLAs..
So what is written in SLAs?
Availability
Downtime (year)
Downtime (month)
90%
36.5 days
72 hours
95%
18.25 days
36 hours
97%
10.96 days
21.6 hours
98%
7.30 days
14.4 hours
99%
3.65 days
7.2 hours
99.5% (EC2, EBS)
1.83 days
3.6 hours
99.8%
17.52 hours
86.23 minutes
99.9% (SoftLayer, IBM)
4.38 hours
21.56 minutes
99.99
52.56 minutes
4.32 minutes
99.999
5.26 minutes
25.9 seconds
http://aws.amazon.com/ec2/sla/
http://www.softlayer.com/about/service-level-agreement
Maciej Lasyk, High Availability Explained
5/14
26. SLAs..
Availability mentioned in SLAs are only goals of service provider
Usually when it's not met than company pays off the fees
Maciej Lasyk, High Availability Explained
5/14
27. How deep is this hole?
app layer (core, db, cache)
data storage
operating system
hardware
networking
location
So we would like to achieve 99,9999% which is about 30s of downtime per year
Maciej Lasyk, High Availability Explained
6/14
28. How deep is this hole?
app layer (core, db, cache)
data storage
operating system
hardware
networking
location
Even Proof of Concept is very hard to provide: 5s of downtime per layer yearly!
Maciej Lasyk, High Availability Explained
6/14
31. th
th
LB – 4 layer or 7 ?
4th layer:
7th layer:
- high performance
- low cost
- just do the LB work!
- good for quickfixes / patches
- reliable
- not that scalable
- scalable
- low performance
- complex codebase
- custom code for protocols
- cookies? what about memcache..
Maciej Lasyk, High Availability Explained
8/14
36. Planning for failure
Everything starts here - DNS:
- keep TTLs low (300s). Can't make under 60min? That's bad!
- check SLA of DNS servers (dnsmadeeasy.com history)
- what do you know about DNSes?
- zero downtime here is a must!
- this can be achieved with complicated network abracadabra
- remember what 99.9999% means?
- round robin is a load – balancer but without failover!
- GSLB – killed by OS/browser/srvs cache'ing
(GlobalServerLoadBalancing)
- GlobalIP (SoftLayer etc) – workaround for GSLB via routing
Maciej Lasyk, High Availability Explained
10/14
37. Planning for failure
E-mail servers:
- it's simple as MX records (delivering)
- it's almost simple as complicated system of SMTP servers (sending)
- it's not that simple when IMAP locking over DFS (reading)
5 gmail-smtp-in.l.google.com.
10 alt1.gmail-smtp-in.l.google.com.
20 alt2.gmail-smtp-in.l.google.com.
30 alt3.gmail-smtp-in.l.google.com.
40 alt4.gmail-smtp-in.l.google.com.
When MXing – watch the spam!
Maciej Lasyk, High Availability Explained
10/14
38. Planning for failure
WEB servers:
- it's simple as some frontend loadbalancer
- did you really stick user session to particular server? Memcache!
- LB balancing algorithm
- how many Lbs?
- what if LB goes down?
Maciej Lasyk, High Availability Explained
10/14
39. Planning for failure
DB servers:
- it's.. not that simple
- replication (master – master? App should be aware..)
- replication ring? Complicated, works, but in case of failure...
- let's talk about MySQL:
- NoSPOF solution: MySQL cluster
- MySQL Galera cluster – synch, active-active multi-master
- master – master – simply works
- Failover? Matsunobu Yoshinori mysql-master-ha
- MySQL utilities (http://www.clusterdb.com/mysql/mysql-utilities-webinar-qa-replay-now-available/)
Maciej Lasyk, High Availability Explained
10/14
40. Planning for failure
Caching servers:
- this is cache for God's sake – why would we use HA here?
- just use proper architecture like... redundancy.
Maciej Lasyk, High Availability Explained
10/14
41. Planning for failure
Caching servers:
- this is cache for God's sake – why would we use HA here?
- just use proper architecture like... redundancy.
Load – balancers:
- remember about failovering IP addresses!
Maciej Lasyk, High Availability Explained
10/14
42. Planning for failure
Caching servers:
- this is cache for God's sake – why would we use HA here?
- just use proper architecture like... redundancy.
Load – balancers:
- remember about failovering IP addresses!
Storage – DFSes:
- GlusterFS – we'll see it in action in a minute
- NFS? Could be – over some SAN / NAS (high cost solution)
- CephFS – just like GlusterFS – it's great and does the work
- DRBD – lower level, does the work on block – device layer – slow...
Maciej Lasyk, High Availability Explained
10/14
44. Planning for failure
GlusterFS: replicated volumes vs Geo-replication
- replicated:
- mirrors data
- provides HA
- synch – replication
- Geo-replication:
- mirrors data across geo – distributed clusters
- ensures backing up data for DR
- asynch – replica (periodic checks)
Maciej Lasyk, High Availability Explained
10/14
45. Planning for failure
HA for virtualization solutions?
- it's really complicated, like...
Maciej Lasyk, High Availability Explained
11/14
46. Planning for failure
HA for virtualization solutions?
- it's really complicated, like...
Maciej Lasyk, High Availability Explained
11/14
47. Tools
The most important tool would be the conclusion from the picture below:
Maciej Lasyk, High Availability Explained
12/14
48. Tools
The most important tool would be the conclusion from the picture below:
Maciej Lasyk, High Availability Explained
12/14
49. Tools
The most important tool would be the conclusion from the picture below:
Maciej Lasyk, High Availability Explained
12/14
50. Tools
- DNS: roundrobin, GSLB, low ttls, globalIP
Maciej Lasyk, High Availability Explained
12/14
55. Turn on HA thinking!
Main goal of HA? Improve user experience!
- keep the app fully functional
- keep the app resistant and tolerant to faults
- provide method for a successful audit
- sleep well (anyone awake?) ;)
Maciej Lasyk, High Availability Explained
13/14
56. Thank you :)
High Availability Explained
Maciej Lasyk
Kraków, devOPS meetup #2
2014-01-28
http://maciek.lasyk.info/sysop
maciek@lasyk.info
@docent-net
Maciej Lasyk, High Availability Explained
14/14