Infrastructure Knowledge

During a 10 years career, I was able to see the evolution of the IT philosophy in a Middleware Context.

​

The great advantage I realized to work in the Middleware world, was that it require to have strongs:

 - Network notions

 - System notions

 - Applicative notions

​

So it require to be polyvalent and have a good IT generale culture to be efficient.

​

At the beginning monolithic applications architectures were the main cases we met. Working in Sciforma/BNP/SG, I've seen a lot of client projects designed with this architecture with heavy Web Application Servers as Weblogic/WebsphereAS...but with an application deployed on it using maximum 30% of the WAS features.

​

Automation era brought new ways of thinking and gave birth to new philosophically tought tools as Docker which had the effect of a tsumani in the biggest and oldest IT dependant companies.

​

I participated to this evolution by for example building the Openshift Plateform in SG.

Today we do not stop of hearing API, API, API...! As  it now exists a native evolved and resilient service for the infrastructure with Microservices, it's the way to provide the service which is the challenge. Self provisionning is the leitmotiv in the company requiring performances, autonomy and security. I think HAPI project design responded perfectly to this need (A Tomcat installation can be self ordered and provisionned in 1 minute thanks to this API). It free us a lot of time and we use it to improve more and more features to make client's life easier.