The Future of Adhearson

•

0 likes•375 views

The document discusses plans for the next major version (2.0) of the Adhearsion telephony framework. It describes extracting Asterisk-specific code into a new library called Punchblock that will provide a common call control API across platforms. This will allow Adhearsion applications to run on Asterisk, FreeSWITCH or other backends. It also outlines changes to the API and goals for AdhearsionConf 2012, including porting apps to 3 platforms and gaining new contributors. Questions are posed about scaling, multi-platform use cases, needed features, and desired new capabilities.

Technology

The future of Adhearsion

Ben Klang, Project Leader
Ben Langfeld, Core Team

Goals for AdhearsionConf 2012
• Application portability across 3 distinct platforms

Goals for AdhearsionConf 2012
• Application portability across 3 distinct platforms

• 100 attendees

Goals for AdhearsionConf 2012
• Application portability across 3 distinct platforms

• 100 attendees

• 50 plugins on ahnhub.com

Goals for AdhearsionConf 2012
• Application portability across 3 distinct platforms

• 100 attendees

• 50 plugins on ahnhub.com

• 10 new core contributors

Adhearsion 2.0
• The next major evolution of Adhearsion

Adhearsion 2.0
• The next major evolution of Adhearsion

• Many improvements including:

Adhearsion 2.0
• The next major evolution of Adhearsion

• Many improvements including:

• Core architecture overhaul

Adhearsion 2.0
• The next major evolution of Adhearsion

• Many improvements including:

• Core architecture overhaul

• A reduction in internal complexity and line-count

Adhearsion 2.0 continued
• Overhaul of the component system

Adhearsion 2.0 continued
• Overhaul of the component system

• Renaming to ‘plugins’

Adhearsion 2.0 continued
• Overhaul of the component system

• Renaming to ‘plugins’

• Railties-like modular hooks into the core system

Adhearsion 2.0 continued
• Overhaul of the component system

• Renaming to ‘plugins’

• Railties-like modular hooks into the core system

• Advanced initialisation routines

Punchblock
• Low level telephony platform abstraction library

Punchblock
• Low level telephony platform abstraction library

• Asterisk (+ SCF in the future)

Punchblock
• Low level telephony platform abstraction library

• Asterisk (+ SCF in the future)

• Rayo (Voxeo Prism today; tomorrow the world)

Punchblock
• Low level telephony platform abstraction library

• Asterisk (+ SCF in the future)

• Rayo (Voxeo Prism today; tomorrow the world)

• FreeSWITCH?

Adhearsion on Punchblock
• Extraction of all Asterisk-speciﬁc code from Adhearsion into
Punchblock

Adhearsion on Punchblock
• Extraction of all Asterisk-speciﬁc code from Adhearsion into
Punchblock

• A consistent call control API for Adhearsion applications

API Changes
• The dialplan DSL will have some modiﬁcations, but will
be mostly backward compatible

API Changes
• The dialplan DSL will have some modiﬁcations, but will
be mostly backward compatible

• #join -> #conference

API Changes
• The dialplan DSL will have some modiﬁcations, but will
be mostly backward compatible

• #join -> #conference

• Parameters may change slightly

Ruby version support
• CRuby 1.9+ - yes

• JRuby 1.6+ - yes

Ruby version support
• CRuby 1.9+ - yes

• JRuby 1.6+ - yes

• Rubinius 2.0 - yes

Ruby version support
• CRuby 1.9+ - yes

• JRuby 1.6+ - yes

• Rubinius 2.0 - yes

• Ruby 1.8 - no

Adhearsion really far out

• Adhearsion 1.x - Asterisk applications

Adhearsion really far out

• Adhearsion 1.x - Asterisk applications

• Adhearsion 2.x - Voice applications

Adhearsion really far out

• Adhearsion 1.x - Asterisk applications

• Adhearsion 2.x - Voice applications

• Adhearsion 3.x - Real-time communications applications

Questions for you
• How important is scaling Adhearsion across multiple
back-ends (1 Adhearsion to every 5 Asterisk)?

