Microservices: Lessons Learned

Serverless User Group Poland

Infrastructure microservices such as Service Discovery and Routing need mechanisms to manage distributed state. The most common answer for this is the use of a central, consistent key value store such as Consul, Etcd or Zookeeper. These systems use consensus-based algorithms, such as Raft or Paxos, to provide consistency and failure tolerance. I believe this is a dangerous direction for our industry, and instead we should be focusing on ease of use and reliabiligy. As such, Weave wants its infrastructure microservices to be decentralized, yet easy to install and run; our approach is inspired by the Internet, which is distributed and operates with no consensus. In this talk, I'll explain how we designed our Service Discovery and Address Management using Convergent Replicated Data Types (CRDTs) and Gossip, review the pros and cons of this concept, and how it compares to alternatives.

Kubernetes Sealed secrets

Sebastien Goasguen

OpenShift on IBM Cloud BMS

Shoichiro Sakaigawa

This document summarizes an OpenShift meetup discussing using OpenShift on IBM Cloud Bare Metal Server. It provides an overview of the speaker's background and experience with OpenShift, Kubernetes, and IBM Cloud. It then outlines the setup of OpenShift on IBM Cloud Bare Metal Server, including using NFS storage, installing OpenShift nodes via Ansible playbooks, and configuring the infrastructure for the OpenShift master, etcd, router, Docker registry, and nodes.

SignalR for ASP.NET Developers

Reative UI

Microsoft signal r

Node Session - 1

Functional Programming in Serverless World (Serveless UG Poland)

Continuous delivery in AWS

Anton Babenko

SignalR Overview

Michael Sukachev

MONITORING THE UNKNOWN, 1000*100 SERIES A DAY - DEVOXX MOROCCO 2017

Quentin Adam

Andrea Tosatto - Kubernetes Beyond - Codemotion Milan 2017

Codemotion

Fullstack workshop

Assaf Gannon

TechTalk - Building Serverless Applications with IBM Bluemix

Janakiram MSV

Kubernetes Native Serverless solution: Kubeless

Sebastien Goasguen

Scalatra scala meetup

Tomasz Lelek

Problems you’ll face in the Microservices World: Configuration, Authenticatio...

Quentin Adam

Okay, Microservices are cool. But, as all the new trendy buzzword, it’s not a silver bullet, and there are several problems to manage. One is the authentication, distributed authentication is hard, and there is many ways to achieve it. Configuration is the second issue to be managed when dealing with distributed micro application strategy. This talk is a concrete return of experience to build a strategy on microservice and problems we will have to deal on this occasion.

London Hug 20/6 - Clustering RabbitMQ using Consul

London HashiCorp User Group

Pre-rendering single page app

Michał Koźmiński

This document discusses pre-rendering apps for faster response times, SEO benefits, and support for slower devices. It describes two approaches: using Node.js with HTML parsing and JSDOM libraries, and Rendr, an open-source library from Airbnb that allows Backbone.js apps to run server-side using Express. Rendr replaces Backbone classes and standardizes rendering processes. The document provides instructions for migrating views and controllers to Rendr and setting up an Express app with a rendering configuration. Examples and additional resources are listed.

node.js 실무 - node js in practice by Jesang Yoon

Jesang Yoon

Sharing 4 years of experience about node.js - A google chrome V8 engine javascript based web server technology. This slide covers about wide range of knowledge about node.js learned from 4 years of production, experiment, test & failures 4년 동안 node.js 서버 프로그래밍을 경험한 내용을 간략하게 정리해 보았습니다. node.js 를 접하시는 분들에게 도움이 되었으면 합니다.

What's hot (20)

We don't need consensus: All agreed?

Kubernetes Sealed secrets

OpenShift on IBM Cloud BMS

SignalR for ASP.NET Developers

Reative UI

Microsoft signal r

Node Session - 1

Functional Programming in Serverless World (Serveless UG Poland)

Continuous delivery in AWS

SignalR Overview

MONITORING THE UNKNOWN, 1000*100 SERIES A DAY - DEVOXX MOROCCO 2017

Andrea Tosatto - Kubernetes Beyond - Codemotion Milan 2017

Fullstack workshop

TechTalk - Building Serverless Applications with IBM Bluemix

Kubernetes Native Serverless solution: Kubeless

Scalatra scala meetup

Problems you’ll face in the Microservices World: Configuration, Authenticatio...

London Hug 20/6 - Clustering RabbitMQ using Consul

Pre-rendering single page app

node.js 실무 - node js in practice by Jesang Yoon

Viewers also liked

The Centre Cannot Hold: Making IT Architecture Relevant In A Post IT World

