ANODE – Continuous Deployment with Node.js over Azure, Yosef Dinerstein

•

1 j'aime•3,333 vues

In his lecture, Yosef will present an open source project he led over the past year and will demonstrate how his team developed a platform using node.js in Windows Azure for collaborative development, hosting, and continuous deployment of Web applications. **NOTE THIS PRESENTATION CAME WITH A LIVE DEMO - THAT WILL BE UP ON THE DEVOPSCON WEBSITE** Presented at DevOps Con Israel 2013

ANODE
no spinning donuts

WIFI:
UserName: emeaguest
Password: Ad6se2f8

anode in a sentence

Rapid web services development platform
on top of Azure, harvesting node.js
strengths.

Why we built it?
Agile development on cloud
Our cloud === Azure
node.js
JavaScript
Asynchronous
Scalable
Deployable
Community
Azure support for node.js
Native support is evolving in parallel (e.g. see Azure Web Services)
ANODE is an open source project
ANODE can be used as complementary to native node.js support in Azure

Features
• Management UI
• Deployment
• Logging
• Testing
• Security
• Helping services

Management UI
WEB UI
No tools
Any browser
HTML 5
CLI
Developer friendly paradigm
Extendable
Plugins

Deployment
Fast
Seconds
Multitenant
Multiple apps
System apps
Multiple versions side by side
Integration with source control
GIT
Github
Bitbucket
Flexible

DEMO
- Introducing demo farm
- Glimpse of management UI
- Hydepark application
- hydepark.demo.msproto.net

anode architecture

User Developer

Azure load balancer Github
(Bitbucket)

Apps Apps System
apps

app discovery deploy
RP
authentication app management
private/public
console
endpoints
s
domain names configuration mgr

data proxy chronos

app lifetime

development flow

Write app code

Github
check in Source push Anode
control

DEMO
- Full development cycle
- Adding feature to a live service
- Deployment configuration

Summary
ANODE
Continuous development of WEB services on Azure
Developed and hosted over ANODE: onx.ms
Availability
In 2-3 weeks via Github

Contact
yosefd@microsoft.com
Twitter @yosefdi

Contenu connexe

Tendances

Brian Jones Resume-2016-06-2p

Brian Jones

This talk was held at a Zühlke internal meetup of architects in 2012. It explains the motivation behind DevOps and Infrastructure-as-Code, then introduces Chef, looking at the essential Chef concepts and the Chef recipe DSL. Next comes a brief outlook to Vagrant for managing VMs, Librarian for dependency management, and various Chef testing tools. Finally, different options for cloud deployments with Chef are discussed: AWS CloudFormation, Mccloud and knife-ec2.

Infrastructure-As-Code and Cloud Deployments with Opscode Chef & Co

Torben Knerr

Test-Driven Infrastructure with CloudFormation and Cucumber.

Stelligent

Using Eclipse in the Cloud to monitor hurricanes

Diyan Yordanov

SAP NetWeaver Cloud Platform - Virtual Bootcamp Introduction - Part 1

SAP PartnerEdge program for Application Development

Enterprise Cloud with IBM & Chef (ChefConf 2013)

Michael Elder

Tendances (6)

Brian Jones Resume-2016-06-2p

Infrastructure-As-Code and Cloud Deployments with Opscode Chef & Co

Test-Driven Infrastructure with CloudFormation and Cucumber.

Using Eclipse in the Cloud to monitor hurricanes

SAP NetWeaver Cloud Platform - Virtual Bootcamp Introduction - Part 1

Enterprise Cloud with IBM & Chef (ChefConf 2013)

Similaire à ANODE – Continuous Deployment with Node.js over Azure, Yosef Dinerstein

Serverless on Azure with Functions

Christos Matskas

Scalable APIs with Azure Functions

Christos Matskas

Kunal bhatia resume mass

Kunal Bhatia, MBA Candidate, BSc.

RESUME

