Pivotal Cloud Foundry is the professional enterprise solution of Cloud Foundry supplied to business. We tend to abbreviate it to PCF. Essentially PCF is largely the same code base as the open source Cloud Foundry on Github except for a bespoke components, which are web front-end application. PCF has an Operations Manager as known as Ops-Man and an Administration Manager known as Apps-Man.

Hot shots are a series of shorter podcast episodes from PEAT UK. Small bite size chunks of advice on DEV OPS and Platform Engineering. We had an issue with Docker containers and memory utilisation. Suddenly our Spring Boot integration tests were dying with an exit code of 137.

In this final episode of the experimental series 1, we take a gentle overview of cloud computing. We look at the history of cloud computing

Why and how did this form of computing become popular?

We get to know the meaning of IaaS, PaaS and SaaS. We examine the constituent elements of so-called "cloud" computing. We embrace the positives and negatives of this mode of enterprise.

In this episode, we take an overview of a recent progression in software engineering called Infrastructure as Code. It solves the problems of reliability, configuration and deployment for a software stack. We look at the tools such Vagrant, Puppet, Ansible and Terraform. Finally, we devote entire section to the Ruby programming language and its suitability to Infrastructure as Code.

In this week's episode, we look at an alternate forms of software engineering beyond the typical developer led roles. We consider developer operations (Dev Ops) and also platform engineering roles (specifically cloud native).

In this week's episode, we discussion the topic of pair development, which is more commonly known as pair-programming. We also give advice on being at successful job interviews where pairing is used a test metric.

In this episode we explore the new brand selection for the Java EE Platform now that the umbrella specification is moving from Oracle Corporation to the Eclipse Foundation

This episode is all about Heroku's Twelve Factor applications, which are design rules for building flexible, sustainable and robust cloud-native application.

I. Codebase - One codebase tracked in revision control, many deploys

II. Dependencies - Explicitly declare and isolate dependencies

III. Config - Store config in the environment

IV. Backing services - Treat backing services as attached resources

V. Build, release, run - Strictly separate build and run stages

VI. Processes - Execute the app as one or more stateless processes

VII. Port binding - Export services via port binding

VIII. Concurrency - Scale out via the process model

IX. Disposability - Maximize robustness with fast startup and graceful shutdown

X. Dev/prod parity - Keep development, staging, and production as similar as possible

XI. Logs - Treat logs as event streams

XII. Admin processes - Run admin/management tasks as one-off processes

Experimental podcast series and in this episode we look at basic difference between hardware and software. We also consider the future relationship between hardware and software. Why is my television behaving as badly as a general purpose computer?

This episode is all about Heroku's Twelve Factor applications, which are design rules for building flexible, sustainable and robust cloud-native application.