The document discusses how IT architecture is failing to adequately support business needs and priorities. It notes that businesses are increasingly bypassing internal IT functions and turning to external cloud providers instead. This is due to perceptions that internal IT is too slow, rigid, and unresponsive. The ideal vision of IT architecture aligning business and IT strategy is not being realized. In practice, the IT function reacts too slowly and only partially to business pressures. As a result, IT architecture is becoming less relevant in a "post-IT world." The document raises questions about whether the complexity of IT architecture across multiple disciplines is itself contributing to issues between business and IT.

Investing Intelligently In The IT Function

Orchestration and provisioning architecture for effective service management

Orchestration and provisioning are important for effective service management throughout the entire service lifecycle. A generalized architectural approach can yield benefits like reduced costs, faster response times, and greater flexibility. Orchestration involves automating the arrangement and coordination of systems and services, while provisioning creates, maintains, and deactivates resource objects. Together, orchestration and provisioning are key to delivering cloud and other complex services at scale.

Complexity and Solution Architecture

After unnecessary complexity has been reduced from the problem being solved, the scope of the solution to the problem is governed by the complexity of the problem. Complexity is needed to handle and process complexity. Systems acquire or accrete unnecessary complexity over time as originally unforeseen exceptions or changes are incorporated. It may be possible to reduce complexity by collapsing/compressing/combining/consolidating elements and by removing non-value-adding, duplicate, redundant activities. When unnecessary or accreted complexity in the problem being solved has been removed, you are left with necessary complexity that must be incorporated into the solution. Simple problems do not have complex solutions. Complex problems do not have simple solutions. The complexity factor of the proposed solution must match the complexity factor of the problem being resolved. Many system implementation and operational failures arise because of failure to understand and address the core complexity of the problem.

The First 100 Days for a New CIO - Using the Innovation Value Institute IT Ca...

Conway's Law, Cognitive Diversity, Organisation Transformation And Solution D...

These topics may appear to be separate but are closely related to the need for an effective solution design process, approach and function. Nearly 50 years ago, Dr Melvin Conway wrote a short and insightful article titled How Do Committees Invent? where he made a number of observations on the system and solution design process including “… organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.” which has become known as Conway’s Law. He identified organisation problems that lead to poor solution design. Conway’s Law is a warning rather than a prediction. It provides an insight into the solution design problems that can occur if the solution design structures, processes and function are not optimised. What he describes does not have to happen but all too frequently does. Cognitive Diversity has become a fashionable concept that is talked about more than implemented. It has been written about extensively by Dr Scott Page. The core concept is that “… a random group of intelligent problem solvers will outperform a group of the best problem solvers”. The value of cognitive diversity to organisations is greatest in the thinking areas such as the solution design function. Managing diverse teams can be difficult and achieving cognitive diversity can be painful and challenging. Cognitive diversity of less value in pure operational and transactions areas where there is a reduced need for problem-solving. Cognitive diversity protects the organisation against factors such as Cognitive Bias, Strategic Misrepresentation, Planning Fallacy, Optimism Bias, Focalism and Groupthink and their consequences. Cognitive diversity protects against the effects of Conway’s Law. Many organisations are attempting to transform themselves in response to external changes and drivers. Organisation transformation is frequently concerned with a migration from product-orientation to services-orientation characterised by responsiveness, customer centricity, self-service and flexibility. Information technology underpins successful and effective organisation transformation. This is especially true of initiatives such as digital transformation. Digital transformation involves designing and implementing solutions across a wide range of application and system areas. Being good at solution design means that solutions are defined, designed and delivered in a reliable, stable and innovative way to ensure that cost, time, required functionality and quality are constantly optimised to meet the needs of the business. Good solution design mean: • Being aware of all the options and selecting the most appropriate one subject to all constraints • Avoiding all the conscious and unconscious biases that lead to bad solutions Put simply, a cognitively diverse team designs better solutions.

Process Oriented Architecture

This describes the concept of a Process Oriented Architecture. A Process Oriented Architecture is a way of linking process areas to actual (desired) interactions – customer (external interacting party) service journeys through the organisation. It allows two views of any process to be maintained and operated: 1. External view – that experienced by user 2. Internal view – that worked on by the organisational competency An organisation will interact will multiple external parties. Each external party will have a number of interaction paths or journeys. These journeys are the routes of experience of external parties. These routes of experience need to be mapped (as) seamlessly (as possible) to internal organisational operational process competency groupings. The interaction paths or journeys represent the Straight Through Processing that the customer (external party) wants to experience. The complexity of internal organisational operational process competency groupings needs to be masked from the customer (external party). Process Oriented Architecture is a key enabler of successful digital transformation.

Supplier And Service Provider Governance

Competence in sourcing is a core skill of the IT function. The IT function is becoming largely a manager of suppliers and service providers across a wide range of products, solutions and services. IT mediates between the business and the supplier ecosystem, acting as a lens focussing business needs on appropriate suppliers. When products and services are outsourced, the risks of the suppliers and service providers are inherited by the acquiring organisation. Sourcing should not be a “fire and forget” activity. Effective supplier selection and ongoing assessment, validation and management is an important skill for the IT function. The Service Organisation Controls audit approach can be adapted for use by the IT function to develop an approach to vendor governance.