PAULO RUVALCABA

Serverless architecture with Azure

Christos Matskas

Presentation at Android Builders Summit 2012. Based on the experience of working with ODM companies and SoC vendors, this session would discuss how to figure out the performance hotspot of certain Android devices and then improve in various areas including graphics and boot time. This session consists of the detailed components which seem to be independent from each other in traditional view. However, the situation changes a lot in Android system view since everything is coupled in a mass. Three frequently mentioned items in Android engineering are selected as the entry points: 2D/3D graphics, runtime, and boot time. Audience: Developers who work on Android system integration and platform enablement.

Improve Android System Component Performance

National Cheng Kung University

Mobile Apps are not stand alone applications running on a mobile device anymore. Apps today are complex systems with back-ends hosted on clouds, with application servers, databases, API calls to external systems, and of course a powerful app running on a mobile device. Mobile App development and deployment is further complicated with todays need for supporting multiple mobile devices, with multiple OSes, multiple versions of the OSes, multiple form factors and varied network, CPU, GPU and memory specs. DevOps - the new and growing movement addresses these development and deployment challenges. The goal of DevOps is to align Dev and Ops by introducing a set of principles and practices such as continuous integration and continuous delivery. Mobile apps take the need for these practices up a level due to their inherent distributed nature. Multi-platform mobile apps need even more care in applying DevOps principles as there are multiple platforms to be targeted, each with its own requirements, quirks, and nuanced needs. This talk will introduce attendees to the basic practices of DevOps and then take a look at the DevOps challenges specific to cross-platform Mobile apps and present Best Practices to address them.

Dev ops for cross platform mobile modeveast 12

Sanjeev Sharma

Open Source Licenses and Tools

g2ix

Spring Boot & Spring Cloud on Pivotal Application Service

VMware Tanzu

webinos and Open Ecosystems Open Governance

webinos project

Spring Boot & Spring Cloud Apps on Pivotal Application Service - Daniel Lavoie

VMware Tanzu

Deep Dive SharePoint 2013: Developing applications in SharePoint 2013: forget...

Microsoft Developer Network (MSDN) - Belgium and Luxembourg

[데브멘토 동영상] Meego for Intel Atom Processor and AppUp Center 2부 최종 이진용 Intel Korea 차장(Application Engineer) 전LG전자 소프트웨어센터 책임연구원 전PalmPalm Technology 신임연구원 전Nexen 선임연구원 중앙대학교 컴퓨터공학과 대학원 분산 및 운영체제 전공

Meego의 현재와 미래(2)

mosaicnet

App Engine overview (Android meetup 06-10)

jasonacooper

Kubecon SIG Apps December 2017 Update

Matthew Farina

Introduction and hacking OpenStack, Pycon India

Atul Jha

Reply Netcamp PoliTo - AWS IoT - Grohe and Caleffi Case Studies

Andrea Mercanti

Gerrit linuxtag2011

thkoch

citus™ iot ecosystem

DUONG Dinh Cuong

In this talk, Cheng will walk through version 2.0 of the Tizen SDK, the alpha version of which was released to developers in September; the web app development process, Tizen IDE and latest version of the SDK tools will be explained to give web developers an overview of Tizen platform. The second half of the talk will take a practical approach, focusing on how to port HTML 5 applications to Tizen. Topics covered will include tips and tricks for porting apps and how to make the most of Tizen’s extensive support for W3C/ HTML5 standards. Cheng will also discuss how the Tizen device APIs are used to ‘fill in the gaps’ in the functionality offered by the W3C APIs.

LinuxCon Europe 2012 - Tizen Mini Summit

Cheng Luo

Similaire à ANODE – Continuous Deployment with Node.js over Azure, Yosef Dinerstein (20)

Serverless on Azure with Functions

Scalable APIs with Azure Functions

Kunal bhatia resume mass

RESUME

Serverless architecture with Azure

Improve Android System Component Performance

