Bestand wählen
Merken

The Art of Ember Deployment

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
a the and so on and and and the and the and the highest hammered out it is going to be here and so that's we got going on here the order of at poignant mining is the nearly a for those of you I don't know I live in Manhattan out my wife and 2 daughters I write a lot of room in java scripts of Objective C and we're not doing bad stuff coding I love to play beach volleyball the online organizer of Amber JS MYC made seeing some footage earlier in the day and please come join our community we love have speakers met account so don't hesitate to reach out and schedule something I run a fun kind of hybrid business really have a product as well as you have a consulting and we can be helpful in any of those side let me know let's jump into it so the how we deliver software has evolved over time I would say this is
kind of their way to say that it started annular vault set tapes this is really where I got started playing games on all Torrey than lot of time with these guys the on and then if you look in your on if that today when you checked in on probably had 1 of these guys and they're actually looked a lot like those and then finally came model beloved Internet and with that I think the browser which he has become the most ubiquitous at runtime the world and then start off in a car that way but what about going and it became pretty amazing and so delivering software for most of us became an had we delivered via the web and in the beginning resist static HTML set sent from a fairly low powered server to the browser eventually that became dynamic HTML sent from some 1 more powerful servers the browser and then can arise in the server side out frameworks I'm again delivering by red representation additional representations of that at state with each request the browser and finally we came to today with them becomes to and where we're delivering an H C L and jobless the payload and then interacting with an API that really having the entire 1 time the in the browser and the you know we we may take what I just said for granted but of course you know willing give its instead it best the future is already here it's not evenly distributed for as many of us as are here in this room there are many more people and industry who have yet to arrive at this kind of browser at paradigm i and for many of us here in the room we're still holding on to on some of our deployment techniques from the server at days and even though we moved to this new paradigm effort I want to talk about today that it is after all we no longer use CD-ROM duplicators to deploy software and it's kind of a funny picture and the reason I included even though it's a little blurry is that In my very 1st off company which kind of started around the dawn of the web on this was getting 1 of these was a game-changer for us I mean it it changed our lives but but we also no longer undeployed FTP files individually anybody recognize this program of the facts so awesome somebody at least as old as I am and so 1 is the web server the server where that point approach simplified it's copying all files servers restart the server processes pretty simple proposed points you can do that copy files step more elegantly I get push your Twitter BitTorrent and Dr. containers if you're have and and you probably want your rolling restart to avoid downtime so the question is is the server rapid planning approach right for Member apps and you can probably guess by the fact that I'm up here talking to you that my answer to that is no and so let's look at why start with the real basic flow here so browser makes initial request for your and wrapped requests index at TML from your server your server comes back with some with that in HTML response and that response contains within it on a script tag that points to a finger printed on dollars to file so in this case they act as the C 1 2 3 but task so the browser courses that page a short time later makes the request for that a script and comes back to the server services just got it here you go and wrapped news all's well but during deployments this doesn't necessarily go so smoothly because there is a moment in time during the during a rolling deployment where that request for the HTML comes into the server it's factor reference to you at the SADC 1 2 3 the
request is made in a right at that moment before the request is made your deployment for structure has flipped over traffic to the new server and so the new server comes up in that the new the new new deployment you now have a new fingerprinted Dallas 5th package APK STDs 4 5 6 and when it gets a request for this 1 2 3 yeah for for not found user gets a hiccup warrior 218 they refresh the page and I go everything's fine will just ignore that modestly not agree experience and so the lesson here is to keep static assets working during rolling restart pure using this traditional approach somehow you got keep all the old and new versions of these assets around however this the few minutes during the deployment of
1 way to do this is with many of us probably do is deployed these assets to CDN and just removed old ones for a while our maybe never now consider considering storage costs instance so another aspect to think about is how users interact with the absent in this browser that paradigm because today it's not uncommon for a user to be on your site for 5 10 15 minutes in this 1 kind of page load fuel and so what happens during this when you're doing deployment as well that it's it's to known JavaScript user starts doing their thing requests and J. Sun from the server and then around that point time you decide they have got some nifty new feature I'm going to deploy you place in new jobless 15 API change to go with it and of course this user who's on this yellow timeline up here doesn't have a new job script writers refresh the page and and so when they next try to make any request that API assuming that you have some sort of breaking change their they're going to get some sort of error and so the lesson here is that
whether we think about it this way or not we have multiple versions of a and rapidly use of what's ever new version and new users are getting and you have the previous version that guide users who have been on the site for a few minutes on our parties and so we somehow need or API leaning backwards compatible for at least the length of a user session it and so what I'm listening you based on what we just looked at it is that the idea of Virginia and were at your server at API act together as as as a single version number with a single release process is a lie and we can embrace this this fact choose honesty and give our and wrapper separate repositories suffered versioning scheme a separate release process we can learn some lessons here from the way we think about the native app ecosystem here and it's and that's part of it taken for granted that your that have multiple versions of a native app while talking to your API on in which you need to do is to keep your API working for those older clients for some period time decide to end of life then at some point but you certainly don't wanna do that kind of each release you go from the actor the app and you would never consider for example trying to timely release of your API change with when your app it's approved by Apple ordered through the Android submission process right that was a pretty silly so we can learn from these native apps and see that there this requirement buys a certain amount of freedom and a bunch of the coupling and so for example you might have multiple apps and apps for talking to a single API and you might have builds the out being tested running against your production API and we think a learning embrace these things we can we can and should be the same approach for Amber apps assuming a we're versioning in deploying these things independently but there is a big workflow difference between native apps remembrance and that's how Absolon somehow the updated and the the key difference here is that instead of an actor an OS being responsible for updating launching was responsible here is HTML it's to know you can think of as the bootstrapping engine for the emperor and this the problem was seems pretty obvious but when you fall through the implications to what is a mean for your deployment sends out there some pretty serious implications for we need to think about for parties HTML pages is you know pages that are shopping apps need to point a finger printed jobless and CSS that they can't be fingerprinted themselves right they need to be a stable euro they have a certain matter were significant so you would wanna lose your say your app bundle before your vendor bundle on in 5 years using a strategy strategy like that and they're really also really good place to provide an environment specific configuration Turin graphic you don't really want big into Europe dust In addition if you can serve up this HTML comments on the same domain you're API negative sidestep have all the cost complexity and that comes along with I'm having separate domains for those finally caching should be minimal to no 1 so that when you you are deploying new version you're delivering it to new users as the so the conclusion here is that each team males be managed and deployed as part of your static asset fields so that's really part of the amber apropos and build process but somehow to be deployed to your API Server your app server and ideally in green quarterly update should not require redeploying server code on and it shouldn't require restarting server processors and back when we were 1st talk 1st building Amber wraps we were deploying and perhaps together and making a small Java change a CSS change meant a 5 to 10 minute the point process for what really matters static assets which is kind of insane so here is a kind of a sketch of the idea replying are in the bottom here were deploying a JavaScript CSS and images of static assets to static asset server serving those at the browser and that's how we got our API Server deploying serving up API requests any kind of non-timber dynamic pages as well as the HTML for JavaScript that and so the question is how do we get our HTML from our amber endeavor CI environment on onto that PIC so 1 possibility is we could simply copy of the file system but in a lot of modern poem environments this is ephemeral and so that's not really a great approach we could deployed as on and have already got territory castle were kind of read out of the that HTML artistry and serve it up hominids viable but 3 reads can be pretty slow and we certainly want this page to be fast and like we said to have a lot of small very small amount of cashing in next so we can deploy quickly and so what is the what's a good kind of low latency of persistent place to put this so we are addressing our environment that turns out to be a pretty good fit not the only effect on but for cross is a good 1 so for example but it as an example how this looks a simple environment this is that's implementation with the Railsback and we've got our HTML the being deployed into it's a real server reading at its to no AdaGrad medicine serving it up or acetic acid food S 3 with CloudFront sitting in sitting in front of as a CDN and this process turns out to work really well and not only does it solve the problems that we looked at earlier on but it also opens up the huge world of emerging possibilities die so what are some of us or 1 the things that we realized really quickly that was was possible here is that we can preview before activating so we deploy on a new so a new batch of HTML pointing to the static assets I'm into our server environment we don't necessarily have to start serving up that immediately draw users instead we can kind of keep there and serve it up only given a particular
query strings of example they released query parameter of identifying a particular release that we want a preview so here a developer can I look at very new code running in the production environment talking to their production API Server before any user sees the level of confidence that you have when you actually I actually decide flip that switch is pretty substantial pretty confident that the world is not gonna block about point and certainly we talk about deployment like to be take those steps with confidence so we can also do something really interesting which is because we have this HTML passing from Radice your API Server app server to a browser we can take advantage of that moment and do a little HTML rewriting we wanted to now why would you wanna do this ball here's an example this is an example rails controller comm obviously works in any kind of back and and online 3 were gravity HTML in online for we're doing is we're serializing J. Sun and Jason representation of the current user and then we're sticking out into a meta tag a come down with the HTML and what that means for our that is as it's really not doesn't need to be some kind of weight do in AJAX request for information about current user before can make some initial decisions about routing would you I show a login screen or do I write immediately to our is due to the content of the delusions looking for and this is just a nice kind of used to this that initial experience and there's a bunch of other use cases where do you know a tiny bit of rewriting here can be really powerful on I'm adding CSR of tokens perhaps I including dynamic analytics grams for things like Google Analytics metrics excetera on as well as embedding than configuration to control things like feature flags the that might simply be seen setting of global that your consulting onto would determine whether flights enabled or disabled closely related to this is the ability to easily do AB test there's to style is the 1 using the kind of feature flight style I just described where you can but it uses into an area of the attorney feature on or off depending on what the other 1 we used when we're data on a full-fledged redesign of our and wrap and we said that it would be nice if the test test this before we cut over position dramatic differences also what if we deploy into 2 different writers pockets of set so have 2 kinds of current HTML paradigms but users into an AB test using RAD framework and then serve 1 up and in of 1 2 1 2 1 group 1 to the other 2 but time we actually did fully cut over we felt really confident that our redesign was indeed an improvement but and finally I and I don't I don't love this as the parent you ibid sometimes it's appropriate and you can use the fact that you were servers being notably notified when a new version of a rap is deployed to communicate via WebSockets Areva your purse infrastructure is down to rouse say hey there's a new version available you should fresh now take advantage of it so I'm all this stuff what I just described to you is I've some ideas 11 talking about for about a year now I'm kind of in public 1st Orelle's how about 11 months ago and since then a bunch of people of stepped up and run with a lot of these ideas in create open source implementations around so I want to take a look with you at some of those open-source implementations today now there's a bunch up here not gonna go into depth and all of them but the 1st thing that I did to kind of start to filter these out ways to save you know what we want to be developing at an embassy life and makes a ton of sense to the building deployment of tooling on top of whatever still I already has no brings to the table so let's filters down to just the embassy alive based acts now and he's there were 3 that really embraced the kind of this kind of assets HTML distinction that we talked about earlier and and those 3 were ever deploy fine and builds an embassy elided point and so I started doing some research and kind of looking at the implementation of each of these it turns out that Member deploy and and embassy line deployed share the same kind of idea of having a plug-ins architecture and so for example if you remember the slide were like talk about deploying to register you may not have right it's in your environment certainly when 1 reading just for this maybe have another low-latency store Mongol or Cassander or you know push customizable will do just fine for this so well it turns out that you both on the on changes in microclimate developed these 2 projects I'm talking to that same conclusion like this should be really should be affordable and it turns out the front and bills started life offers a fork of member deploy coming from and builds is on ambitious project that has both the client side women infrastructure as well as a whole kind of rails engine implementation the back and for implementing on the server side pieces embassy aligned unemployed has the best name in my in my opinion right and animates makes sense that's what it is that's what you'd expect it to be named on so and it's the ever deployed has the biggest ecosystem entities and it had some about for work no well put together the plug-ins you to do different types of deployments the playing your S 3 up here in Europe Additional file to S 3 instead of 2 Matisse and there's some folks down it from a Microsoft contributed and as a component and so on to some good momentum around that and so what we did just last week is we pull together a conference call and we were able to pull together in about 24 hours thanks to Twitter's new group Dm functionality and and on that call and we started to merge these 3 projects if if
so instead of 3 also projects each with 1 or 2 maintainers we now have 1 Austin project on with the team of now 6 people because in addition to my compliance insult offline trying to inherent chambers remain tended to the projects and it's described and somehow this is open-source luck would have it had been shelters jump in and an enormous help and you know how I found out there doing this and so the team is is a tremendous and we're really excited about I'm moving forward and we move the project from some from michael's domain Michael's I help users underneath embassy aligned rely on thanks to help from staff and so we're really excited about making this a more well polished well-oiled machine that's going to be on the kind of a one-stop-shop for getting employment set up for Member apps and this experience to me is what had account is all about and it's going from idea to you a few different implementations were experimenting with are concepts that as far as how best to approach it want to now kind of coalescing under 1 kind of Amber approach to the problem so where we going from here the roadmap of for the next release is 0 4 0 it's it's relatively a small step to take making sure that the ecosystem that has grown up around on member deploy its moved over successfully to the new new name in new infrastructure in this is pretty straightforward and we wanna provide migration instructions for users of the old embassy like employing on we were also deprecating J sum this configuration in favor of a job script file that you be easily and consume environment variables for sensitive credentials and so forth and timing for this is broken tablets released by the end of this week the roadmap for us the roadmap for 0 . 0 we're really excited about and we're looking for input on this to use you can visit the repo and look look at the deployment pipeline as you come in and China and were but we're looking to move to a what we call that a pipeline hopes and plug-ins architecture and it's taking the plug-in approach that has the currently was of evolving around and the boy and moving into new model really lot after the amber and approach in these plug-ins and you will be amber add-ons themselves they'll get to leverage all the Member saliva structure that already exists there but we're going to be adding a oppose deploy hopes that we can easily on communicator slack Iousy channel with each deployed on some to make details who could deploy are except time happens at a etc. on and we're looking to provide some great documentation for plugin developers this ecosystem can flourish and will be providing a lot of support by that the people who are were looking to you add audience here and finally embassy lifetime builds which as I mentioned is 1 of the most ambitious cut takes on this has been going to become a plugin for embassy lot so that's going help really help us exercise sorry PI early to make sure they were arriving at the right ideas and the basic architecture like I kind of alluded to just now ever so deployed plug-ins will be embassy like and and with an additional keywords will be auto-discovered on a wired up you obviously need to provide some of your own configuration for to be able to successfully talk to means that the the back and services involved in your deployment and the goal is that you be able to deploy from either your development environment or from your CI environment so that they'll be both some nice interactive tools to work with the McMahon line as well as on kind of silent I had lists tools are and the plug-in kind of hopes that these pollutants can implement on are listed here will deploy a build up they'd assets of the index activated did deployed as well as list which lets you look at the most recent deployments and choose to activated particular 1 roll back to particular 1 so the basic usage patterns will look like this and you will have configured 1 or more a deployment targets able to say member deploy staging and that will deploy your assets and your HTML to the configured staging deployed target based on the plug ins and you guy in black thing release and notify your group chat so what made mistakes news Ember deploy a role that staging go back to the most recently activated version also sent a notification I wanna consider what you should be releasing Amber deploy list is going to have to give you a list of recently deployed things for that target it's also found for hopefully for most plug-ins can be able to give you a preview your like described earlier so as a developing can grab that take a look and have once kind of sanity check before you decide what version of the amber up to activate to actually perform the activation of the past the identified this identifier number 2 . activate and and the band that usage of everything I just described is not something that some of some of it exists today in 0 3 0 I will exist in 0 4 0 a lot of it is going to be on changing somewhat 4 0 5 0 so again looking for input for those of you who have implemented place solutions on yourself I know everybody in this room who has happened production has done that and talk to us about what you would look to see but beyond 0 5 0 but we would like to support deployment to name pockets to support this kind of A B testing data testing things we talked about ensure that you've used apps where on the allowed and use you to kind toggle between classic and beta right so that you can get people starting to experience them a new version without necessarily putting them at risk because it doesn't have all the features that your initial you current version does and we like enables deployed that support that scenario pretty clearly but and then beyond that entails a gun 0 5 0 I talk to some of folks where a deploying HTML is not a great fit for them it makes more sense for them to have what the service continue to kind of render the overall HTML but instead we want to be able to deploy configuration information so what are the JavaScript assets were the CSS at CSS assets the configuration options that I'm taking kind of from my static field and then letting in the server merge them with the configuration options of my servers striving to be able to produce this page got something like that so and I would see we talked just talk about this 1 that this 1 that that's the same slide so and so in addition uh as I said your use case is your ideas on how come talk to us but to me this experience over the last year and so on and then in the last week has been really ungrammatical while what I love about this community and when we got on a conference call on last Tuesday and we had 5 people in the call so that most of whom they know each other and I had come conversations together because we have a common mind-set from what we've learned by watching Amber project of all a common set of tools that were we become good at using from embassy allied to get how to slack you you know I A C but we basically were able to make some decisions together that the that this merger is the right move and the productive as a team In literally a matter of minutes was a pretty astonishing thing and really kind of this this paradigm which I know a lot of experience in open-source already is unparalleled in the history of humanity so that you know given to the to have really nice it's it's pretty Austin's and so 1 last idea that I wanted to just throw out as something we can talk about later as his work with fast and and so I have on the answers to the of thought about it not too long but 1 possibility is that in this scenario is that your fast food server could sit in front of your API Server but it could be reading HTML and from your comment API server proxy API API calls back come and catching your job script locally on so there's certainly is a much simpler scenario for desperate server if you want take advantage of all the possibilities that is that that I described earlier we may want to consider having a relationship between nor fast it's Avery Kassovitz a little bit more robust and with so anyway this idea something I would really love to talk about party here later today with with folks so the thinking about it and the with that of this is attributed to Steve Jobs there no it's true but are real artist ship on real artists deploying and I thank you to everybody who's kind of helped make this particular journey of possible to small story in a kind of overall arc of the amber story on it's it's it's it's an exciting 1 1 that I feel really lucky to be apart so keep in touch I joined the moniker interested in this stuff down and it's not just a ready to take advantage of a nice new conventions for the next you know the
real and and
and
q
Selbst organisierendes System
Applet
EDV-Beratung
Biprodukt
Data Mining
Objekt <Kategorie>
EDV-Beratung
Scheduling
Wechselsprung
Software
Rhombus <Mathematik>
Skript <Programm>
Hybridrechner
Ordnung <Mathematik>
Hydrostatik
Programmierparadigma
Punkt
Momentenproblem
Browser
Selbstrepräsentation
Dynamic HTML
Versionsverwaltung
Internetworking
Homepage
Programmierparadigma
Skript <Programm>
Punkt
Addition
App <Programm>
Internetworking
Prozess <Informatik>
Mosaicing <Bildverarbeitung>
Magnetbandlaufwerk
Wurm <Informatik>
Teilbarkeit
Filetransferprotokoll
Dienst <Informatik>
Software
Menge
Twitter <Softwareplattform>
Automatische Indexierung
Rechter Winkel
Server
Versionsverwaltung
CD-ROM
Aggregatzustand
Server
Filetransferprotokoll
Automatische Handlungsplanung
E-Mail
Framework <Informatik>
Homepage
Task
Hydrostatik
Benutzerbeteiligung
Informationsmodellierung
Software
Spieltheorie
Endogene Variable
Elektronischer Fingerabdruck
Skript <Programm>
Fünf
Optimierung
Datenstruktur
Datei-Server
Elektronische Publikation
Rechenzeit
Browser
Rechenzeit
Elektronische Publikation
Datenfluss
Menge
Endogene Variable
Hydrostatik
Domain <Netzwerk>
Prozess <Physik>
Punkt
Dokumentenserver
Browser
Applet
Bootstrap-Aggregation
Versionsverwaltung
Komplex <Algebra>
Ähnlichkeitsgeometrie
Strategisches Spiel
Homepage
Eins
Spezialrechner
Client
Hausdorff-Dimension
Prozess <Informatik>
Code
Minimum
Programmierparadigma
Skript <Programm>
Dateiverwaltung
Punkt
Elektronischer Programmführer
Umwandlungsenthalpie
App <Programm>
Addition
Dicke
Prozess <Informatik>
Dokumentenserver
Güte der Anpassung
Gebäude <Mathematik>
Applet
Nummerung
Humanoider Roboter
Biprodukt
Frequenz
Arithmetisches Mittel
Datenfeld
Rechter Winkel
Client
Strategisches Spiel
Server
Versionsverwaltung
Programmierumgebung
Faserbündel
Fehlermeldung
Instantiierung
Lesen <Datenverarbeitung>
Fitnessfunktion
CDN-Netzwerk
Server
Web Site
Subtraktion
Kontrollstruktur
Mathematisierung
Zahlenbereich
Implementierung
Interaktives Fernsehen
Kolmogorov-Komplexität
Dienst <Informatik>
Code
Homepage
Hydrostatik
Multiplikation
Domain-Name
Reelle Zahl
Kommunalität
Mobiles Internet
Skript <Programm>
Booten
Coprozessor
Speicher <Informatik>
Konfigurationsraum
Bildgebendes Verfahren
Implementierung
URL
Cross-site scripting
Trennungsaxiom
Soundverarbeitung
Videospiel
Diskretes System
Konfigurationsraum
Einfache Genauigkeit
Gasströmung
Quick-Sort
CDN-Netzwerk
Last
Betafunktion
Mereologie
Stapelverarbeitung
Lie-Gruppe
Umsetzung <Informatik>
Gewichtete Summe
Browser
Service provider
Kreisbogen
Homepage
Spezialrechner
Dynamic HTML
Client
Softwaretest
Typentheorie
Fahne <Mathematik>
Gruppe <Mathematik>
Mustersprache
Radikal <Mathematik>
Skript <Programm>
Gleitendes Mittel
Gerade
Softwaretest
App <Programm>
Addition
Gebäude <Mathematik>
Strömungsrichtung
Biprodukt
Meta-Tag
Entscheidungstheorie
Dienst <Informatik>
Token-Ring
Menge
Rechter Winkel
Client
Server
Programmierumgebung
Repository <Informatik>
Lesen <Datenverarbeitung>
Zeichenkette
Tabelle <Informatik>
Fitnessfunktion
Maschinenschreiben
Subtraktion
Mathematisierung
Analytische Menge
Homepage
Open Source
Virtuelle Maschine
Kappa-Koeffizient
Mailing-Liste
Domain-Name
Variable
Informationsmodellierung
Bereichsschätzung
Reelle Zahl
Migration <Informatik>
Datentyp
Vererbungshierarchie
Inhalt <Mathematik>
Datenstruktur
Konfigurationsraum
Videospiel
Architektur <Informatik>
Open Source
Indexberechnung
Gasströmung
Plug in
Elektronische Publikation
Kontrast <Statistik>
Chatten <Kommunikation>
Betafunktion
Gamecontroller
Impuls
Bit
Sensitivitätsanalyse
Konfiguration <Informatik>
Punkt
Gemeinsamer Speicher
Dokumentenserver
Selbstrepräsentation
Gruppenkeim
Versionsverwaltung
Login
Template
Fahne <Mathematik>
Prozess <Informatik>
Gamecontroller
Programmierparadigma
Volumenvisualisierung
Schnitt <Graphentheorie>
Parametersystem
Lineares Funktional
Softwareentwickler
Filter <Stochastik>
Topologische Einbettung
Klassische Physik
Volumenvisualisierung
Abfrage
Systemaufruf
p-Block
Ein-Ausgabe
Gesetz <Physik>
Konfiguration <Informatik>
Softwarewartung
Rechenschieber
Arithmetisches Mittel
Datenfeld
Gruppenkeim
Twitter <Softwareplattform>
Automatische Indexierung
Projektive Ebene
Information
Proxy Server
Gravitation
Telekommunikation
Server
Gewicht <Mathematik>
Ortsoperator
Stab
EDV-Beratung
Implementierung
Zahlenbereich
Gebäude <Mathematik>
Framework <Informatik>
Code
Zusammenhängender Graph
Booten
Speicher <Informatik>
Softwareentwickler
Hilfesystem
Cross-site scripting
URL
Linienelement
Diskretes System
Betafunktion
Konfigurationsraum
Token-Ring
Mailing-Liste
Migration <Informatik>
Videokonferenz
Flächeninhalt
Tablet PC
Computerarchitektur
Videokonferenz
Rhombus <Mathematik>
Dienst <Informatik>
Ereignishorizont

Metadaten

Formale Metadaten

Titel The Art of Ember Deployment
Serientitel Ember Conf 2015
Autor Melia, Luke
Lizenz CC-Namensnennung - Weitergabe unter gleichen Bedingungen 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben.
DOI 10.5446/34741
Herausgeber Confreaks, LLC
Erscheinungsjahr 2015
Sprache Englisch

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract My team and I decided to invest in making our deployments awesome. When I told people about our approach, the community responded with excitement and new OSS implementations. This talk will show you how to make your team’s deployments delightful and empowering instead of slow, clumsy and frustrating. I'll take you through the key concepts and show you the open source tools that are now available.

Ähnliche Filme

Loading...
Feedback