Don’t Mention The “A” Word – Trends In Continuing Business And IT Misalignment

Despite years of emphasising the need for IT and business alignment, the disconnect between business and IT continues. IT focuses too much of pure technology. However, business expectations cam be unrealistic, based on part on IT not explaining itself to the business. IT technology trends are not relevant the business. The business is concerned with the results of investment in IT and sees technology as means to an end and not as ends in themselves. IT needs to structure itself so alignment pervades the entire IT function. IT must embed business alignment in the way it operates to ensure it remains relevant to the business. IT needs to mediate between the business and suppliers and technologies, acting as a lens focussing business needs on appropriate solutions. The gulf is between business and IT seems to be getting wider. Failure to ensure this alignment may lead to the business bypassing IT and going straight to suppliers and service providers. Disintermediation of IT is central to the business plans of many internet-based service providers. Failure to systematise alignment will expose IT to the danger of becoming irrelevant.

Integrated Project and Solution Delivery And Business Engagement Model

This document outlines an integrated project delivery and business engagement model. It discusses how projects have both IT and business dimensions and require an integrated approach across stages and functions. The model includes components like stages, artifacts, activities and gates. It presents the model's extended dimensions and integrated process with business engagement. The initial focus areas are business engagement and solution definition to establish a solid foundation before implementation. Key aspects include defining artifacts across stages, review gates, and taking an artifact-based approach to provide project status. Addressing business analysis and solution design weaknesses is seen as key to avoiding common causes of project failures.

Code Review Checklist

Nitin Bhide

Maximising The Value and Benefits of Enterprise Architecture

Introduction To Business Architecture – Part 1

This is the first of a proposed four part introduction to Business Architecture. It is intended to focus on activities associated with Business Architecture work and engagements. Business change without a target business architecture and a plan is likely to result in a lack of success and even failure. An effective approach to business architecture and business architecture competency is required to address effectively the pressures on businesses to change. Business architecture connects business strategy to effective implementation and operation: • Translates business strategic aims to implementations • Defines the consequences and impacts of strategy • Isolates focussed business outcomes • Identifies the changes and deliverables that achieve business success Enterprise Architecture without Solution Architecture and Business Architecture will not deliver on its potential. Business Architecture is an essential part of the continuum from theory to practice.

Solution Architecture Concept Workshop

The document summarizes the objectives, process, roles, and activities involved in a Solution Architecture Concept workshop. The workshop is intended to define the scope, components, and architectural overview of a proposed IT solution by bringing together stakeholders to develop a shared understanding of business needs and technical requirements. Key parts of the workshop include preparation activities, a two-day session to discuss business/functional and technology/implementation views, and documentation of findings.

Enterprise Business Analysis Capability - Strategic Asset for Business Alignm...

This document discusses the role and importance of enterprise business analysis as a strategic capability for achieving business and IT alignment and driving innovation. Some key points: - Enterprise business analysis can help translate business strategy into objectives, ensure IT solution delivery is aligned to strategy/objectives, and contribute to solution delivery governance. - It involves analyzing business requirements and processes associated with changes, defining business solutions to deliver requirements/processes, and rebuilding the conversation between business and IT. - Multiple levels of business analysis (enterprise, functional, IT) are needed to effectively prevent fragmentation across the organization and deliver solutions in response to business needs from strategy through delivery. - Without this capability, IT risks delivering solutions that are not

Data Audit Approach To Developing An Enterprise Data Strategy

Digital Transformation And Enterprise Architecture

Digital transformation - extending and exposing business processes outside the organisation - by implementing a digital strategy – a statement about the organisation’s digital positioning, operating model, competitors and customer and collaborator needs and behaviour through the delivery of digital solutions defined in a digital architecture – a future state application, data and technology view to achieve digital operating status - is potentially (very) complex. Digital architecture does not exist in isolation entirely separate from an organisation’s overall enterprise architecture. Digital architecture must exist within the within the wider enterprise architecture context. Enterprise architecture provides the tools and the approaches to manage the complexity of digital transformation. The management function that drives digital transformation needs to involve the enterprise architecture function in the design and implementation of digital strategy and organisation, process and policies and the creation of a digital architecture. Management must appreciate the technology focus and the benefits of an enterprise architecture approach. The early involvement of enterprise architecture increases successes and reduces failures. Management must trust and involve enterprise architecture. The enterprise architecture function must accept and rise to the challenge and deliver. The enterprise architecture function must allow its value to be measured.

The Myth Of Requirements

