The Pivotal Engineering Dojo: Earning Your Black Belt in Cloud Foundry Engineering (Cloud Foundry Summit 2014)

This document discusses the seven deadly sins of microservices and how to avoid them. The sins include lusting after new technology without consideration for operations, gluttony by not implementing circuit breakers, greed in creating too many small services, sloth by not properly separating services, wrath from ignoring issues in distributed systems, envy of other teams' deployment processes, and pride in thinking tests are not needed. The document provides recommendations to help address each sin such as starting small, service ownership, automated testing, monitoring, and continuous delivery practices.

This document provides an introduction to DevOps. It defines DevOps as a software development method that stresses communication, collaboration, integration, automation, and measurement between software developers and IT professionals. Traditionally, these groups worked in silos with barriers between development and operations. DevOps aims to break down these silos by having development and operations work more closely together through practices like configuration management, infrastructure automation, deployment automation, and monitoring. This mindset shift and cultural change can provide benefits like improved feedback, collaboration, agility, disaster recovery, and faster testing and deployment. Common DevOps tools include infrastructure as a service providers, virtualization platforms, and containerization tools.

Christian Posta, principal architect at Red Hat discusses how to manage your data within a microservices architecture at the 2017 Microservices.com Practitioner Summit.

Talk delivered at Domain-Driven Design Exchange 2018 More Domain-Driven Design related content at: https://domaincentric.net/

Slides from my talk at ALT.NET Cork. Unlike centralized version control systems, the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects.In this session I'll take you through a quick tour of the essential git commands with some demos.We'll cover branching and merging strategies, pull requests ,working on open source (GitHub etc), git clients and git deployments to the cloud.

- Project Kudu is an open source .NET Foundation project that powers deployments and hosting for Azure Web Apps, WebJobs, and Mobile Services. It provides features like configurable build steps, diagnostic tools, and APIs. - Azure Web Apps provides auto-scaling, high availability, continuous deployment from sources like Git, and supports languages like .NET, Java, PHP, Node.js, and Python. - Kudu provides access to sites through its console and APIs, allowing diagnostic dumps, file browsing, and customizing deployment pipelines through scripts.

This document summarizes Nicolas De Loof's talk about patterns for developing applications in the cloud. The talk discusses scaling applications horizontally and vertically, keeping stateless designs, using standards, and designing for failure. It also emphasizes continuous integration, deployment, and delivery practices like managing infrastructure as code and enabling zero downtime deployments.

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/10fVilQ. Yoni Goldberg describes some of the technological innovations that have helped Gilt to reach its current size, and highlight some of the core challenges that the company's engineering team continues to face. He also discusses what every tech team needs to consider and address before heading down the path of building a first-class micro-services architecture. Filmed at qconnewyork.com. Since joining Gilt at 2010 as a platform engineer, Yoni Goldberg has been leading a variety of personalization efforts and other customer-facing initiatives--including the Gilt Insider loyalty program, the post-purchase experience, and SEO/optimization efforts. Prior to joining Gilt, Yoni worked at Google, where he wrote his master's thesis on Fusion Tables.

This document summarizes serverless design patterns and tools. It begins with a brief history of cloud computing and an introduction to serverless computing. Common serverless use cases like event-driven applications and stream processing are described. Several serverless patterns are then outlined, such as hosting a static website or REST API using AWS Lambda and API Gateway. Finally, the document demonstrates a serverless application and discusses future directions for serverless technologies.

A talk I gave at the London Splunk User Group in July of 2014. A brief overview of why choose Ansible over the other options, then some live demos of configuring certain bits of Splunk with Ansible. Intended to be a taster of what's possible. All the Ansible playbooks are shared on Github, the link to which is in the presentation.

Windows 2016 provides two new options for delivering infrastructure and therefore applications - Nano server and Containers (Windows or Hyper-V). In this session you'll learn how to use PowerShell to automate the lifecycle management of these new options and how to integrate them into your devops driven environment. This session is for anyone needing to understand what nano server and containers can do for them and needing to learn how to manage these infrastructure options. Attendees will learn the differences and similarities between nano server and more 'traditional' options and gain and understanding of how containers can be best utilised on a Windows platform. They will also see live demonstrations of working with these objects and have the code used in the demo made available as a take away

- DevOps aims to break down barriers between development and operations teams through automation, measurement, and culture change. This enables faster delivery of applications and services. - Traditional IT operations has focused too much on control and constraint rather than enabling teams. As a result, developers often work around or avoid IT. - If IT does not adapt by becoming more agile and self-service oriented like cloud computing, it risks becoming irrelevant like backup tape changers - a outdated technology that people work to avoid. IT must partner with teams rather than control them to remain relevant in the future.

This was a session Brian Verkley and I delivered in Las Vegas for EMC World 2016 called 12 Factor App FTW ! In this presentation we talked to each of the 12 factors and how it can relate to the operations side of the house.

Oliver Busse / We4IT Paul Withers / Intec Systems Relational, NoSQL, NewSQL, Graph: there are a lot of database options out there. The current push from large technology providers, including Microsoft and IBM, is graph. Learn what graph databases are and why they may be a good fit for many Domino applications. Find out about the main open source framework, Apache Tinkerpop, and options based upon it - both open source and proprietary, small and enterprise, on premises and cloud. Then see how you can leverage them today to add value to your existing Domino data, with OpenNTF Domino API's GraphNSF functionality.

Jenkins Docker integration. How to leverage Jenkins and Docker in your Continuous Delivery pipelines.

Microservices are small, autonomous services that work together to form an application. The document discusses the benefits of microservices as well as the "Seven Deadly Sins" that can plague microservices architectures: lust, gluttony, greed, sloth, wrath, envy, and pride. It provides examples and recommendations to avoid these anti-patterns, such as implementing circuit breakers, proper service boundaries, independent deployments, versioned APIs, and thorough automated testing.

Managing middleware with Puppet can be challenging due to the complex nature of middleware applications and configurations. Some key challenges include having multiple software development lifecycles to manage for applications and middleware updates, issues with ownership of configuration directories, maintaining idempotency when applying configurations, and managing customizations while avoiding naming conflicts. The document recommends isolating any company-specific customizations into a wrapper module to more easily contribute standard configuration back to the open source community. Active management of middleware is important for security and availability reasons.

Presentation for PHP Unconference 2011 - unfortunately I did not get enough votes so never did the talk :(

We’re all doing Agile nowadays, aren’t we? We’ll all delivering software in an Agile way. But what does that mean? Does it mean sprints and stand-ups? Kanban even? But what about Extreme Programming? If as a development team we’re not using pair programming, test driven development, continuous integration, and other XP practices, then we’re not really doing Agile software development and we may be on a march to frustration, or even failure. I’m going to look at why the current trend of companies and projects adopting Scrum, calling themselves Agile, but not transitioning their development to XP, is a recipe for disaster. I’d like to cover the main practices of XP as well as other good practices that can really help a team deliver quality software, whether they’re doing two-week sprints, Kanban, or even Waterfall. https://www.youtube.com/watch?v=aZgnY9fAHOA

How to choose the right technology for our startup in Indonesia. How to learn pitfall from other startup

This document discusses the development of the Yii PHP framework. It was originally developed from Prado in 2004 and became Yii 1.0 in 2008. The framework uses an MVC architecture and takes inspiration from other frameworks like Rails and Symfony. It focuses on being easy to use, powerful, and flexible. The framework is developed as an open source project under the BSD license to encourage contributions from the community.