Questions for you
• How important is scaling Adhearsion across multiple
back-ends (1 Adhearsion to every 5 Asterisk)?

• Would you be interested in using a single Adhearsion
application on multiple platforms simultaneously?

The document introduces Chef Delivery, which provides a shared workflow from code to customer. It features a unified pipeline with fixed stages and phases for approving, verifying, building, deploying, and testing changes. The workflow provides visibility, reliability, and safety for moving quickly from ideas to shipped software. It also allows visualization of changes and uses build cookbooks and APIs to automate deployments across a project's infrastructure.

Gasimov Orkhan "Service Discovery and Coordination by Netflix Eureka and Spri...

LogeekNightUkraine

This document provides an overview of service discovery and coordination using Netflix Eureka and Spring Cloud. It discusses how Eureka allows for dynamic service registration and lookup, load balancing, and high availability through a peer-aware cluster. Key features highlighted include Eureka clients automatically registering and sending heartbeats to the server, and the DiscoveryClient interface for looking up service instances.

Backing Data Silo Atack: Alfresco sharding, SOLR for non-flat objects

ITD Systems

The document discusses a scheme for sharding Alfresco repositories to address scalability and storage limitations. Key points of the scheme include: - Repositories are sharded across multiple independent servers, each storing a part of the content. - A level 7 switch balances requests across repositories and provides a single API entry point. - An external SOLR cloud indexes all repositories in a single index to allow federated queries. - The scheme is benchmarked to scale to 15,000 concurrent users on commodity hardware. Additional considerations for production include auto-discovery, configuration management, and safety checks.

Infrastructure as Code with Chef

Sarah Hynes Cheney

The document discusses DevOps and infrastructure as code. It describes how using infrastructure as code allows organizations to automate infrastructure provisioning and management. This enables continuous delivery of applications and infrastructure through a unified software development pipeline. Chef is presented as a tool that can help implement such a DevOps approach through its support for infrastructure as code, compliance automation, and a shared development workflow.

Perforce webinar clear-case_jb[2]

Perforce

They didn’t think migrating off their legacy version control system would be difficult. They thought it would be impossible. For Cadence Design Systems, the multinational electronic design automation (EDA) software and engineering services company, moving off ClearCase was an important but daunting goal. They knew a modern, flexible system would foster innovation and help them keep up with rapidly evolving customer demands. But, they had a highly customized environment and wanted to preserve the data they’d accumulated over the years. It wasn’t easy. But, with Perforce, it was possible. How? Find out. Cindi Hunter, Director of Configuration Management and Tom Tyler, Senior Consultant at Perforce Software, share their highly successful migration process, which includes: • Defining the scope of your migration given your unique environment. • Determining a migration strategy to preserve sophisticated branching strategies, custom tools, and important data. • Ensuring you get the migration support you need from your new vendor.

Testing Alfresco extensions

ITD Systems

The document discusses a Python framework for testing Alfresco extensions. It allows testing REST APIs, UI interactions, and complex scenarios. The framework uses Python and Proboscis for testing, Selenium for browser emulation, and provides wrappers for common REST calls and predefined classes for interacting with Alfresco Share forms. Examples are given of REST API tests, setting up browser-specific UI tests, and testing a workflow dashlet and form.

Traditionally at Bandai Namco Studios, there has been no unified version control system in place and teams could choose to use any VCS system for their game titles—Subversion, Git, AlienBrain, or none at all. I’ll talk about why Bandai Namco Studios chose to standardize on Perforce Helix, show how we develop LiveOps-type mobile applications using the Unity game engine, and the advantages we gain from centrally managing code and assets in Helix.

Code Hosting: The Key to Autonomous, Self-Service Development

Rachel Maxwell

The document discusses Helix4Git, a product from Perforce Software that allows their versioning engine to directly manage Git data. It provides automated mirroring of Git repositories to remote locations for improved scalability and performance in continuous integration and delivery pipelines. A new version, Helix TeamHub, adds additional features to solve challenges for developers working with multiple Git repositories at scale, such as improved collaboration, administration, and integration capabilities.