The myths of requirements are that: • Requirements gathered from business users through requirements gathering meetings and workshops define the scope and functionality of the solution • Requirements gathering workshops at the start of a project are sufficient to understand business needs • Requirements change The reality is that what is gathered during requirements workshops, meetings, interviews, questionnaires and other activities are not solution requirements but business stakeholder requirements. Stakeholder requirements must be translated into solution requirements which is turn must be translated into a solution design. A solution is a Resolver, a Provider or an Enabler. Good solution design requires solution ownership and technical leadership throughout the process. Any solution is always greater than the sum of the gather requirements. Requirements do not equal a solution. Any solution also causes problems in terms of: • Required organisational changes to implement and operate solution • Additional operational overhead • Cost to implement The solution is the minimum set of components that works and that solves the problem at the minimum cost with minimum additional costs.

Business process analysis and design – importance of having a common language...

Review of Data Management Maturity Models

This document reviews several existing data management maturity models to identify characteristics of an effective model. It discusses maturity models in general and how they aim to measure the maturity of processes. The document reviews ISO/IEC 15504, the original maturity model standard, outlining its defined structure and relationship between the reference model and assessment model. It discusses how maturity levels and capability levels are used to characterize process maturity. The document also looks at issues with maturity models and how they can be improved.

Viewers also liked (20)

The Centre Cannot Hold: Making IT Architecture Relevant In A Post IT World

Investing Intelligently In The IT Function

Orchestration and provisioning architecture for effective service management

Complexity and Solution Architecture

The First 100 Days for a New CIO - Using the Innovation Value Institute IT Ca...

Conway's Law, Cognitive Diversity, Organisation Transformation And Solution D...

Process Oriented Architecture

Supplier And Service Provider Governance

Don’t Mention The “A” Word – Trends In Continuing Business And IT Misalignment

Integrated Project and Solution Delivery And Business Engagement Model

Code Review Checklist

Maximising The Value and Benefits of Enterprise Architecture

Introduction To Business Architecture – Part 1

Solution Architecture Concept Workshop

Enterprise Business Analysis Capability - Strategic Asset for Business Alignm...

Data Audit Approach To Developing An Enterprise Data Strategy

Digital Transformation And Enterprise Architecture

The Myth Of Requirements

Business process analysis and design – importance of having a common language...

Review of Data Management Maturity Models

Similar to Microservices: Lessons Learned

Spring boot microservice metrics monitoring

Oracle Korea

This document summarizes a presentation on monitoring microservices with Spring Boot. It discusses evolving architectures from monolithic to microservices and challenges in microservices. It then covers different monitoring techniques like metrics, tracing and logging. It provides an overview of tools like Prometheus, Grafana, Spring Boot Admin, Eureka and Consul for monitoring microservices. Finally, it outlines hands-on labs to set up monitoring of a sample application with different tool combinations.

Spring Boot - Microservice Metrics Monitoring

DonghuKIM2

Product Release Webinar- WSO2 Developer Studio 3.5

WSO2

This document provides an overview of WSO2 Developer Studio 3.5.0, an integrated development environment for developing, deploying, debugging and testing SOA applications. It introduces the presenters Harshana Marin and Jasintha Dasanayake. Key features of Developer Studio include tools for composing services visually, managing service metadata in registries, developing composite applications, and deploying to local, remote or cloud servers. It allows collaborative development and includes sample projects.

Amazon ECS Deep Dive

Amazon Amazon Elastic Container Service (Amazon ECS)

Paul Maddox gave a presentation on deploying containerized microservices applications on Amazon ECS. He demonstrated building a Twitter analyzer application with Go microservices that communicate via RPC and are deployed to a production ECS cluster using AWS CloudFormation templates. Key components included Amazon ECS, ECR, container instances, tasks and containers. Deployments were made repeatable and auditable using infrastructure-as-code.

GIDS 2019: Developing Apps with Containers, Functions and Cloud Services

Patrick Chanezon

The document discusses developer workflows for building cloud applications using containers, functions, and managed cloud services. It presents options for developing applications locally and deploying to the cloud using tools like Docker Desktop, Azure Functions runtime, Azure Dev Spaces, and Telepresence that enable local development and debugging. The document also discusses approaches for packaging and deploying distributed applications using CNAB and Duffle.

Four Scenarios for Using an Integration Service Environment (ISE)

Daniel Toomey

The document discusses four scenarios for using an Azure Integration Service Environment (ISE): 1) private static outbound IP addresses, 2) predictable performance by controlling scaling, 3) support for additional hybrid connections via on-prem connectors, and 4) segregated network security by containing integration solutions within a private network. An ISE provides a way to run Logic Apps within an isolated and securable environment with access to on-premises resources. The document outlines the steps to create an ISE and provides examples of using ISE for outbound IPs, scaling, and hybrid connectivity.

Application Performance Management on AWS - ARC317 - re:Invent 2017

