This document discusses strategies for scaling a Ruby on Rails application from a small startup to an enterprise-level application. It recommends starting with a small, highly productive team using Rails for rapid development. As the application and user base grow, it suggests adding caching, load balancing, and splitting the application across multiple servers. It also discusses personalizing pages with AJAX to improve caching. The goal is to scale the application efficiently while keeping development agile and in Rails.
EuroPython 2011 - How to build complex web applications having fun?Andrew Mleczko
Web development is a complexity challenge nowadays. Growing number of functionalities results in customer expectations increase which makes project design more difficult. Using proper tools that suite your customer needs is essential.
This talk is about successful story using closely together Pyramid and Plone. Basing on these examples you will see the main reasons for using Plone as a CMS only and letting Pyramid do the rest (vertical application).
An introduction to Google's PRPL pattern that can be used to implement Progressive Web Applications. Delivered at MWLUG 2017 in Alexandria, VA by Keith Strickland.
Better and Faster: A Journey Toward Clean Code and EnjoymentChris Holland
Video: http://bit.ly/tdd-talk-2
This slideshow has links, download the PDF to click them.
While this presentation touches on PHP a fair bit, it does make parallels to other ecosystems such as Java and C#/.Net, building toward an approach for building Web Applications in a Test-Driven way.
Have you ever jumped into a legacy software project and gotten to a point where it takes a near-infinite amount of time to deliver any new feature, for fear of breaking legacy functionality you’ve barely begun to understand? Software Engineering can be extremely difficult and maddening. But it doesn’t have to be. We will explore leveraging TDD and OOP principles to make Software Engineering fun again.
Coding exercises supporting this presentation are available here:
http://bit.ly/tdd-vids
EuroPython 2011 - How to build complex web applications having fun?Andrew Mleczko
Web development is a complexity challenge nowadays. Growing number of functionalities results in customer expectations increase which makes project design more difficult. Using proper tools that suite your customer needs is essential.
This talk is about successful story using closely together Pyramid and Plone. Basing on these examples you will see the main reasons for using Plone as a CMS only and letting Pyramid do the rest (vertical application).
An introduction to Google's PRPL pattern that can be used to implement Progressive Web Applications. Delivered at MWLUG 2017 in Alexandria, VA by Keith Strickland.
Better and Faster: A Journey Toward Clean Code and EnjoymentChris Holland
Video: http://bit.ly/tdd-talk-2
This slideshow has links, download the PDF to click them.
While this presentation touches on PHP a fair bit, it does make parallels to other ecosystems such as Java and C#/.Net, building toward an approach for building Web Applications in a Test-Driven way.
Have you ever jumped into a legacy software project and gotten to a point where it takes a near-infinite amount of time to deliver any new feature, for fear of breaking legacy functionality you’ve barely begun to understand? Software Engineering can be extremely difficult and maddening. But it doesn’t have to be. We will explore leveraging TDD and OOP principles to make Software Engineering fun again.
Coding exercises supporting this presentation are available here:
http://bit.ly/tdd-vids
Atlassian's P2 plugin system is fantastic for developers familiar with Maven, Java, OSGi, and (generally speaking) tools built over a decade ago. But where do the modern front-end development tools and techniques fit in to the picture? Join developer Chris Darroch as he explains how to build a sophisticated front-end for an Atlassian add-on using technologies like Node.js, Gulp, Wepback, and JavaScript transpiled from TypeScript / ES2015. He'll cover the basic front-end pillars of the P2 system, talk about how Maven applies to writing front-end code. Note: this session assumes familiarity with JavaScript and Node.js.
Chris Darroch, Senior Developer, Atlassian
Keshav Puttaswamy, Head of Product, Server, Atlassian
Description of the Java platform (languages, runtime libraries, execution environments) and how to write cross platform portable Java code (mobile, desktop, server, iot, ...).
FaaS or not to FaaS. Visible and invisible benefits of the Serverless paradig...Vadym Kazulkin
When we talk about prices, we often only talk about Lambda costs. In our applications, however, we rarely use only Lambda. Usually we have other building blocks like API Gateway, data sources like SNS, SQS or Kinesis. We also store our data either in S3 or in serverless databases like DynamoDB or recently in Aurora Serverless. All of these AWS services have their own pricing models to look out for. In this talk, we will draw a complete picture of the total cost of ownership in serverless applications and present a decision-making list for determining if and whether to rely on serverless paradigm in your project. In doing so, we look at the cost aspects as well as other aspects such as understanding application lifecycle, software architecture, platform limitations, organizational knowledge and plattform and tooling maturity. We will also discuss current challenges adopting serverless such as lack of high latency ephemeral storage, unsufficient network performance and missing security features.
The Ember.js Framework - Everything You Need To KnowAll Things Open
All Things Open 2014 - Day 2
Thursday, October 23rd, 2014
Yehuda Katz
Founder of Tilde
Front Dev 1
The Ember.js Framework - Everything You Need To Know
How To Become A DevOps Engineer | Who Is A DevOps Engineer? | DevOps Engineer...Simplilearn
This presentation on "How to become a DevOps Engineer" will help you learn what is DevOps, who is a DevOps engineer, career roadmap of a DevOps engineer, certifications for DevOps engineer, and salary of a DevOps engineer. A DevOps Engineer is an IT professional who understands the software development lifecycle and uses various automation tools for developing CI/ CD pipelines. In simple words, they collaborate with developer and operation teams to deliver high-quality products within a minimum amount of time. Now, let's get started and understand a few important ways to become a DevOps engineer.
Below are explained in this presentation:
1. Who is a DevOps engineer?
2. DevOps career roadmap
3. DevOps certification
4. DevOps engineer salary
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands on and interactive approach. The DevOps training course focuses heavily on the use of Docker containers, a technology that is revolutionizing the way apps are deployed in the cloud today and is a critical skillset to master in the cloud age.
After completing the DevOps training course you will achieve hands on expertise in various aspects of the DevOps delivery model. The practical learning outcomes of this DevOps training course are:
An understanding of DevOps and the modern DevOps toolsets
The ability to automate all aspects of a modern code delivery and deployment pipeline using:
1. Source code management tools
2. Build tools
3. Test automation tools
4. Containerization through Docker
5. Configuration management tools
6. Monitoring tools
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at https://www.simplilearn.com/cloud-computing/devops-practitioner-certification-training
Is Enterprise Java Still Relevant (JavaOne 2015 session)Ian Robinson
Soon after Java burst into the world in the 90s it started to gatecrash the parties of its enterprise computing seniors, whose initial amused response was -- You're Not On The List, You're Not Coming In. But EJBs turned heads in the 20th Century and when the Java Enterprise platform emerged, it started getting more invites until it was the party. Now Java EE is grown up with its own kids - EE7 is already two years old. How is it and the platform doing? The party is now in the cloud and the guest list includes many different language technologies and fast-moving open-source innovations. Is Enterprise Java still relevant here? And if it is, what does it need to keep doing or what does it need to change to stay on the VIP list?
Stack Overflow - It's all about performance / Marco Cecconi (Stack Overflow)Ontico
Stack Overflow, and its Q&A network Stack Exchange, have been growing exponentially for the last five years. They now encompass
~150 Q&A sites
~9 million users
~13 million questions
~22 million answers
In this talk, I will describe:
+ The physical architecture of Stack Overflow. How many servers are there? What is their purpose and what are their specs?
+ The logical architecture of the software. How do we scale up? What are the main building blocks of our software?
+ The tooling system. What supports our extreme optimization philosophy?
+ The development team. What are our core values? What footprint do we want to leave as developers?
The days of EJB’s being the center of the Java EE universe are coming to an end. CDI is increasingly becoming the de facto component framework, due to its flexibility and lack of legacy. Starting in Java EE 7 and continuing in 8, the Java EE platform is migrating to enable all of EJB’s best features to be usable in the CDI world. In this session, you’ll learn implementation-level details on how they relate to each other, where we are in the EJB/CDI alignment story, what trade-offs you might need to make, and what you have to gain from making the transition. You will walk out with runnable examples and vendor-level insights. This is the perfect session for heavy EJB users looking to keep up with Java EE’s transition to CDI.
At Netflix, we provide a Java-based API that supports the content discovery, sign-up, and playback experience on thousands of device types that millions use around the world every day. As our user base and traffic have grown by leaps and bounds, we are continuously evolving this API to enable the best user experience. In this talk, I will give an overview of how and why the Netflix API has evolved to where it is today and where we plan to take it in the future. I will discuss how we make our system resilient against failures using tools such as Hystrix and FIT, while keeping it flexible and nimble enough to support continuous A/B testing.
Social and Technical Evolution of the Ruby on Rails Software EcosystemTom Mens
Presentation by Eleni Constantinou (postdoctoral researcher at the Software Engineerin Lab of the University of Mons, Belgium) during the Workshop on Ecosystem Architecuters (WEA2016), Copenhagen, Denmark, 29 November 2016.
Abstract: Software ecosystems evolve through an active community of developers who contribute to projects within the ecosystem. However, development teams change over time, suggesting a potential impact on the evolution of the technical parts of the ecosystem. The impact of such modifications has been studied by previous works, but only temporary changes have been investigated, while the long-term effect of permanent changes has yet to be explored. In this paper, we investigate the evolution of the ecosystem of Ruby on Rails in GitHub in terms of such temporary and permanent changes of the development team. We use three viewpoints of the Rails ecosystem evolution to discuss our preliminary findings: (1) the base project; (2) the forks; and (3) the entire ecosystem containing both base project and forks.
Atlassian's P2 plugin system is fantastic for developers familiar with Maven, Java, OSGi, and (generally speaking) tools built over a decade ago. But where do the modern front-end development tools and techniques fit in to the picture? Join developer Chris Darroch as he explains how to build a sophisticated front-end for an Atlassian add-on using technologies like Node.js, Gulp, Wepback, and JavaScript transpiled from TypeScript / ES2015. He'll cover the basic front-end pillars of the P2 system, talk about how Maven applies to writing front-end code. Note: this session assumes familiarity with JavaScript and Node.js.
Chris Darroch, Senior Developer, Atlassian
Keshav Puttaswamy, Head of Product, Server, Atlassian
Description of the Java platform (languages, runtime libraries, execution environments) and how to write cross platform portable Java code (mobile, desktop, server, iot, ...).
FaaS or not to FaaS. Visible and invisible benefits of the Serverless paradig...Vadym Kazulkin
When we talk about prices, we often only talk about Lambda costs. In our applications, however, we rarely use only Lambda. Usually we have other building blocks like API Gateway, data sources like SNS, SQS or Kinesis. We also store our data either in S3 or in serverless databases like DynamoDB or recently in Aurora Serverless. All of these AWS services have their own pricing models to look out for. In this talk, we will draw a complete picture of the total cost of ownership in serverless applications and present a decision-making list for determining if and whether to rely on serverless paradigm in your project. In doing so, we look at the cost aspects as well as other aspects such as understanding application lifecycle, software architecture, platform limitations, organizational knowledge and plattform and tooling maturity. We will also discuss current challenges adopting serverless such as lack of high latency ephemeral storage, unsufficient network performance and missing security features.
The Ember.js Framework - Everything You Need To KnowAll Things Open
All Things Open 2014 - Day 2
Thursday, October 23rd, 2014
Yehuda Katz
Founder of Tilde
Front Dev 1
The Ember.js Framework - Everything You Need To Know
How To Become A DevOps Engineer | Who Is A DevOps Engineer? | DevOps Engineer...Simplilearn
This presentation on "How to become a DevOps Engineer" will help you learn what is DevOps, who is a DevOps engineer, career roadmap of a DevOps engineer, certifications for DevOps engineer, and salary of a DevOps engineer. A DevOps Engineer is an IT professional who understands the software development lifecycle and uses various automation tools for developing CI/ CD pipelines. In simple words, they collaborate with developer and operation teams to deliver high-quality products within a minimum amount of time. Now, let's get started and understand a few important ways to become a DevOps engineer.
Below are explained in this presentation:
1. Who is a DevOps engineer?
2. DevOps career roadmap
3. DevOps certification
4. DevOps engineer salary
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands on and interactive approach. The DevOps training course focuses heavily on the use of Docker containers, a technology that is revolutionizing the way apps are deployed in the cloud today and is a critical skillset to master in the cloud age.
After completing the DevOps training course you will achieve hands on expertise in various aspects of the DevOps delivery model. The practical learning outcomes of this DevOps training course are:
An understanding of DevOps and the modern DevOps toolsets
The ability to automate all aspects of a modern code delivery and deployment pipeline using:
1. Source code management tools
2. Build tools
3. Test automation tools
4. Containerization through Docker
5. Configuration management tools
6. Monitoring tools
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at https://www.simplilearn.com/cloud-computing/devops-practitioner-certification-training
Is Enterprise Java Still Relevant (JavaOne 2015 session)Ian Robinson
Soon after Java burst into the world in the 90s it started to gatecrash the parties of its enterprise computing seniors, whose initial amused response was -- You're Not On The List, You're Not Coming In. But EJBs turned heads in the 20th Century and when the Java Enterprise platform emerged, it started getting more invites until it was the party. Now Java EE is grown up with its own kids - EE7 is already two years old. How is it and the platform doing? The party is now in the cloud and the guest list includes many different language technologies and fast-moving open-source innovations. Is Enterprise Java still relevant here? And if it is, what does it need to keep doing or what does it need to change to stay on the VIP list?
Stack Overflow - It's all about performance / Marco Cecconi (Stack Overflow)Ontico
Stack Overflow, and its Q&A network Stack Exchange, have been growing exponentially for the last five years. They now encompass
~150 Q&A sites
~9 million users
~13 million questions
~22 million answers
In this talk, I will describe:
+ The physical architecture of Stack Overflow. How many servers are there? What is their purpose and what are their specs?
+ The logical architecture of the software. How do we scale up? What are the main building blocks of our software?
+ The tooling system. What supports our extreme optimization philosophy?
+ The development team. What are our core values? What footprint do we want to leave as developers?
The days of EJB’s being the center of the Java EE universe are coming to an end. CDI is increasingly becoming the de facto component framework, due to its flexibility and lack of legacy. Starting in Java EE 7 and continuing in 8, the Java EE platform is migrating to enable all of EJB’s best features to be usable in the CDI world. In this session, you’ll learn implementation-level details on how they relate to each other, where we are in the EJB/CDI alignment story, what trade-offs you might need to make, and what you have to gain from making the transition. You will walk out with runnable examples and vendor-level insights. This is the perfect session for heavy EJB users looking to keep up with Java EE’s transition to CDI.
At Netflix, we provide a Java-based API that supports the content discovery, sign-up, and playback experience on thousands of device types that millions use around the world every day. As our user base and traffic have grown by leaps and bounds, we are continuously evolving this API to enable the best user experience. In this talk, I will give an overview of how and why the Netflix API has evolved to where it is today and where we plan to take it in the future. I will discuss how we make our system resilient against failures using tools such as Hystrix and FIT, while keeping it flexible and nimble enough to support continuous A/B testing.
Social and Technical Evolution of the Ruby on Rails Software EcosystemTom Mens
Presentation by Eleni Constantinou (postdoctoral researcher at the Software Engineerin Lab of the University of Mons, Belgium) during the Workshop on Ecosystem Architecuters (WEA2016), Copenhagen, Denmark, 29 November 2016.
Abstract: Software ecosystems evolve through an active community of developers who contribute to projects within the ecosystem. However, development teams change over time, suggesting a potential impact on the evolution of the technical parts of the ecosystem. The impact of such modifications has been studied by previous works, but only temporary changes have been investigated, while the long-term effect of permanent changes has yet to be explored. In this paper, we investigate the evolution of the ecosystem of Ruby on Rails in GitHub in terms of such temporary and permanent changes of the development team. We use three viewpoints of the Rails ecosystem evolution to discuss our preliminary findings: (1) the base project; (2) the forks; and (3) the entire ecosystem containing both base project and forks.
Why every startup built with Ruby on Rails has an upper hand over their compe...DreamToIPO
Why every startup built with Ruby on Rails has an upper hand over their competitors - Built with ruby on rails, Ruby on Rails development specialist, startup ruby on rails development company.
Introduction to Ruby on Rails by Rails Core alumnus Thomas Fuchs.
Originally a 3-4 hour tutorial, 150+ slides about Rails, Ruby and the ecosystem around it.
Michael Choi's process for designing web application(s), including which programming language to use, when to use Node.js, when to use a light-weight framework vs a heavy MVC framework, how to set up git for collaboration based on complexity of the project, how a tool like Jenkins can be used for continuous integration, continuous delivery, and continuous deployment, where to host the data, what services to use for orchestrating containers or servers.
A great idea can be built with almost any technology. The success or failure of your project has more to do with vision, leadership, execution, and market than technological choices.
Besides the vision, a lot of startups focus on culture. what isn’t often mentioned is that the technical decisions will have a direct effect on the company culture. Great things have been built with each of the technologies. But they do come with a culture.
The purpose of this presentation is to help developers, managers, founders, etc. to make an insightful decision about the framework they want to use to create their product.
Do you need Ops in your new startup? If not now, then when? And...what is Ops?
Learn how to scale ruby-based distributed software infrastructure in the cloud to serve 4,000 requests per second, handle 400 updates per second, and achieve 99.97% uptime – all while building the product at the speed of light.
Unimpressed? Now try doing the above altogether without the Ops team, while growing your traffic 100x in 6 months and deploying 5-6 times a day!
It could be a dream, but luckily it's a reality that could be yours.
For developers, one of the most significant factors in evaluating a job role is the technology stack that they’ll be using. Having the right technologies in your stack is the best way to help your employees and business grow.
Cloud-Native Fundamentals: Accelerating Development with Continuous IntegrationVMware Tanzu
DevOps. Microservices. Containers. These terms have a lot of buzz for their role in cloud-native application development and operations. But, if you haven't automated your tests and builds with continuous integration (CI), none of them matter.
Continuous integration is the automation of building and testing new code. Development teams that use CI can catch bugs early and often; resulting in code that is always production ready. Compared to manual testing, CI eliminates a lot of toil and improves code quality. At the end of the day, it's those code defects that slip into production that slow down teams and cause apps to fall over.
The journey to continuous integration maturity has some requirements. Join Pivotal's James Ma, product manager for Concourse, and Dormain Drewitz, product marketing to learn about:
- How Test-Driven Development feeds the CI process
- What is different about CI in a cloud-native context
- How to measure progress and success in adopting CI
Dormain is a Senior Director of Product and Customer Marketing with Pivotal. She has published extensively on cloud computing topics for ten years, demystifying the changing requirements of the infrastructure software stack. She’s presented at the Gartner Application Architecture, Development, and Integration Summit; Open Source Summit; Cloud Foundry Summit, and numerous software user events.
James Ma is a product manager at Pivotal and is based out of their office in Toronto, Canada. As a consultant for the Pivotal Labs team, James worked with Fortune 500 companies to hone their agile software development practices and adopt a user-centered approach to product development. He has worked with companies across multiple industries including: mobile e-commerce, finance, heath and hospitality. James is currently a part of the Pivotal Cloud Foundry R&D group and is the product manager for Concourse CI, the continuous "thing do-er".
Presenters : Dormain Drewitz & James Ma, Pivotal
AppSec Pipelines and Event based SecurityMatt Tesauro
Presented at AppSec California 2017, this is a continuation of earlier talks about AppSec Pipelines and demonstrates 1st and 2nd Gen Pipelines, how OWASP is creating a pipeline for its projects and how several companies have benefited from combining DevOps, Agile, CI/CD and Security into an AppSec Pipeline to move beyond traditional AppSec testing.
Hadoop and the Relational Database: The Best of Both WorldsInside Analysis
The Briefing Room with Dr. Robin Bloor and Splice Machine
Live Webcast on August 5, 2014
Watch the archive:
https://bloorgroup.webex.com/bloorgroup/lsr.php?RCID=71551d669454741c8bd56f2349bdf140
As the pressure of Big Data collides with the reality of daily operations, many organizations are trying to solve the challenge of meeting new requirements without disrupting the flow of business. One solution focuses on the data layer itself, by combining the well known functionality of relational database technology with the scale-out capabilities of Hadoop.
Register for this episode of The Briefing Room to hear from veteran Analyst Dr. Robin Bloor as he outlines the critical components of a business-ready data layer. He’ll be briefed by John Leach and Rich Reimer of Splice Machine who will explain how their solution delivers the best of both data worlds: the trusted capabilities of relational with the infinite scalability of Hadoop. They will also discuss how Hadoop has transformed from a batch-oriented workhorse into a scale-out layer capable of supporting real-time applications and operational analytics using traditional SQL.
Visit InsideAnlaysis.com for more information.
Scaling Up Lookout was originally presented at Lookout's Scaling for Mobile event on July 25, 2013. R. Tyler Croy is a Senior Software Engineer at Lookout, Inc. Lookout has grown immensely in the last year. We've doubled the size of the company—added more than 80 engineers to the team, support 45+ million users, have over 1000 machines in production, see over 125,000 QPS and more than 2.6 billion requests/month. Our analysts use Hadoop, Hive, and MySQL to interactively manipulate multibillion row tables. With that, there are bound to be some growing pains and lessons learned.
Just In Time Scalability Agile Methods To Support Massive Growth PresentationTimothy Fitz
Eric Reis and Chris Hondl's MySQL conference presentation on Just In Time Scalability. http://startuplessonslearned.blogspot.com/2008/09/just-in-time-scalability.html
Innovate Better Through Machine data AnalyticsHal Rottenberg
This talk was presented at IP Expo Manchester in May, 2016. the themes discussed are:
- how does machine data relate to devops?
- how can tracking this data lead to better outcomes?
- what types of data are important to track?
DOES15 - Ernest Mueller - DevOps Transformations At National Instruments and...Gene Kim
Ernest Mueller, Lean Systems Manager, AlienVault
DevOps Transformations At National Instruments and Bazaarvoice (And Infosec!)
In this presentation, I’ll share the thrills and chills of the real-world successes and setbacks in culture and collaboration, speeding up software releases, embedding DevOps engineers into product teams, implementing agile processes with operations teams, integrating testing and information security into daily work, automation and its pitfalls, metrics and their weaponization, and more. I’ll also discuss how we integrated security objectives into all these initiatives.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...
Enterprise Architectures with Ruby (and Rails)
1. Enterprise Architecture with
Ruby (and Rails)
Building amazing products, companies and
technology using Ruby on Rails and friends.
An opinionated overview for MagmaRails.MX by
Konstantin Gredeskoul, CTO, Wanelo, Inc
twitter: @kig, github.com/kigster
2. My Background
CTO @ Wanelo.com — “Pinterest for shopping”
Principal @ ModCloth.com — is one of the largest
independent e-commerce Rails sites
Principal @ Blurb.com — print-on-demand bookstore,
and a large e-commerce web site
Professionally building enterprise software since 1995
Converted from Java/Perl/C to ruby in 2006
5. What is Enterprise?
It’s an organization with many people,
services, technologies
Enterprise architecture is an ongoing
business function that helps an 'enterprise'
figure out how to best execute the strategies
that drive its development [ref: wikipedia]
7. From Start-Up To Enterprise
Many modern enterprises started small, as
tiny start-ups
8. From Start-Up To Enterprise
Many modern enterprises started small, as
tiny start-ups
Many start-ups choose RoR for productivity
9. From Start-Up To Enterprise
Many modern enterprises started small, as
tiny start-ups
Many start-ups choose RoR for productivity
As the start-up grows, so does the technology,
applications, and the stack.
11. Teams using RoR can be
very productive
Productivity is super important for unproven
young companies trying things out
12. Teams using RoR can be
very productive
Productivity is super important for unproven
young companies trying things out
“Build quickly, iterate, avoid building features
users don’t need” — Lean Start-Up Movement
13. Teams using RoR can be
very productive
Productivity is super important for unproven
young companies trying things out
“Build quickly, iterate, avoid building features
users don’t need” — Lean Start-Up Movement
Do not optimize “prematurely”, but think about
tomorrow’s scalability when building today.
15. Productivity vs Scale:
The Dilemma!
To move fast - we use Ruby (dynamic
languages), a framework (Rails), cloud, a
familiar database, and keep the team small
16. Productivity vs Scale:
The Dilemma!
To move fast - we use Ruby (dynamic
languages), a framework (Rails), cloud, a
familiar database, and keep the team small
To truly scale an application - need multiple
languages (Java, C/C++, Scala), custom or no
frameworks, datacenter, large team
18. But does everyone need
mega scale?
Majority of Rails projects are OK without mega-
scale (only a tiny fraction is like Twitter or Facebook)
19. But does everyone need
mega scale?
Majority of Rails projects are OK without mega-
scale (only a tiny fraction is like Twitter or Facebook)
Ruby/Rails can happily grow into a large
applications without major rewrites
20. But does everyone need
mega scale?
Majority of Rails projects are OK without mega-
scale (only a tiny fraction is like Twitter or Facebook)
Ruby/Rails can happily grow into a large
applications without major rewrites
Best assurance that an application will grow
well with it’s use, is to follow best practices.
22. So what is this talk about?
How to start small
But move fast
23. So what is this talk about?
How to start small
But move fast
How to evolve a Rails app
But keep it scalable
24. So what is this talk about?
How to start small
But move fast
How to evolve a Rails app
But keep it scalable
How to split things up
When the app gets large, and keep everyone sane
27. Get a great team together
Keep team size small, 4-6 developers is ideal
28. Get a great team together
Keep team size small, 4-6 developers is ideal
Have at least 2-3 ruby/rails/front-end
experts on the team
29. Get a great team together
Keep team size small, 4-6 developers is ideal
Have at least 2-3 ruby/rails/front-end
experts on the team
Do automated testing (and TDD) from the
beginning. Hard to add later.
31. Process matters
Paired Programming is amazing.
Level the field, transfer knowledge, build trust within
the team, move faster
32. Process matters
Paired Programming is amazing.
Level the field, transfer knowledge, build trust within
the team, move faster
Morning stand-ups, weekly sprint planners,
technical discussions as needed, retrospectives
33. Process matters
Paired Programming is amazing.
Level the field, transfer knowledge, build trust within
the team, move faster
Morning stand-ups, weekly sprint planners,
technical discussions as needed, retrospectives
Dedicated graphic designer/UXR, and a
Product Manager
35. Everyday tools matter
RubyMine IDE is very powerful, but $69
Other tools also work, VIM, TextMate
36. Everyday tools matter
RubyMine IDE is very powerful, but $69
Other tools also work, VIM, TextMate
When pairing, using consistent toolset is
very important. Pick it and stick to it.
37. Everyday tools matter
RubyMine IDE is very powerful, but $69
Other tools also work, VIM, TextMate
When pairing, using consistent toolset is
very important. Pick it and stick to it.
If everyone has their own laptop, create a
common OS account and use it to pair
39. Communication is key
Continuous Integration server runs all
automated tests (Jenkins is great!)
Everyone knows when tests break!
40. Communication is key
Continuous Integration server runs all
automated tests (Jenkins is great!)
Everyone knows when tests break!
41. Communication is key
Continuous Integration server runs all
automated tests (Jenkins is great!)
Everyone knows when tests break!
Pivotal CI Monitor open source app pulls from Jenkins
43. Communication is key
Use Chat (eg, Campfire) to notify team
about check-ins, deploys or failed builds
44. Communication is key
Use Chat (eg, Campfire) to notify team
about check-ins, deploys or failed builds
Review other’s commits (ie, on GitHub) to
learn as much code as possible
45. Communication is key
Use Chat (eg, Campfire) to notify team
about check-ins, deploys or failed builds
Review other’s commits (ie, on GitHub) to
learn as much code as possible
Take care of your team mates, and do worry
about the project. Success depends on it.
47. A few more awesome tools*
iTerm2 - free mega awesome Terminal
replacement (Cmd-D/Cmd-Shift-D)
48. A few more awesome tools*
iTerm2 - free mega awesome Terminal
replacement (Cmd-D/Cmd-Shift-D)
SizeUp - align windows on the screen right/left/
up/down/middle.
49. A few more awesome tools*
iTerm2 - free mega awesome Terminal
replacement (Cmd-D/Cmd-Shift-D)
SizeUp - align windows on the screen right/left/
up/down/middle.
iStat Menus - view CPU, Network IO, Disk in Mac
OS-X Toolbar
50. A few more awesome tools*
iTerm2 - free mega awesome Terminal
replacement (Cmd-D/Cmd-Shift-D)
SizeUp - align windows on the screen right/left/
up/down/middle.
iStat Menus - view CPU, Network IO, Disk in Mac
OS-X Toolbar
CCMenu - view results of CI in your toolbar
52. Choice of libraries matters
MiniTest, Jasmine, Capybara
(RackTest + Selenium) for testing
53. Choice of libraries matters
MiniTest, Jasmine, Capybara
(RackTest + Selenium) for testing
Devise for authentication, user mgmt
54. Choice of libraries matters
MiniTest, Jasmine, Capybara
(RackTest + Selenium) for testing
Devise for authentication, user mgmt
Twitter Bootstrap for early UI is amazing
although we prefer SCSS instead of LESS
55. Choice of libraries matters
MiniTest, Jasmine, Capybara
(RackTest + Selenium) for testing
Devise for authentication, user mgmt
Twitter Bootstrap for early UI is amazing
although we prefer SCSS instead of LESS
HAML for views, RABL for APIs
57. Data matters the most
Relational Databases: PostgreSQL, MySQL
High consistency, reliability, decades of research,
great performance, gets tricky at mega-scale
58. Data matters the most
Relational Databases: PostgreSQL, MySQL
High consistency, reliability, decades of research,
great performance, gets tricky at mega-scale
BigTable based: MongoDB, HBase
Eventual consistency, recent, have indexes,
almost table-like. Also tricky at mega scale.
59. Data matters the most
Relational Databases: PostgreSQL, MySQL
High consistency, reliability, decades of research,
great performance, gets tricky at mega-scale
BigTable based: MongoDB, HBase
Eventual consistency, recent, have indexes,
almost table-like. Also tricky at mega scale.
Amazon Dynamo like: RIAK, Voldemort
Distributed hash-table, tricky from the very
beginning.
61. What to choose?
Without a strong reason otherwise, choose
a relational database. I prefer PostgreSQL.
62. What to choose?
Without a strong reason otherwise, choose
a relational database. I prefer PostgreSQL.
Instagram scaled on PostgreSQL very well
63. What to choose?
Without a strong reason otherwise, choose
a relational database. I prefer PostgreSQL.
Instagram scaled on PostgreSQL very well
If under pressure and in doubt, it’s OK to
choose whatever you are familiar with.
66. New Rails Project: Day 1
rails new my-awesome-app
cd my-awesome-app
rake db:migrate
67. New Rails Project: Day 1
rails new my-awesome-app
cd my-awesome-app
rake db:migrate
68. New Rails Project: Day 1
rails new my-awesome-app
cd my-awesome-app
rake db:migrate
ruby 1.9.3-p125
rails 3.2.3
macbook air 1.8Ghz
69. incoming
http
1. Starting Up
One app server, one db, nginx
10 unicorns per app server
Unicorn // Passenger
Unicorn Passenger
Ruby Ruby VM N)
VM (times
nginx for static assets
PostgreSQL for data
Always put your DB on a
separate server
DB
Cloud
70. incoming
http
1. Starting Up
nginx
Unicorn // Passenger
Unicorn Passenger
Ruby Ruby VM N)
VM (times
DB
71. incoming
http
1. Starting Up
nginx
Simple, but no app server Unicorn // Passenger
Unicorn Passenger
redundancy, limited Ruby Ruby VM N)
VM (times
throughput
DB
72. incoming
http
1. Starting Up
nginx
Simple, but no app server Unicorn // Passenger
Unicorn Passenger
redundancy, limited Ruby Ruby VM N)
VM (times
throughput
10 unicorns = 10
concurrent requests at any DB
one time
73. incoming
http
2. Growing Up
nginx
Split into multiple App Unicorn // Passenger
Unicorn Passenger
Servers Ruby Ruby VM N)
VM (times
HAProxy to distribute load
nginx for static files found
on local file system, proxy
requests otherwise DB
74. incoming
http
2. Growing Up nginx
haproxy
Split into multiple App
Servers
Unicorn
Unicorn / Passenger
HAProxy to distribute load
Ruby VM
Ruby VM
nginx for static files found
on local file system, proxy
requests otherwise DB
75. incoming
http
2. Growing Up nginx
haproxy
Site usage grows.
Responses get slow. Unicorn
Unicorn / Passenger
Ruby VM
Ruby VM
DB
76. incoming
http
2. Growing Up nginx
haproxy
Site usage grows.
Responses get slow. Unicorn
Unicorn / Passenger
Ruby VM
Ruby VM
Started at 150ms, then
400ms, then 700ms....
DB
77. incoming
http
3. Scaling Up nginx
haproxy
Unicorn
Unicorn / Passenger
Ruby VM
Ruby VM
DB
78. incoming
http
3. Scaling Up nginx
Add MemCached (1Gb+) haproxy
Unicorn
Unicorn / Passenger
Ruby VM
Ruby VM
DB
79. incoming
http
3. Scaling Up nginx
Add MemCached (1Gb+) haproxy
Use Redis (or cookies) for
sessions (reduce db load) Unicorn
Unicorn / Passenger
Ruby VM
Ruby VM
DB
80. incoming
http
3. Scaling Up nginx
Add MemCached (1Gb+)
haproxy
Use Redis (or cookies) for
sessions (reduce db load) Unicorn
Unicorn / Passenger
Ruby VM
Ruby VM memcache
redis
DB
81. incoming
http
3. Scaling Up nginx
Add MemCached (1Gb+)
haproxy
Use Redis (or cookies) for
sessions (reduce db load) Unicorn
Unicorn / Passenger
Ruby VM
Ruby VM memcache
Add action caching
(even short TTL helps, i.e. 1min) redis
DB
82. incoming
http
3. Scaling Up nginx
Add MemCached (1Gb+)
haproxy
Use Redis (or cookies) for
sessions (reduce db load) Unicorn
Unicorn / Passenger
Ruby VM
Ruby VM memcache
Add action caching
(even short TTL helps, i.e. 1min) redis
Use AJAX to personalize
pages to make them cacheable* DB
85. Personalization with AJAX -
A brief de-tour
1. Logged in (or not) user requests a page...
2. Page is served from the cache without any
personalization (no “Hi John!”, “Logout”, etc)
86. Personalization with AJAX -
A brief de-tour
1. Logged in (or not) user requests a page...
2. Page is served from the cache without any
personalization (no “Hi John!”, “Logout”, etc)
3. on document.ready: AJAX hits the server, gets tiny
JSON data of the current user (or “not logged in”)
87. Personalization with AJAX -
A brief de-tour
1. Logged in (or not) user requests a page...
2. Page is served from the cache without any
personalization (no “Hi John!”, “Logout”, etc)
3. on document.ready: AJAX hits the server, gets tiny
JSON data of the current user (or “not logged in”)
4. JS modifies the DOM to show user’s logged in
state, any other personalization, or “Log In”.
91. Personalization with AJAX -
Why?
Because entire page can be served from
the cache (often 50Kb+ per request)
92. Personalization with AJAX -
Why?
Because entire page can be served from
the cache (often 50Kb+ per request)
No ActiveRecord and no rendering makes
it really fast!
93. Personalization with AJAX -
Why?
Because entire page can be served from
the cache (often 50Kb+ per request)
No ActiveRecord and no rendering makes
it really fast!
Recent rough test using Rails 3.2.3, ruby
1.9.3-p194, memcached: 4ms latency!!!
95. Why not page caching?
Because unlike action caching, page
caching is file-system based.
96. Why not page caching?
Because unlike action caching, page
caching is file-system based.
Because it’s more difficult to expire
97. Why not page caching?
Because unlike action caching, page
caching is file-system based.
Because it’s more difficult to expire
Because it’s more difficult to share
across many servers
98. incoming
http
4. Scaling Images nginx
haproxy
We are serving lots of
images. Nginx is
getting slammed. Unicorn
Unicorn / Passenger
Ruby VM memcache
Ruby VM
redis
DB
99. incoming
http
4. Scaling Images nginx
haproxy
We are serving lots of
images. Nginx is
getting slammed. Unicorn
Unicorn / Passenger
Ruby VM memcache
Ruby VM
Should we add more redis
balancers? Write our own?
DB
100. incoming
http
4. Scaling Images nginx
haproxy
We are serving lots of
images. Nginx is
getting slammed. Unicorn
Unicorn / Passenger
Ruby VM memcache
Ruby VM
Should we add more redis
balancers? Write our own?
DB
HELLZ NO!
101. incoming incoming
http http
4. Scaling Images CDN
cache images, JS
nginx
haproxy
Unicorn // Passenger
Unicorn Passenger
RubyRuby VM N)
VM (times memcache
redis
DB
102. incoming incoming
http http
4. Scaling Images CDN
cache images, JS
Don’t wait to use a CDN to
SERVE images, especially nginx
user-uploaded images.
haproxy
Unicorn // Passenger
Unicorn Passenger
RubyRuby VM N)
VM (times memcache
redis
DB
103. incoming incoming
http http
4. Scaling Images CDN
cache images, JS
Don’t wait to use a CDN to
SERVE images, especially nginx
user-uploaded images.
haproxy
S3 is a popular choice to
STORE images. Unicorn // Passenger
Unicorn Passenger
RubyRuby VM N)
VM (times memcache
redis
DB
104. incoming incoming
http http
4. Scaling Images CDN
cache images, JS
Don’t wait to use a CDN to
SERVE images, especially nginx
user-uploaded images.
haproxy
S3 is a popular choice to
STORE images. Unicorn // Passenger
Unicorn Passenger
RubyRuby VM N)
VM (times memcache
But it’s smart to keep a
redis
local backup copy... DB
105. incoming incoming
http http
5. Deployments and CDN
Downtime
cache images, JS
Our site is popular!
nginx
And our users hate haproxy
downtime.
Unicorn // Passenger
Unicorn Passenger
RubyRuby VM N)
VM (times memcache
redis
DB
106. incoming incoming
http http
5. Deployments and CDN
Downtime
cache images, JS
Our site is popular!
nginx
And our users hate haproxy
downtime.
Unicorn // Passenger
Unicorn Passenger
RubyRuby VM N)
VM (times memcache
They really really do.
redis
DB
108. 5. Deployments and
Downtime
We want to be able to deploy the code while
the site is running. So users are happy.
109. 5. Deployments and
Downtime
We want to be able to deploy the code while
the site is running. So users are happy.
There are several ways to do that.
110. 5. Deployments and
Downtime
We want to be able to deploy the code while
the site is running. So users are happy.
There are several ways to do that.
This solution uses DNS round robin with two
balancers, and two public IP addresses.
111. Two Cluster Solution = Almost Zero Downtime
incoming http incoming http
balancer1 balancer2
nginx nginx
haproxy haproxy
Unicorn // Passenger
Unicorn Passenger Unicorn // Passenger
Unicorn Passenger
RubyRuby VM N)
VM (times memcache memcache RubyRuby VM N)
VM (times
redis
DB
112. Two Cluster Solution = Almost Zero Downtime
incoming http incoming http
balancer1 balancer2
nginx nginx
haproxy haproxy
Unicorn // Passenger
Unicorn Passenger Unicorn // Passenger
Unicorn Passenger
RubyRuby VM N)
VM (times memcache memcache RubyRuby VM N)
VM (times
redis
DB
116. Two Clusters are cool!
Cluster 1 runs old code and is live
Cluster 2 gets new code
117. Two Clusters are cool!
Cluster 1 runs old code and is live
Cluster 2 gets new code
Old and new run in parallel, but only one
is serving live traffic
120. Migrations with Zero
Downtime?
Almost possible on a live system, if:
We are not removing or renaming columns or tables
in active use
121. Migrations with Zero
Downtime?
Almost possible on a live system, if:
We are not removing or renaming columns or tables
in active use
Migrations do not lock tables (for too long)
122. Migrations with Zero
Downtime?
Almost possible on a live system, if:
We are not removing or renaming columns or tables
in active use
Migrations do not lock tables (for too long)
Column/Table renames/deletes can be
done in two deployments instead of one
123.
124. So the app is now faster, and we
can deploy without a downtime
125. So the app is now faster, and we
can deploy without a downtime
What about email and other
long-running tasks?
126. So the app is now faster, and we
can deploy without a downtime
What about email and other
long-running tasks?
Don’t forget SPF records.
127. incoming http
Background Jobs with
Resque balancer1
nginx
But monitor it’s queues
haproxy
Must restart on reboot
Resque Workers Unicorn memcache
redis
DB
128. incoming http
Background Jobs with
Resque balancer1
nginx
But monitor it’s queues
haproxy
Must restart on reboot
Resque Workers Unicorn memcache
redis
resque-cleaner is
awesome! DB
130. Different queues for different types of jobs
Relatively easy to implement priorities for Jobs
(order queues by priority)
131. Different queues for different types of jobs
Relatively easy to implement priorities for Jobs
(order queues by priority)
Group Jobs by execution times to avoid delays
132. Different queues for different types of jobs
Relatively easy to implement priorities for Jobs
(order queues by priority)
Group Jobs by execution times to avoid delays
Resque::Worker x N
QUEUE=SlowQueue1,SlowQueue2
redis
Resque::Worker x M
QUEUE=FastQueue1,FastQueue2
133. DB Usage and complexity grows.
We are doing big joins with many
tables, and they are taking their sweet
time.
135. Solr to the Resque
Use Solr instead of doing complex joins
136. Solr to the Resque
Use Solr instead of doing complex joins
Solr reads are < 10ms
137. Solr to the Resque
Use Solr instead of doing complex joins
Solr reads are < 10ms
Sunspot Gem by default writes to Solr
from each ruby VM (i.e. unicorn)!
138. Solr to the Resque
Use Solr instead of doing complex joins
Solr reads are < 10ms
Sunspot Gem by default writes to Solr
from each ruby VM (i.e. unicorn)!
Serialize writes with Resque!
139. Solr to the Resque
Use Solr instead of doing complex joins
Solr reads are < 10ms
Sunspot Gem by default writes to Solr
from each ruby VM (i.e. unicorn)!
Serialize writes with Resque!
One master for writes
140. Solr to the Resque
Use Solr instead of doing complex joins
Solr reads are < 10ms
Sunspot Gem by default writes to Solr
from each ruby VM (i.e. unicorn)!
Serialize writes with Resque!
One master for writes
Read replicas on each app server
141. Putting it together
Unicorn Unicorn / Workers
Resque Passenger
Unicorn / Passenger
Ruby VM
Ruby VM
3. Update Solr
solr_replica
4. Replicate
solr_master
2. Read Model Info
1. Model Changed
redis
DB
144. At this size...
Automate everything
Chef or Puppet is awesome
Monitor everything
Tolerate reboots, restarts, partial failures
145. At this size...
Automate everything
Chef or Puppet is awesome
Monitor everything
Tolerate reboots, restarts, partial failures
Use OS services layer to start/stop everything
Ensures recovery after reboot
146. At this size...
Automate everything
Chef or Puppet is awesome
Monitor everything
Tolerate reboots, restarts, partial failures
Use OS services layer to start/stop everything
Ensures recovery after reboot
Capistrano tends to gets “complex”
Can also deploy with Chef
148. Choose Vendors Wisely
You can pick your own, but here is my list:
Clouds - JOYENT, EngineYard
fastest I/O cloud, but on Solaris derivative
149. Choose Vendors Wisely
You can pick your own, but here is my list:
Clouds - JOYENT, EngineYard
fastest I/O cloud, but on Solaris derivative
Automation - Chef + OPSCODE
150. Choose Vendors Wisely
You can pick your own, but here is my list:
Clouds - JOYENT, EngineYard
fastest I/O cloud, but on Solaris derivative
Automation - Chef + OPSCODE
Caching/CDN - FASTLY.COM
varnish based CDN, very fast, full power of VCL
configuration
151. Choose Vendors Wisely
You can pick your own, but here is my list:
Clouds - JOYENT, EngineYard
fastest I/O cloud, but on Solaris derivative
Automation - Chef + OPSCODE
Caching/CDN - FASTLY.COM
varnish based CDN, very fast, full power of VCL
configuration
Metrics and Performance - NewRelic
Turnkey solution, getting better every day
154. In Development
Use foreman to start dependent services (Solr,
Redis, Resque) from a Procfile
Do “Just enough” testing with Solr - it’s slow!
155. In Development
Use foreman to start dependent services (Solr,
Redis, Resque) from a Procfile
Do “Just enough” testing with Solr - it’s slow!
Deploy to single-box demo servers often using
the same Capistrano scripts used for
production
160. How Big Exactly?
200+ models
200K+ lines of RUBY source code without gems
100K+ lines of ERB, HTML and HAML templates
100+ gem dependencies
161. How Big Exactly?
200+ models
200K+ lines of RUBY source code without gems
100K+ lines of ERB, HTML and HAML templates
100+ gem dependencies
this is a real world application that’s in production today.
165. Here is why I think it is.
1.5+ hours for the full the test suite to complete
10 mins of db seeds, 30 minutes for unit tests only, etc
166. Here is why I think it is.
1.5+ hours for the full the test suite to complete
10 mins of db seeds, 30 minutes for unit tests only, etc
merges often result in integration tests going RED
167. Here is why I think it is.
1.5+ hours for the full the test suite to complete
10 mins of db seeds, 30 minutes for unit tests only, etc
merges often result in integration tests going RED
20 seconds boot-up time for Rails env (r console, etc)!
168. Here is why I think it is.
1.5+ hours for the full the test suite to complete
10 mins of db seeds, 30 minutes for unit tests only, etc
merges often result in integration tests going RED
20 seconds boot-up time for Rails env (r console, etc)!
500Mb of RSS RAM for one single-threaded web process
169. Here is why I think it is.
1.5+ hours for the full the test suite to complete
10 mins of db seeds, 30 minutes for unit tests only, etc
merges often result in integration tests going RED
20 seconds boot-up time for Rails env (r console, etc)!
500Mb of RSS RAM for one single-threaded web process
it’s a difficult undertaking to upgrade dependencies and rails
176. Let’s zoom in...
Is PERFORMANCE of the app an issue?
NO! 150ms per request avg
177. Let’s zoom in...
Is PERFORMANCE of the app an issue?
NO! 150ms per request avg
Is SCALABILITY of the app an issue?
178. Let’s zoom in...
Is PERFORMANCE of the app an issue?
NO! 150ms per request avg
Is SCALABILITY of the app an issue?
NO! 8000+ concurrent users
179. Let’s zoom in...
Is PERFORMANCE of the app an issue?
NO! 150ms per request avg
Is SCALABILITY of the app an issue?
NO! 8000+ concurrent users
Is RELIABILITY of the app an issue?
180. Let’s zoom in...
Is PERFORMANCE of the app an issue?
NO! 150ms per request avg
Is SCALABILITY of the app an issue?
NO! 8000+ concurrent users
Is RELIABILITY of the app an issue?
NO! barely any downtime in
over one year
182. Then WTF is the Problem?
Is PRODUCTIVITY of developing the app an issue?
183. Then WTF is the Problem?
Is PRODUCTIVITY of developing the app an issue?
YES! Lots of waiting all the time
184. Then WTF is the Problem?
Is PRODUCTIVITY of developing the app an issue?
YES! Lots of waiting all the time
Is MERGING source code between parallel projects difficult?
185. Then WTF is the Problem?
Is PRODUCTIVITY of developing the app an issue?
YES! Lots of waiting all the time
Is MERGING source code between parallel projects difficult?
YES! 30+ people sharing large codebase
186. Then WTF is the Problem?
Is PRODUCTIVITY of developing the app an issue?
YES! Lots of waiting all the time
Is MERGING source code between parallel projects difficult?
YES! 30+ people sharing large codebase
Is KEEPING TEST SUIT GREEN challenging?
187. Then WTF is the Problem?
Is PRODUCTIVITY of developing the app an issue?
YES! Lots of waiting all the time
Is MERGING source code between parallel projects difficult?
YES! 30+ people sharing large codebase
Is KEEPING TEST SUIT GREEN challenging?
YES! tests are brittle and long running
189. But wait, there’s more!
What about DEPLOYMENT of a large app?
Takes a long time, and small tweaks require full deploys
190. But wait, there’s more!
What about DEPLOYMENT of a large app?
Takes a long time, and small tweaks require full deploys
What about HOSTING COSTS?
Necessary to provide enough RAM for the app to be scalable.
192. RAM? Latency matters...
1 Request = 200ms on average latency
5 reqs/second on a single-threaded ruby VM process
193. RAM? Latency matters...
1 Request = 200ms on average latency
5 reqs/second on a single-threaded ruby VM process
30,000 RPM = 500 r/sec = 100 processes
50Gb of RAM @ 200ms latency
If average latency is 600ms, need 150Gb of RAM !!!
205. Smaller Applications
Contain web GUI, logic, and data
May combine with other apps
May rely on common libraries
May rely on services
206. Smaller Applications
Contain web GUI, logic, and data
May combine with other apps
May rely on common libraries
May rely on services
Typically run in their own Ruby VM
208. Consider a Typical E-Commerce Store
Users must be able to register, login, logout (profiles)
209. Consider a Typical E-Commerce Store
Users must be able to register, login, logout (profiles)
Users must be able to browse and search products,
view, and add to cart
210. Consider a Typical E-Commerce Store
Users must be able to register, login, logout (profiles)
Users must be able to browse and search products,
view, and add to cart
Users must be able to checkout
211. Consider a Typical E-Commerce Store
Users must be able to register, login, logout (profiles)
Users must be able to browse and search products,
view, and add to cart
Users must be able to checkout
Probably many other stories, such as admin, but we’ll
ignore for now.
215. One idea...
Application 1:
Marketing, Product Catalog Browser,
Search + Product Detail Page
Application 2:
Checkout, Payment, Order History, Returns
Fulfillment
Very clear user flow transfer and data separation.
217. Some things can be shared
Service:
Single Sign-on, User profiles, Login/Registration
[devise?, rest-full authentication?]
218. Some things can be shared
Service:
Single Sign-on, User profiles, Login/Registration
[devise?, rest-full authentication?]
Service:
Product Catalog data, Inventory Data
219. Some things can be shared
Service:
Single Sign-on, User profiles, Login/Registration
[devise?, rest-full authentication?]
Service:
Product Catalog data, Inventory Data
Service:
Comments, Votes, Ratings, Reviews
222. Services Technologies
Rack/Sinatra/Rails are popular, and are often an
entirely sufficient choice
Goliath is awesome if performance is important,
and if the service is mostly I/O bound
223. Services Technologies
Rack/Sinatra/Rails are popular, and are often an
entirely sufficient choice
Goliath is awesome if performance is important,
and if the service is mostly I/O bound
node.js is also a popular choice
224. Services Technologies
Rack/Sinatra/Rails are popular, and are often an
entirely sufficient choice
Goliath is awesome if performance is important,
and if the service is mostly I/O bound
node.js is also a popular choice
Implementation may change in the future, as long
as the API stays consistent
225. http
balancer / router
/checkout → checkout app
/* → catalog app
catalog app checkout app
cart
DB CSS/UI Library DB
Product Service Reviews, User Auth / Login
Inventory Comments, Profiles
Votes, Ratings
DB DB DB
226. http
balancer / router
/checkout → checkout app
/* → catalog app
catalog app checkout app
CSS/UI Library
DB DB
Product Service Reviews, User Auth / Login
Inventory Comments, Profiles
Votes, Ratings
DB DB DB
227. http
balancer / router
Extract look and feel
/checkout → checkout app
/* → catalog app
(CSS/UI) into a gem to catalog app checkout app
share across apps CSS/UI Library
DB DB
Product Service Reviews, User Auth / Login
Inventory Comments, Profiles
Votes, Ratings
DB DB DB
228. http
balancer / router
Extract look and feel
/checkout → checkout app
/* → catalog app
(CSS/UI) into a gem to catalog app checkout app
share across apps CSS/UI Library
DB DB
Create client API wrapper Product Service Reviews, User Auth / Login
gems for consumers
Inventory Comments, Profiles
Votes, Ratings
DB DB DB
229. http
balancer / router
Extract look and feel
/checkout → checkout app
/* → catalog app
(CSS/UI) into a gem to catalog app checkout app
share across apps CSS/UI Library
DB DB
Create client API wrapper Product Service Reviews, User Auth / Login
gems for consumers
Inventory Comments, Profiles
Votes, Ratings
DB DB DB
Create a single shared
“base” client gem library
232. Rails App with < 30 Models
Can run tests pretty quickly, hopefully under 5 minutes
233. Rails App with < 30 Models
Can run tests pretty quickly, hopefully under 5 minutes
Is often large enough to describe typical “clusters of
functionality”, i.e. - mini apps
234. Rails App with < 30 Models
Can run tests pretty quickly, hopefully under 5 minutes
Is often large enough to describe typical “clusters of
functionality”, i.e. - mini apps
Ruby VM might actually stay under 100Mb of RSS RAM
235. Rails App with < 30 Models
Can run tests pretty quickly, hopefully under 5 minutes
Is often large enough to describe typical “clusters of
functionality”, i.e. - mini apps
Ruby VM might actually stay under 100Mb of RSS RAM
Is more comprehensible and can be effectively
maintained by a small dev team.
236. 3rd Party Integrations
catalog app checkout app analytics financial warehouse
and ERP system management
reporting system
CSS/UI Library
DB DB
Product Service Reviews, User Auth / Login
Inventory Comments, Profiles
Votes, Ratings
DB DB DB
240. Ecosystem of Applications
Is inevitable in large companies
Scale better from team perspective
Offer decoupling and implementation hiding
241. Ecosystem of Applications
Is inevitable in large companies
Scale better from team perspective
Offer decoupling and implementation hiding
Can be individually optimized and scaled
243. API Proxy / Router
catalog app checkout app
analytics financial
and ERP
CSS/UI Library
DB DB reporting system
http://api.mycompany.com/
Product Service Reviews, User Auth / Login
Inventory Comments, Profiles
Votes, Ratings
DB DB DB
246. Example: Order Placed
Warehouse Management System needs to be updated
Analytics Engine needs to be notified
247. Example: Order Placed
Warehouse Management System needs to be updated
Analytics Engine needs to be notified
Financials needs to be updated
248. Example: Order Placed
Warehouse Management System needs to be updated
Analytics Engine needs to be notified
Financials needs to be updated
Question: which component is responsible
for updating each application?
250. 1995 Was Great
GoF Design Patterns: Observer
“...One-to-Many dependency between objects
so that when one object changes state, all its
dependents are notified and updated
automatically...”
260. Other Distributed Options
DRb - distributed Ruby (also Rinda, Starfish,
beanstalkd, etc)
DCell - actor based based on 0MQ
http://www.unlimitednovelty.com/2012/04/
introducing-dcell-actor-based.html
261. Other Distributed Options
DRb - distributed Ruby (also Rinda, Starfish,
beanstalkd, etc)
DCell - actor based based on 0MQ
http://www.unlimitednovelty.com/2012/04/
introducing-dcell-actor-based.html
All of them are a bit too low level for sharing
and consuming business events
262. I would love a library for
publishing business events
built on top
266. Future Library
Hides complexities of queues and
exchanges
Consumers declare interest in events
they care about, define persistence and
retry policy
267. Future Library
Hides complexities of queues and
exchanges
Consumers declare interest in events
they care about, define persistence and
retry policy
Publishers fire! events and forget about it
269. Future Library, ctd.
Once registered, consumers get
messages even after being offline
270. Future Library, ctd.
Once registered, consumers get
messages even after being offline
When publisher can submit an event to
the queue, it’s job is done.
271. Future Library, ctd.
Once registered, consumers get
messages even after being offline
When publisher can submit an event to
the queue, it’s job is done.
Library of business events becomes a
compliment to the set of business APIs