Heroku

Eberhard Wolff

Heroku is a platform as a service that originally started as a Ruby PaaS but now supports Node.js, Clojure, Grails, Scala, and Python. It uses the Git version control system for deployment and a dyno process model for scaling applications. While flexible in allowing custom buildpacks and configuration via environment variables, there are also restrictions like maximum source code size and memory limits for dyno processes.

Spring Boot

Eberhard Wolff

Spring Boot makes it easier to create Java web applications. It provides sensible defaults and infrastructure so developers don't need to spend time wiring applications together. Spring Boot applications are also easier to develop, test, and deploy. The document demonstrates how to create a basic web application with Spring Boot, add Spring Data JPA for database access, and use features for development and operations.

External Master Data in Alfresco: Integrating and Keeping Metadata Consistent...

ITD Systems

Micro Services - Small is Beautiful

Eberhard Wolff

The document discusses microservices and their advantages over monolithic architectures. Microservices break applications into small, independent components that can be developed, deployed and scaled independently. This allows for faster development and easier continuous delivery. The document recommends using Spring Boot to implement microservices and Docker to deploy and manage the microservices as independent components. It provides an example of implementing an ELK stack as Dockerized microservices.

High Availability and Scalability: Too Expensive! Architectures for Future E...

Eberhard Wolff

The document discusses high availability and scalability approaches for enterprise systems. Traditionally, enterprises rely on highly reliable hardware, small clusters, and standby data centers. However, this approach is expensive and systems can still fail. The document proposes using virtualization, stateless servers, and NoSQL databases to achieve high availability and scalability at lower cost. Servers are provisioned as "Phoenix servers" that can be easily recreated if failed, without relying on expensive reliable hardware. Data is distributed across servers for redundancy and fine-grained scaling. This software-based approach provides better performance and availability compared to traditional hardware-centric methods.

Perfecting Your Development Tools: Updates to the Helix Plugin for Jenkins

Perforce

Considering a mono repo that can manage all your source code, binary and other assets? Join us for an exclusive recap of our Birds of Feather presentation from this year’s Jenkins World conference! Senior Integration Engineer Paul Allen will reveal much anticipated updates around the Helix Plugin for Jenkins (or ‘P4 Plugin’). This presentation covers... - The latest DSL Pipeline support in the ‘P4 Plugin' - Tips & tricks on mapping your Branches and Streams into a Jenkins Workspace - Best practices on publishing assets into Helix - A sneak preview of the latest ‘P4 Plugin’ for Jenkins

ELK Stack

Eberhard Wolff

AWS Summit Tel Aviv - Enterprise Track - Enterprise Apps & Hybrid

Amazon Web Services

The document summarizes a presentation given at the AWS Summit 2013 in Tel Aviv on using AWS for enterprise applications and hybrid environments. The presentation covered: 1. Using AWS to extend on-premises data center capacity and provide flexible infrastructure for new projects. 2. Connecting the on-premises environment to AWS through a virtual private cloud (VPC) and direct connect. 3. Leveraging AWS for development, testing, and continuous deployment activities. 4. Examples of running enterprise workloads like Oracle databases, SAP applications, and Microsoft software on AWS.

Alfresco Day Platform Update

ohej

Chef for DevOps - an Introduction

Sanjeev Sharma

Serverless Media Workflow

MooYeol Lee

This document describes the serverless media workflow built by the speaker for adding video capabilities to Vingle. It discusses ingesting videos from clients into S3 using transfer acceleration, processing videos with AWS services like Elastic Transcoder and Elemental MediaConvert, and delivering videos via S3 and CloudFront. The architecture evolved over two versions to support features like parallel encoding and bypassing processing when possible to improve performance and reduce costs.

Alfresco DevCon 2018: SDK 3 Multi Module project using Nexus 3 for releases a...

Martin Bergljung

NodeJS Interactive 2019: FaaS meets Frameworks

Chris Bailey