Cloud is the new normal, and organizations are deploying different types workloads on AWS. Understanding the performance efficiency and overall application performance is critical to ensuring that you can scale your workload to meet the demands of your customers. Understanding how well your application performs over time helps you to continuously improve and innovate your software to get the most out of the AWS platform. If you aren't measuring custom application metrics, you are operating your software blindly and cannot pinpoint areas of improvement. Learn how to use Amazon CloudWatch custom metrics, alerts, dashboards and AWS X-Ray to architect an application monitoring service to provide insight to your workload's performance.

Azure Cloud Application Development Workshop - UGIdotNET

Lorenzo Barbieri

Resume_Ashok-updated (1) (1)

chimmili ashok

This document contains a summary of qualifications and experience for an individual with over 3 years of experience in server administration, networking, and AWS management. It details education qualifications including an MCA and BSc, and professional experience providing support and managing AWS environments for several clients in roles such as Systems Engineer and Provisioning Engineer. Responsibilities included provisioning and maintaining systems, security, automation tasks, troubleshooting, and managing configurations.

Get visibility into your Containers/Kubernetes using Azure Monitor

BizTalk360

From Monolith to Microservices

This document provides an overview of microservices architecture and how to implement it using Amazon ECS and Docker containers. It discusses what microservices are, characteristics of the architecture, and how ECS provides a fully managed platform for deploying and scheduling containers. It also covers task placement strategies, running services on ECS, and reference architectures like continuous deployment, secrets management, and service discovery that align with the twelve-factor app methodology. Finally, it introduces Blox, an open source project that aims to simplify deploying and managing microservices on ECS.

Enabling Microservices Frameworks to Solve Business Problems

Ken Owens

AWS Serverless concepts and solutions

ElenaIvannikova3

The document discusses AWS serverless concepts and solutions. It covers serverless computing advantages like dynamic resource allocation and scaling with usage. It then discusses serverless architectures using AWS services like Lambda, S3, SNS, SQS, and Kinesis. It also covers AWS Lambda configuration and deployment using the Serverless Application Model and CloudFormation. Finally, it discusses CI/CD pipelines and infrastructure as code for serverless applications.

Hybrid Infrastructure Integration

Hybrid Infrastructure Integration is an approach to connect on-premises IT resources with AWS and bridge processes, services, and technologies used in common enterprise customer environments. This session addresses connectivity patterns, security controls, account governance, and operations monitoring approaches successfully implemented in enterprise engagements. Infrastructure architects and IT professionals can get an overview of various integration types, approaches, methodologies, and common service patterns, helping them to better understand and overcome typical challenges in hybrid enterprise environments.

Hybrid Infrastructure Integration

This document discusses integrating on-premises infrastructure with AWS. It examines integrated infrastructure using VPN and Direct Connect, integrated services like Active Directory and monitoring tools, and an integrated platform for deployment and management. Example integrated solutions discussed include storage expansion, backup/archiving, and continuous integration/deployment. The takeaways emphasize the importance of connectivity and authentication/authorization for hybrid integration.

re:Invent 2019 CON328R Improving observability of your containers

Shubha Bheema Rao

Improving observability of containerized applications means providing full stack visibility across application, container, and compute layers, compatibility with existing tools, and the ability to run applications anywhere without changing tools. CloudWatch Container Insights provides a fully managed observability service that works across Amazon ECS, Amazon EKS, and AWS Fargate, collecting metrics and logs and providing dashboards. FireLens enables sending container logs to various destinations like AWS services, partners, and self-managed solutions. App Mesh provides service mesh capabilities and enhances visibility at the application level.

Weave Cortex: Multi-tenant, horizontally scalable Prometheus as a Service

This document describes Cortex, a multi-tenant horizontally scalable Prometheus as a service. It retrieves metrics from applications using Prometheus scrapers, distributes the metrics across ingesters using consistent hashing, stores metrics in DynamoDB with indexes and chunks in S3, and provides a Prometheus compatible query API. The goal is to build a proof of concept quickly to monitor tens of thousands of users sending tens of millions of samples per second in a cost effective and scalable way, reusing Prometheus where possible. There is still work to be done on features like recording rules, alerting, reliability, performance, and code cleanup before it is production ready.

Pune microsoft azure developers 2nd meetup

ratneshsinghparihar

The document outlines an agenda for a Microsoft Azure Developers Meetup. It includes demos of building real-time survey, bus tracking, and home automation applications using Azure Mobile Services. It discusses features of Mobile Services like shared backends, authentication, and push notifications. The demos illustrate how to integrate apps with backend services for data storage and real-time updates across devices using technologies like Pusher API. Server-side scripts and REST APIs for Mobile Services are also covered.

Hybrid Infrastructure Integration

Similar to Microservices: Lessons Learned (20)

Spring boot microservice metrics monitoring

Spring Boot - Microservice Metrics Monitoring

Product Release Webinar- WSO2 Developer Studio 3.5

Amazon ECS Deep Dive

Amazon Amazon Elastic Container Service (Amazon ECS)

