Azure PaaS is Dead - Death by Container

One of Azure's big initial innovations was their PaaS platforms.  These services were a level up from most of Amazon's offerings.

Microsoft appears to be in the process of killing of their traditional offerings. They are instead exposing the containerized underpinnings and forcing customers to do their own packaging and Docker image construction.  This makes sense for large enterprises but means that teams need to understand the underlying O/S software modules and system components that may need to be installed in their containers.

PaaS

PaaS makes it easier for less sophisticated teams to deploy sophisticated scalable applications. Azure PaaS lets customers deploy applications without worrying about the Operating System, System Patching, CVE security scanning , load balancing, log aggregation, or other issues.  The opacity of the underlying system meant teams had to know less and that teams couldn't know more if they wanted too.

Microsoft modernized much of their PaaS platform by providing additional isolation via Docker Containers and Kubernetes that is hidden under the surface of the PaaS offering. It looks like their future plans are based on having users manage their Docker images and containers themselves.

Azure App Services on GitHub have been disabled

Most of the Azure App Service repositories have been archived with no information about what happened or links to go-forward guidance.  This means Microsoft is no longer updating the _hidden_ Docker containers that the PaaS services are deployed into for many of the languages.
As of 2020 Archived projects include
  • Node
  • Ruby
  • PHP
  • Tomcat
  • Wildfly
  • Java

Microsoft's View of PaaS and IaaS

Kubernetes deployed models require a skill set somewhere between IaaS and PaaS. Some parts are as complicated as full IaaS Companies don't own the O/S but they do own patching and scanning of containers that are virtually mini-operating systems.

Three Different Azure Services

These services expose the Kubernetes Underpinnings. They require that you create your own Docker images for deployment.  Docker Images are not being updated for any of these that can take deployments without your own container.
  • AZURE APP SERVICE - LINUX
  • AZURE CONTAINER SERVICE - LINUX
  • AZURE SERVICE FABRIC - LINUX
My conclusions are based on my effort at deploying the Java Tika document parsing jar in Azure in the same way I did with AWS beanstalk.  This article describes the experience Exploring Docker on Azure PaaS with Tika

Archived repositories added 2020/09/28

Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS access id and secret key.
Read more