In the beginning, we had servers behind a load balancer.
Each server of a given kind (api servers, frontend servers, etc) had the same set of processes
running on them, and each application bound to the same statically allocated port on every server.
This worked well! Over time we wanted to take better advantage of our often under utilized
servers, and adjusting our CPU to memory to IOPS ratio during the three years
SKU depreciation cycle wasn’t fast enough as our system architectures continued to quickly evolve.
The JOnAS application server is evolving to provide a PaaS platform to run Java applications. For this, the application server must be able to isolate clients sharing the same platform. This insulation is especially critical among c...
The title of this article is one that is asked on many occasions around the forums and SQL Server community. SQL Server Integration Services (SSIS) is the Extract, Transform and Load (ETL) platform behind SQL Server. There aren’t ma...
The IBM WebSphere Application Server V7 Feature Pack for OSGi Applications and Java Persistence API (JPA) 2.0 is now generally available. Java Persistence API - OSGi - Java - IBM WebSphere Application Server - Programming
Microservices Without the Servers (Amazon) — By “serverless”, we mean no explicit infrastructure required, as in: no servers, no deployments onto servers, no installed software of any kind. We’ll use only managed cloud services and ...