GIDS 2019: Developing Apps with Containers, Functions and Cloud Services

Four Scenarios for Using an Integration Service Environment (ISE)

Application Performance Management on AWS - ARC317 - re:Invent 2017

Azure Cloud Application Development Workshop - UGIdotNET

Resume_Ashok-updated (1) (1)

Get visibility into your Containers/Kubernetes using Azure Monitor

From Monolith to Microservices

Enabling Microservices Frameworks to Solve Business Problems

AWS Serverless concepts and solutions

Hybrid Infrastructure Integration

re:Invent 2019 CON328R Improving observability of your containers

Weave Cortex: Multi-tenant, horizontally scalable Prometheus as a Service

Pune microsoft azure developers 2nd meetup

Hybrid Infrastructure Integration

More from Weaveworks

Weave AI Controllers (Weave GitOps Office Hours)

LLMs are one of the rising workloads on Kubernetes and so are the complexities of deploying, managing and fine-tuning them. With this latest extension we can offer a strong blueprint for enterprises on how to keep LLMs OCI contained with the use of Kubernetes, Flux and Weave AI Controllers. The Highlights: * Simplified deployment, management, and fine-tuning of LLMs on any Kubernetes infrastructure. * Strong security and governance ensured through GitOps workflows and a robust signing and verification process. The Whys: * Security, Governance & Compliance: Ensures vulnerability-free and compliant deployments. * Seamless Integration: Works with existing systems, including Red Hat OpenShift. * GitOps for Productivity & Collaboration: Leverages the power of Flux and Kubernetes for automated, streamlined workflows. The Weave AI Controllers are an out of the box extension for Flux and are shipped and supported with Weave GitOps Assured (https://www.weave.works/product/gitops) and Enterprise (https://www.weave.works/product/gitops-enterprise/). Read our latest blog for more information (https://www.weave.works/blog/weave-ai-controllers) and visit GitHub to get started - https://github.com/weave-ai/weave-ai

Flamingo: Expand ArgoCD with Flux (Office Hours)

Flamingo is an open source tool that allows for integrated use of both Flux and ArgoCD, the two leading GitOps solutions available today. * See how to integrate the two most used CNCF projects together to create flexible and extensible GitOps solutions. * Learn how to use Flux’s powerful and secure controllers with ArgoCD’s web-based GUI. * Understand how Flamingo provides a path towards Platform Engineering for ArgoCD users. * Explore extending ArgoCD to manage Infrastructure as Code through Flux’s Terraform Controller. For more information visit: https://github.com/flux-subsystem-argo/flamingo

Webinar: Capabilities, Confidence and Community – What Flux GA Means for You

Flux, the original GitOps project, began its development in a small London office back in 2017 with the goal to bring continuous delivery (CD) to developers, platform and cluster operators working with Kubernetes. From donating the project to the CNCF, its continued growth within the cloud native community, to its achievement of passing rigorous battle tests for security, longevity and governance, it’s little wonder that Flux v2 has reached yet another celebratory milestone – General Availability (GA). Flux is the GitOps platform of choice for many enterprise companies such as SAP, Volvo Cars, and Axel Springer; and is embedded within AKS, Azure Arc and EKS Anywhere. It provides extensive automation to CI/CD, security and audit trails, and reliability through canary deployments and rollback capabilities. Join this webinar by Flux maintainers and creators and discover: * Latest release features and roadmap for the future. * Interesting use cases for Flux (e.g security). * Flux capabilities you may not be aware of (e.g. extensions). * Joining the vibrant Flux community. * How to leverage Flux in a supported enterprise environment today.

Six Signs You Need Platform Engineering

Although not an entirely new concept, Platform Engineering and Internal Developer Platforms (IDPs) are all the rage due to their potential to increase development velocity and deployment frequency while boosting reliability and security. Join Joe Dahlquist, VP of PMM and Mohamed Ahmed, VP of Developer Platforms at Weaveworks to learn the 6 tell-tale signs your company should implement a platform engineering approach. The webinar draws on hundreds of conversations with SRE’s, developers, and platform engineering teams to help you better understand what works, what doesn’t and what might be missing from your strategy. Attendees can apply these learnings to their first (or next) developer platform regardless of your build vs. buy journey. You will learn: * The difference between Internal Developer Platforms and Platform Engineering * Why platform engineering now? * How Dev and Ops benefit from an IDP * 6 tell-tale signs to start platform engineering * Drafting your platform engineering strategy - where to begin and what to avoid

SRE and GitOps for Building Robust Kubernetes Platforms.pdf

In today's technology-driven landscape, ensuring the reliability and stability of systems is critical for organizations to deliver exceptional user experiences. Site Reliability Engineering (SRE) has emerged as a proven methodology to achieve operational excellence and elevate performance. By combining SRE and GitOps, organizations can leverage the benefits of both methodologies. GitOps provides a reliable and auditable approach to managing infrastructure and application changes, ensuring that all deployments are version-controlled and consistent across environments. This aligns with the SRE principle of implementing standardized and automated processes for maintaining system reliability. Join our live webinar as we introduce the fundamentals and significance of SRE and GitOps, and provide actionable strategies for implementation. We’ll also explore the features of Weave GitOps that integrate SRE and GitOps practices to streamline workflows to support system reliability and stability. You will learn: An overview and correlation of key SRE and GitOps best practices The 5 keys DORA metrics for measuring performance of software delivery. How to leverage continuous delivery and progressive delivery to enhance application stability. How Weave GitOps can reliably simplify the management of infrastructure and applications, with real-world customer examples illustrating their impact.

Webinar: End to End Security & Operations with Chainguard and Weave GitOps

One of the key values of GitOps relies on its fully declarative single source of truth in Git for the desired state of your entire system – configuration that continuously reconciles with the runtime of the system. Validating committer identity in your Git repository is a critical component towards a secure GitOps solution. Although basic capabilities are provided by Git service providers, more granular controls for governance and compliance are a requirement to satisfy most enterprise grade implementations. How do you keep that end to end process secure, from Git to Runtime? Join Weaveworks and Chainguard for a live webinar where we will look at how Chainguard Enforce for Git together with Weave GitOps Enterprise Policy Engine allows you to secure your end to end GitOps workflows, from Git to Runtime. You will learn how to: - Use Chainguard Enforce for Git to ensure only authorized GitOps tooling can modify your desired state. - Provide a secure identity to Weave GitOps Enterprise for all Git operations. - Use Weave GitOps Policy Engine to guarantee compliance on admission.

Flux Beyond Git Harnessing the Power of OCI

Watch the recap: https://youtu.be/gKR95Kmc5ac In this KubeCon Europe 2023 session, Stefan and Hidde will talk about the latest developments of Flux around the Open Container Initiative (OCI). The focus will be on how OCI can serve as the single source of truth for both application code (container images) and configuration (OCI artifacts). We will start by explaining how Flux can be used as a package manager for distributing Kubernetes configs and Terraform modules as OCI artifacts. Afterwards, we will demonstrate how to build a secure delivery pipeline that leverages Flux integrations with GitHub Actions and keyless signatures from Sigstore Cosign. Lastly, we will touch upon the upcoming plans for 2023 and the significance of OCI in the future of continuous delivery with Flux.

Automated Provisioning, Management & Cost Control for Kubernetes Clusters

In today’s economic climate, IT departments are feeling the pressure to reduce costs which can have a significant effect on development teams, and more specifically, Kubernetes strategies. For many organizations, there is a good chance that many Kubernetes resources are overprovisioned, and it’s often difficult to visualize which processes are responsible for this unnecessary spend. Weaveworks has joined forces with KubeCost to show you how to “do more with less” by easily integrating a Kubernetes FinOps solution into your existing workflows and seamlessly automating the provisioning and management of FinOps enabled Kubernetes clusters from a single UI / dashboard. Join this webinar to discover best practices for monitoring and reducing Kubernetes spend, while balancing cost, performance, and reliability. What you’ll learn: - Best practices for implementing a FinOps strategy in your organization. - Cluster management and templating capabilities using Weave GitOps for automating FinOps. - How to use predefined, automated policies for reliable cost control across your Kubernetes environment.

How to Avoid Kubernetes Multi-tenancy Catastrophes

This document summarizes a webinar about implementing multi-tenancy in Kubernetes without catastrophes using GitOps. It recommends 5 easy steps: 1) implement a zero trust posture, 2) apply least privilege practices, 3) use policies to enforce governance, 4) leverage GitOps audit capabilities, and 5) reduce the blast radius. The webinar discusses how Weaveworks' Workspaces product establishes boundaries and defines access controls to securely support multiple teams deploying applications.

