[TriLUG] Middleware: was: have a job - Python, Django, Postgres, Flask

[Lance A. Brown via TriLUG]

In a former life I ran a Platform as a Service system at a bank that expanded the Application Layer 
(Middleware) layer in John's diagram.  "Middleware" described software and libraries such as the 
Java JRE, and security and other libraries provided to applications either automatically or as part 
of the application build process.

Application Code + "Middleware" was built and packaged into a container that then ran on the PaaS 
platform to deliver the application functionality.  This gave us the ability to manage the 
middleware bits centrally instead of forcing application teams to keep up with all those changes in 
each application individually.

"Middleware" is a slippery concept.

--[Lance]

John Vaughters via TriLUG wrote on 7/13/2022 11:10 AM:
> That's the way I always viewed it as well.
>
> Presentation Layer <-> Application Layer (Middleware) <-> Storage/Data Layer
>
> But I also see the point that it can have many meanings, but the description above is somewhat physical separation as well in the sense that those layers tend to live on separate servers, which in and of itself get's messy when we start defining servers in a virtual/container world of separation. However, I think you get the gist.
>