The document discusses Function as a Service (FaaS) and how it can be used with frameworks. FaaS allows developers to build and run application functionalities without managing infrastructure. It focuses on business logic over implementation details. The document provides an overview of FaaS and how it works using Apache OpenWhisk as an example. It also discusses how FaaS can scale functions on demand and be used for building microservices and REST APIs. Appsody is presented as a tool that uses FaaS and stacks to provide a development workflow for building cloud-native applications.

How to Scale With Helix Core and Microsoft Azure

Perforce

This document discusses how to scale Helix Core using Microsoft Azure. It begins by explaining the benefits of using Helix Core and Azure together, such as high performance, scalability, security integration, and availability. It then covers computing, storage, and security options on Azure, including virtual machine types and operating system choices. Next, it describes how to set up global deployments with Helix Core on Azure using techniques like proxies, replicas, and the Perforce federated architecture. It concludes with examples of advanced topologies like build servers, hybrid cloud/on-premises implementations, and multi-cloud considerations.

Java Application Servers Are Dead!

Eberhard Wolff

This document discusses the declining relevance of traditional Java application servers. It argues that application servers are no longer needed as containers for multiple applications due to limitations in isolation. Modern applications are better suited as individual JAR files with their own custom infrastructure and standard monitoring and deployment tools rather than relying on application server-specific approaches. Frameworks like Spring Boot and Dropwizard provide an alternative to application servers by allowing applications to be self-contained deployable units without dependency on external application server infrastructure.

CI_CD_Demo.pptx

TheGame26

This document discusses automating the build, test, and deployment of Oracle CNC solutions using a CI/CD pipeline. Key points: - The pipeline has four stages: 1) download and push Docker images, 2) download and push Helm charts, 3) deploy to the target environment, and 4) post-deployment actions like notifications. - Docker images and Helm charts for the solution are stored in a central repository. When the pipeline runs, it pulls these from the central repository. - The deployment stage uses Helm charts to deploy the solution containers to a Kubernetes cluster in the target pre-production environment. It then checks that all cluster components are running. - The pipeline is

Learning from the Early Adopters of DevOps: A Guidebook to Success featuring ...

Perforce

Many organizations have already taken the leap into DevOps. Luckily, this daunting path is now well lit with best practices from customer experience, toolkits for success, and warning signs for ugly DevOps practices. Guest host Amy DeMartine, Senior analyst at Forrester Research, and Perforce invite you to a live broadcast on using DevOps to break your team's bad habits and increase your business value with speed, minimal errors, and pro knowledge on new ways to collaborate. In this broadcast, you'll learn to: - Use Agile and DevOps to improve collaboration and simplify delivery - Avoid bad DevOps habits - Build a toolkit for success and embrace uncertainty - Reference a use case from one of Perforce's largest customers when setting up your own release cycles

Immutable Infrastructure: the new App Deployment

Axel Fontaine

Immutable Infrastructure: the new App Deployment App deployment and server setup are complex, error-prone and time-consuming. They require OS installers, package managers, configuration recipes, install and deployment scripts, server tuning, hardening and more. But... Is this really necessary? Are we trapped in a mindset of doing things this way just because that's how they've always done? What if we could start over and radically simplify all this? What if, within seconds, and with a single command, we could wrap our application into the bare minimal machine required to run it? What if this machine could then be transported and run unchanged on our laptop and in the cloud? How do the various platforms and tools like AWS, Docker, Heroku and Boxfuse fit into this picture? What are their strengths and weaknesses? When should you use them? This talk is for developers and architects wishing to radically improve and simplify how they deploy their applications. It takes Continuous Delivery to a level far beyond what you've seen today. Welcome to Immutable Infrastructure generation. This is the new black.

Immutable Infrastructure: Rise of the Machine Images

C4Media

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1WlpXHF. Axel Fontaine looks at what Immutable Infrastructure is and how it affects scaling, logging, sessions, configuration, service discovery and more. He also looks at how containers and machine images compare and why some things people took for granted may not be necessary anymore. Filmed at qconlondon.com. Axel Fontaine is the founder and CEO of Boxfuse. Axel is also the creator and project lead of Flyway, the open source tool that makes database migration easy. He is a Continuous Delivery and Immutable Infrastructure expert, a Java Champion, a JavaOne Rockstar and a regular speaker at various large international conferences.