Building internal developer platform with EKS and GitOps

An internal developer platform (IDP) is a set of standardized tools and technologies that enables development teams to self-service, offering convenient access to resources they need to create and deploy compliant code. The ultimate goal is to facilitate automation, autonomy and productivity across large teams. However, creating an IDP is highly complex, especially when bridging hybrid scenarios. In fact, build timelines can take anywhere between one to two years! In this Techstrong Learning Experience, we will discuss how platform engineers can more efficiently build an IDP with Amazon EKS and Weave GitOps and accelerate cloud-native adoption while speeding up migration of existing applications to the cloud. Our experts will also introduce EKS Blueprints, a collection of infrastructure-as-code (IaC) modules like Terraform and AWS Cloud Development Kit (AWS CDK) that will help you configure and deploy consistent EKS clusters across on-premises and cloud. Key Takeaways: - Why you should build a self-service IDP - How to leverage EKS, GitOps and EKS Blueprints to build your IDP - A review of use cases and benefits of an IDP

GitOps Testing in Kubernetes with Flux and Testkube.pdf

GitOps is amazing... until you can't apply it! This has been the case mostly for testing where it continues to be more of a push than a pull in organizations' DevOps pipelines. Join us in this talk to learn the benefits of improving your existing testing pipeline with Testkube, an open source project that brings tests inside your Kubernetes cluster, and FluxCD adding the GitOps sprinkles to testing! Speaker: Abdallah Abedraba, Product Leader at Testkube Abdallah works at Testkube, a Kubernetes native testing framework. In his prior experiences, he has tried everything from software engineering to product management, and now working as a Developer Advocate, on open source (a dream of his!) evangelizing all things Testing and Kubernetes. In his free time, he enjoys attending developer conferences and meetups, as well as spending time at the movies and actively listening to music.