Dev ops for cross platform mobile modeveast 12

Open Source Licenses and Tools

Spring Boot & Spring Cloud on Pivotal Application Service

webinos and Open Ecosystems Open Governance

Spring Boot & Spring Cloud Apps on Pivotal Application Service - Daniel Lavoie

Deep Dive SharePoint 2013: Developing applications in SharePoint 2013: forget...

Meego의 현재와 미래(2)

App Engine overview (Android meetup 06-10)

Kubecon SIG Apps December 2017 Update

Introduction and hacking OpenStack, Pycon India

Reply Netcamp PoliTo - AWS IoT - Grohe and Caleffi Case Studies

Gerrit linuxtag2011

citus™ iot ecosystem

LinuxCon Europe 2012 - Tizen Mini Summit

Plus de DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

PRINCIPLES OF OBSERVABILITY // DANIEL MAHER, DataDog

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

THE PLEASURES OF ON-PREM, TOMER GABEL

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

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

SLO DRIVEN DEVELOPMENT, ALON NATIV, Tomorrow.io

DevOpsDays Tel Aviv

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

ONBOARDING IN LOCKDOWN, HILA FOX, Augury

DevOpsDays Tel Aviv

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

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

DevOpsDays Tel Aviv

Plus de DevOpsDays Tel Aviv (20)

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

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

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

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

PRINCIPLES OF OBSERVABILITY // DANIEL MAHER, DataDog

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

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

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

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

THE PLEASURES OF ON-PREM, TOMER GABEL

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

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

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

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

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

FLYING BLIND - ACCESSIBILITY IN MONITORING, FEU MOUREK, Icinga

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

SLO DRIVEN DEVELOPMENT, ALON NATIV, Tomorrow.io

ONBOARDING IN LOCKDOWN, HILA FOX, Augury

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

ANODE – Continuous Deployment with Node.js over Azure, Yosef Dinerstein

1. ANODE no spinning donuts WIFI: UserName: emeaguest Password: Ad6se2f8

2. anode in a sentence Rapid web services development platform on top of Azure, harvesting node.js strengths.

3. Why we built it? Agile development on cloud Our cloud === Azure node.js JavaScript Asynchronous Scalable Deployable Community Azure support for node.js Native support is evolving in parallel (e.g. see Azure Web Services) ANODE is an open source project ANODE can be used as complementary to native node.js support in Azure

4. Features • Management UI • Deployment • Logging • Testing • Security • Helping services

5. Management UI WEB UI No tools Any browser HTML 5 CLI Developer friendly paradigm Extendable Plugins

6. Deployment Fast Seconds Multitenant Multiple apps System apps Multiple versions side by side Integration with source control GIT Github Bitbucket Flexible

7. Logging Instant Queriable Persistent

8. DEMO - Introducing demo farm - Glimpse of management UI - Hydepark application - hydepark.demo.msproto.net

9. anode architecture User Developer Azure load balancer Github (Bitbucket) Apps Apps System apps app discovery deploy RP authentication app management private/public console endpoints s domain names configuration mgr data proxy chronos app lifetime

10. development flow Write app code Github check in Source push Anode control

11. DEMO - Full development cycle - Adding feature to a live service - Deployment configuration

12. Summary ANODE Continuous development of WEB services on Azure Developed and hosted over ANODE: onx.ms Availability In 2-3 weeks via Github

13. Contact yosefd@microsoft.com Twitter @yosefdi

ANODE – Continuous Deployment with Node.js over Azure, Yosef Dinerstein

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (6)

Similaire à ANODE – Continuous Deployment with Node.js over Azure, Yosef Dinerstein

Similaire à ANODE – Continuous Deployment with Node.js over Azure, Yosef Dinerstein (20)

Plus de DevOpsDays Tel Aviv

Plus de DevOpsDays Tel Aviv (20)

ANODE – Continuous Deployment with Node.js over Azure, Yosef Dinerstein