What's hot

Journée DevOps : De l'intégration continue au déploiement continu avec Jenkins

Publicis Sapient Engineering

Perforce Helix Never Dies: DevOps at Bandai Namco Studios

Perforce

Code Hosting: The Key to Autonomous, Self-Service Development

Rachel Maxwell

Heroku

Eberhard Wolff

Spring Boot

Eberhard Wolff

External Master Data in Alfresco: Integrating and Keeping Metadata Consistent...

ITD Systems

Micro Services - Small is Beautiful

Eberhard Wolff

High Availability and Scalability: Too Expensive! Architectures for Future E...

Eberhard Wolff

Perfecting Your Development Tools: Updates to the Helix Plugin for Jenkins

Perforce

ELK Stack

Eberhard Wolff

AWS Summit Tel Aviv - Enterprise Track - Enterprise Apps & Hybrid

Amazon Web Services

Alfresco Day Platform Update

ohej

Chef for DevOps - an Introduction

Sanjeev Sharma

Serverless Media Workflow

MooYeol Lee

Alfresco DevCon 2018: SDK 3 Multi Module project using Nexus 3 for releases a...

Martin Bergljung

NodeJS Interactive 2019: FaaS meets Frameworks

Chris Bailey

How to Scale With Helix Core and Microsoft Azure

Perforce

Java Application Servers Are Dead!

Eberhard Wolff

CI_CD_Demo.pptx

TheGame26

Learning from the Early Adopters of DevOps: A Guidebook to Success featuring ...

Perforce

What's hot (20)

Journée DevOps : De l'intégration continue au déploiement continu avec Jenkins

Perforce Helix Never Dies: DevOps at Bandai Namco Studios

Code Hosting: The Key to Autonomous, Self-Service Development

Heroku

Spring Boot

External Master Data in Alfresco: Integrating and Keeping Metadata Consistent...

Micro Services - Small is Beautiful

High Availability and Scalability: Too Expensive! Architectures for Future E...

Perfecting Your Development Tools: Updates to the Helix Plugin for Jenkins

ELK Stack

AWS Summit Tel Aviv - Enterprise Track - Enterprise Apps & Hybrid

Alfresco Day Platform Update

Chef for DevOps - an Introduction

Serverless Media Workflow

Alfresco DevCon 2018: SDK 3 Multi Module project using Nexus 3 for releases a...

NodeJS Interactive 2019: FaaS meets Frameworks

How to Scale With Helix Core and Microsoft Azure

Java Application Servers Are Dead!

CI_CD_Demo.pptx

Learning from the Early Adopters of DevOps: A Guidebook to Success featuring ...

Similar to The Future of Adhearson

Immutable Infrastructure: the new App Deployment

Axel Fontaine

Immutable Infrastructure: Rise of the Machine Images

C4Media

Kubecon 2019 - Promoting Kubernetes CI/CD to the Next Level

Tim Pouyer

Watch the presentation on YouTube: https://youtu.be/_DvFbN-VR3I Many companies and organizations have adopted CI/CD processes in order to help deliver applications running on Kubernetes quickly, transparently, and with automated tests. While this is a desirable goal, it gets more complex when developing a management layer on top of k8s, especially when both images and helm charts are involved. In developing IBM Cloud Private, we have implemented a CI/CD process that automates promotion through a series of quality gates where we 1) Ensure that all charts (43) and images (135) are in sync across three supported architectures 2) Deploy instances of ICP clusters with different topologies, management services, and infrastructure 3) Run automated and manual functional and security regression tests against those clusters. Since implementation, have we have been able to iterate more quickly by discovering issues earlier in the development process.

Higher. Faster. Stronger. Your Applications with Habitat

Nell Shamrell-Harrington