Intro to GitOps with Weave GitOps, Flagger and Linkerd

Implementing Flux for Scale with Soft Multi-tenancy

Soft multi-tenancy can be hard to achieve and secure. Multiple tenants sharing the same cluster means there are global objects, like Custom Resource Definitions (CRDs), namespaces, and so on, that you don’t want tenants controlling. Platform admins, cluster admins, and tenants, should be separated, with dedicated namespaces, role bindings, node groups, taints and tolerations, etc. With Flux, tenant isolation is enforced by default, so you don’t have to worry about accidental tenant cross-over / cross-contamination. In this session, Priyanka “Pinky” Ravi, Developer Experience Engineer at Weaveworks, will walk you through how to set up multi-tenancy on an existing Kubernetes cluster and manage several tenants within the cluster. Take advantage of the benefits that come with infrastructure as code.

Accelerating Hybrid Multistage Delivery with Weave GitOps on EKS

Join Leo Murillo, Principal Solutions Architect at Weaveworks and Rama Ponnuswami, Sr. Container Specialist at AWS, as they walk through accelerating Multi-stage delivery on GitOps. If you already have EKS-A, you are ready to automate the release of multistage delivery. Thus, allowing you to deploy more often and reliably with less overhead. In this Webinar, we cover: - Best practices for CI/CD, GitOps and Application Pipeline Management. - Simple cluster management across Kubernetes hybrid infrastructure. - Multistage deployments using Weave GitOps for EKS and EKS-A using a single UI dashboard.

The Story of Flux Reaching Graduation in the CNCF

This document summarizes the evolution of Flux from version 1 to version 2. It describes how Flux started as a tool to ensure cluster state matches Git config and has become a multi-tenant continuous delivery platform. It outlines key milestones such as graduating from CNCF sandbox to incubation and hitting over 4,000 stars. It also provides an overview of Flux version 2's architecture and growing set of capabilities around areas like GitOps, Helm, Kustomize, security, and support for artifacts from container registries.

Shift Deployment Security Left with Weave GitOps & Upbound’s Universal Crossp...

In this session, we’ve partnered with Upbound to showcase how to effectively manage application delivery while maintaining a high level of security using Weave GitOps and Upbound. Managing a stateful application deployment with a relational database, Weave GitOps can recognize if there is a policy violation and correct it before deploying the application. Join us as we demonstrate the scenarios where: All changes to application configuration are managed through Git workflows Upbound’s Universal Crossplane allows you to build, deploy, and manage your cloud platforms GitOps provides an extra layer of security by removing the need for direct access to Kubernetes clusters Policy-as-Code guarantees security, resilience and coding standards compliance Watch the recording: xx

Securing Your App Deployments with Tunnels, OIDC, RBAC, and Progressive Deliv...

In a joint webinar with Traefik Labs, we show how Traefik Hub, a SaaS-based cloud native networking platform, helps you publish your containers securely in seconds with tunnels, OIDC authentication and automated TLS certificate management. And, how you can combine that with Weave GitOps to achieve continuous application delivery using progressive delivery strategies for risk-free and reliable deployments. Security is key, so we showcase multi-tenancy for full RBAC across the different deployment stages, and trusted delivery best practices for continuous security and compliance baked in. Learn how: - To utilize canary deployments for reliable and risk-free application deployments. - GitOps lets you automate and secure the publishing of containers at the edge consistently. - Easy it is to deploy, update and manage your application workloads on Kubernetes. - To publish containers securely using tunnels, OIDC authentication and TLS certificate management.

Flux’s Security & Scalability with OCI & Helm Slides.pdf

Flux Security & Scalability using VS Code GitOps Extension

Recently Flux has released two new features (OCI and Cosign) for scalable and secure GitOps. Juozas Gaigalas, a Developer Experience Engineer at Weaveworks, will demonstrate how developers and platform engineers can quickly create scalable and Cosign-verified GitOps configurations using VS Code GitOps Tools extension. New and experienced Flux users can learn about Flux’s OCI and Cosign support through this demo.

Deploying Stateful Applications Securely & Confidently with Ondat & Weave GitOps