JSUG SpringOnePlatform 2016報告会 Case study2 - feed back - springoneplatformTakahiro Fujii
?
JSUG勉強会?SpringOne Platform 2016 報告会!
https://jsug.doorkeeper.jp/events/50931
で発表させて頂いた、case studyのfeedbackになります。
This is the Japanese Feedback document of SpringOnepPlatform 2016 conference.
JSUG SpringOnePlatform 2016報告会 Case study2 - feed back - springoneplatformTakahiro Fujii
?
JSUG勉強会?SpringOne Platform 2016 報告会!
https://jsug.doorkeeper.jp/events/50931
で発表させて頂いた、case studyのfeedbackになります。
This is the Japanese Feedback document of SpringOnepPlatform 2016 conference.
The document discusses the roles and relationships between development (Dev) and operations (Ops) teams, and introduces the DevOps approach. It notes that traditionally there has been a disconnect between Devs and Ops that results in inefficiencies. DevOps aims to bridge this gap through a collaborative mindset and practices like automating infrastructure provisioning and deployments, implementing continuous integration/delivery, monitoring metrics, and breaking down silos between teams. Specific tools mentioned that support DevOps include Puppet for configuration management and Autobahn for continuous deployment.
10+ Deploys Per Day: Dev and Ops Cooperation at FlickrJohn Allspaw
?
Communications and cooperation between development and operations isn't optional, it's mandatory. Flickr takes the idea of "release early, release often" to an extreme - on a normal day there are 10 full deployments of the site to our servers. This session discusses why this rate of change works so well, and the culture and technology needed to make it possible.
The document discusses DevOps and operations as code. It describes how development teams use source control and agile methodologies while operations teams traditionally do not. DevOps aims to bring agile development practices to operations by treating infrastructure like code. This involves using configuration management, roles, recipes, and tools like Chef to define and provision infrastructure in a code-based, reusable way. The document also outlines Opscode's offerings of Chef for configuration management and the Opscode Platform for managing Chef clients.
Debugging,Troubleshooting & Monitoring Distributed Web & Cloud Applications a...Theo Jungeblut
?
In the past, applications where created as monolithic entities running on a single server. If this is the past for you, too, you will have experienced the downside of modern distributed and cloud applications, as debugging, troubleshooting, and monitoring is not easily accomplished with traditional approaches.
Within this session, we will explore different possibilities for collecting and analyzing the needed information to solve issues on modern distributed application and discuss the advantages and disadvantages of each approach like debugger, log files, performance counter and third party solutions. The focus of this session will be on Developer and DevOps need, as increased release cycles and third party dependency more and more result in the need for troubleshooting also on production system, rather than in an isolated test environment.
This session requires a solid understanding of distributed applications and knowledge of SOA, but most principles also apply to and can be beneficial for more traditional application design approaches. The used code examples are in .NET but the shown principles generally apply to other languages, too, and shown software is often available for a variety of environments.
This joint webinar with Neebula Systems CTO Ariel Gordon and DBmaestro CTO Yaniv Yehuda highlights the critical features in best practices and tools that are required to address the new challenges to your organization.
This document contains a collection of letters, numbers, symbols and punctuation marks with no discernible meaning or organization. It does not convey any clear ideas, concepts or information that could be summarized in 3 sentences or less.