Habitat is amazing technology - but a new technology alone will not deliver business value. A technology is good for your business when it allows you to deliver stronger value in higher quantities at a faster velocity. For a business, much of the value comes in the software applications it produces - the application itself is what makes it money. Come hear how Habitat’s focus on the application as the unit of automation allows you to focus on the application itself and not worry about where it will run. Habitat also allows you to easily change where and what your application runs on. Your application and business needs will change over time, which means you need to be able to change your application at a very high velocity without being locked into one type of infrastructure or one vendor. Come witness how Habitat allows your applications to be infrastructure and platform agnostic - you focus on the application, Habitat takes care of packaging your software, exporting it, and running it wherever you need. Learn how you can deliver stronger value in higher quantities at a faster velocity without sacrificing stability.

Containers, microservices and serverless for realists

Karthik Gaekwad

The document discusses containers, microservices, and serverless applications for developers. It provides an overview of these topics, including how containers and microservices fit into the DevOps paradigm and allow for better collaboration between development and operations teams. It also discusses trends in container usage and orchestration as well as differences between platforms as a service (PaaS) and serverless applications.

Containers and Microservices for Realists

Oracle Developers

Containers and microservices for realists

Karthik Gaekwad

Karthik Gaekwad presented on containers and microservices. He discussed the evolution of DevOps and how containers and microservices fit within the DevOps paradigm by allowing for collaboration between development and operations teams. He defined containers, microservices, and common containerization concepts. Gaekwad also provided examples of how organizations are using containers for standardization, continuous integration and delivery pipelines, and hosting legacy applications.

Strong practices for rails applications continuous delivery

Robb Kidd

High-velocity organizations deliver change to their customers quickly in a repeatable and predictable way. This talk will explore some pre-requisites and best practices that will help your team move to safe, continuous delivery of your Rails applications. We will demonstrate the path from code commit, to packaged application, to an updated production environment. All of the necessary steps along the way will be fully automated using Chef Delivery. You will leave with some new ideas, practices, and techniques your team can adopt, continuously delivering value to your customers.

A Bit of Everything Chef

Mandi Walls

This document discusses challenges faced by organizations in managing their infrastructure and applications, and how Chef and related tools can help address those challenges. It outlines Chef's approach of treating infrastructure as code and using automation to enable continuous delivery of infrastructure and applications. This allows for faster innovation, better quality/compliance, and rapid time to value. Key aspects covered include infrastructure as code, automation of the development stack, enabling DevOps workflows, and integrating security and compliance into the software delivery pipeline.

What is the Siemens Open Library, and How it Decreased Development Time for E...

DMC, Inc.

Presenter - John Sullivan Eden Innovations is scaling up its liquid chemical admix production facility and needed to move to a more robust automation system. In an effort to keep costs of the control infrastructure down, it was decided to keep the programming in-house and utilize the freely available Open Library as a base for their control system. This session will cover the benefits gained and challenges faced utilizing and customizing the Open Library for a bespoke controls system. The system was developed with minimal time investment by an engineer with no previous experience with the Siemens platform. Through customizing the open library, Eden was able to quickly develop a library that utilizes Siemens best practices and provides building blocks for any future development

C#: Past, Present and Future

Rodolfo Finochietti

C# has evolved significantly over time, from version 1 through the latest version 8. Some key developments include the addition of generics, LINQ, asynchronous programming, and dynamic features. C# continues to focus on productivity and safe, efficient code with recent versions adding capabilities like nullable reference types, async streams, and ranges/indices. .NET has also evolved with improvements to performance and new functionality in versions like .NET Core 2.1. Looking ahead, .NET Core 3 will add support for desktop frameworks like WinForms and WPF.

Habitat talk at CodeMonsters Sofia, Bulgaria Nov 27 2018

Mandi Walls

Performance testing material

Keylabstraining Bangalore

This document discusses various aspects of software performance testing. It defines performance testing as determining how fast a system performs under a workload to validate qualities like scalability and reliability. Key points covered include why performance testing is important, what performance testers must know, benefits of the LoadRunner tool, its versions and features. It also summarizes different types of performance testing like load testing, stress testing, capacity testing and soak testing.

