In this Wednesday Evening Training, we continued our exploration of basic infrastructure. This time, we explored web server technology. In this, a special welcome for our French colleague Théo Berthin who visited our Dutch site.
Apache, IIS, Tomcat, all are fine examples of webservers. But how do they work, from a technical point of view? In this session we have taken a look at the whole process of accepting and processing requests and generating responses. Which components are involved, how do they interact and how has the web server technology involved the past decade(s)?
Bart van Beek and I had prepared a presentation and some demo's / walkthroughs for this.
After a deep dive into the http protocol, requests and responses, we first discussed IIS. IIS, Internet Information Services, is the web server technology of Microsoft. We have discussed processing requests, the request pipeline, process handling with application pools and web workers, how IIS supports .NET and .NET Core and how .NET Core applications are served using other web server platforms on non-Microsoft Operating Systems.
We enjoyed demo's / walkthroughs on Spring and Tomcat web server, and Microsoft's IIS and had plenty of opportunity for lively discussions on security, scaling and other technical topics. Especially when NodeJS (as a web server) came up, the discussion seemed to intensify ;).
As a bonus, Bart van Beek has given us a recap on the Open Systems Interconnection model (OSI). This model is a conceptual model that characterizes and standardizes the communication functions of a telecommunication or computing system without regard to its underlying internal structure and technology. http, tcp/ip can be placed in this model.
Also this time, Bart managed to largely fill the room-wide whiteboard!
There definitely were plenty of questions left at the end of this week's Wednesday Evening Training. Also, the community would like to experiment with both platforms in handson labs. In the next Wednesday Evening Training on infra we'll definitely include labs for both IIS and Spring/Tomcat and provide some answers on the remaining questions.
To be continued!
OSI model: https://en.wikipedia.org/wiki/OSI_model
Web server (rather obvious, but a nice place to start anyway):https://en.wikipedia.org/wiki/Web_server
IIS official site (obvious as well): https://www.iis.net
More on ASP.NET Core Running under IIS: https://weblog.west-wind.com/posts/2017/Mar/16/More-on-ASPNET-Core-Running-under-IIS
Serving Web Content with Spring MVC: https://spring.io/guides/gs/serving-web-content/
Apache Tomcat (the place to start): http://tomcat.apache.org/
NodeJS: https://www.w3schools.com/nodejs/nodejs_http.asp
#capgemini #werkenbijcapgemini #lifeatcapgemini #wednesdayeveningtraining #iis #tomcat #spring #microsoft #webserver #java #nodejs #dotnet #dotnetcore #dotnetcore #kestrel #httpsys
Apache, IIS, Tomcat, all are fine examples of webservers. But how do they work, from a technical point of view? In this session we have taken a look at the whole process of accepting and processing requests and generating responses. Which components are involved, how do they interact and how has the web server technology involved the past decade(s)?
Bart van Beek and I had prepared a presentation and some demo's / walkthroughs for this.
After a deep dive into the http protocol, requests and responses, we first discussed IIS. IIS, Internet Information Services, is the web server technology of Microsoft. We have discussed processing requests, the request pipeline, process handling with application pools and web workers, how IIS supports .NET and .NET Core and how .NET Core applications are served using other web server platforms on non-Microsoft Operating Systems.
We enjoyed demo's / walkthroughs on Spring and Tomcat web server, and Microsoft's IIS and had plenty of opportunity for lively discussions on security, scaling and other technical topics. Especially when NodeJS (as a web server) came up, the discussion seemed to intensify ;).
As a bonus, Bart van Beek has given us a recap on the Open Systems Interconnection model (OSI). This model is a conceptual model that characterizes and standardizes the communication functions of a telecommunication or computing system without regard to its underlying internal structure and technology. http, tcp/ip can be placed in this model.
Also this time, Bart managed to largely fill the room-wide whiteboard!
There definitely were plenty of questions left at the end of this week's Wednesday Evening Training. Also, the community would like to experiment with both platforms in handson labs. In the next Wednesday Evening Training on infra we'll definitely include labs for both IIS and Spring/Tomcat and provide some answers on the remaining questions.
To be continued!
Further reading
Do you want to read more on web server technology? Here are some links...OSI model: https://en.wikipedia.org/wiki/OSI_model
Web server (rather obvious, but a nice place to start anyway):https://en.wikipedia.org/wiki/Web_server
IIS official site (obvious as well): https://www.iis.net
More on ASP.NET Core Running under IIS: https://weblog.west-wind.com/posts/2017/Mar/16/More-on-ASPNET-Core-Running-under-IIS
Serving Web Content with Spring MVC: https://spring.io/guides/gs/serving-web-content/
Apache Tomcat (the place to start): http://tomcat.apache.org/
NodeJS: https://www.w3schools.com/nodejs/nodejs_http.asp
Past Wednesday Evening Trainings
You'll find post of previous sessions here: https://www.linkedin.com/search/results/content/?keywords=%23wednesdayeveningtraining
Next week
In next week's Wednesday Evening Training, we'll be taking a deep dive in infrastructure a well. In this "how stuff works" session we will discuss various infra topics from a technical point of view.#capgemini #werkenbijcapgemini #lifeatcapgemini #wednesdayeveningtraining #iis #tomcat #spring #microsoft #webserver #java #nodejs #dotnet #dotnetcore #dotnetcore #kestrel #httpsys
No comments:
Post a Comment