Dockercon State of the Art in Microservices

Adrian Cockcroft

CI/CD on AWS

Bhargav Amin

This document summarizes CI/CD on AWS by Bhargav Amin. It introduces DevOps practices like continuous integration, continuous delivery, and continuous deployment. It explains how to design a CI/CD pipeline and create one on AWS using services like CodeCommit, CodeBuild, CodeDeploy, and CodePipeline. The document provides examples of integrating these services to automate building, testing, and deploying code changes. It also includes a link to a demo repository and discusses managing infrastructure with CI/CD by updating CloudFormation templates in a pipeline.

Kubernetes deep dive - - Huawei 2015-10

Vishnu Kannan

Kubernetes is an open-source container orchestration system that automates deployment, scaling, and management of containerized applications. It was originally designed by Google based on years of experience running containers internally. Kubernetes runs containerized applications across multiple machines, dynamically allocating resources and balancing load. It supports both public and private cloud environments as well as bare metal servers. The system aims to simplify container operations while providing portability and scalability.

goployer, 코드 기반의 배포 도구 - 송주영 (beNX) :: AWS Community Day 2020

AWSKRUG - AWS한국사용자모임

The document discusses deployment best practices and introduces goployer, an open source deployment tool. It summarizes key aspects of infrastructure as code and modern deployment approaches like blue/green and canary deployments. Goployer supports immutable infrastructure, deployment as code, measurement and testing to enable cost effective and simple deployments. The DevOps Art project aims to share infrastructure code, develop open source tools like Terraform and goployer, and conduct online workshops to foster a proper conceptual understanding of DevOps philosophy and ideal implementations based on that philosophy.

Cincom Smalltalk News

ESUG

Cincom provided an update on their Smalltalk product line. Recent releases of Cincom Smalltalk, ObjectStudio, and VisualWorks included improvements to the virtual machine, Store, internationalization, and 64-bit support. Future plans include enhancements to mapping, modeling, encryption, performance, and new features like skins and fluid positioning. Cincom is focusing on maintenance releases, online updates, and gathering customer requirements to further improve their products.

CarTrawler's Feature Team Architecture and Development Process Showcase by Lu...

Lucas Sacramento

This document summarizes an architecture and development showcase. It discusses using a monorepo development approach, development process involving tech discussions, coding, and code reviews, and a pipeline involving linting, unit testing, static analysis, building, acceptance testing, visual regression testing, and performance auditing. It also discusses using containers and Kubernetes for container orchestration to provide benefits like provisioning, deployment, resource allocation, health monitoring, scaling, self-healing, automated rollouts and rollbacks, and service discovery/load balancing.

Structured Functional Automated Web Service Testing

rdekleijn

Similar to The Future of Adhearson (20)

Immutable Infrastructure: the new App Deployment

Immutable Infrastructure: Rise of the Machine Images

Kubecon 2019 - Promoting Kubernetes CI/CD to the Next Level

Higher. Faster. Stronger. Your Applications with Habitat

Containers, microservices and serverless for realists

Containers and Microservices for Realists

Containers and microservices for realists

Strong practices for rails applications continuous delivery

A Bit of Everything Chef

What is the Siemens Open Library, and How it Decreased Development Time for E...

C#: Past, Present and Future

Habitat talk at CodeMonsters Sofia, Bulgaria Nov 27 2018

Performance testing material

Dockercon State of the Art in Microservices

CI/CD on AWS

Kubernetes deep dive - - Huawei 2015-10

goployer, 코드 기반의 배포 도구 - 송주영 (beNX) :: AWS Community Day 2020

Cincom Smalltalk News

CarTrawler's Feature Team Architecture and Development Process Showcase by Lu...

Structured Functional Automated Web Service Testing

More from Mojo Lingo

ConnectJS 2015: Video Killed the Telephone Star

The Future of Adhearson

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to The Future of Adhearson

Similar to The Future of Adhearson (20)

More from Mojo Lingo

More from Mojo Lingo (20)

Recently uploaded

Recently uploaded (20)

The Future of Adhearson