So, welcome to the 4th edition of developer news!
Again, as with last week, I could have included many more items, but have tried to limit it to the top 5. As I said before, if interest does continue, I am considering some other formats for daily news and commentary in addition to this weekly post.
So, here we go again:
1 : Researchers find serious flaw in WPA2 protocol
A big story for this week, covered seemingly everywhere, is a security flaw found in the WPA2 protocol, the protocol used to secure most WIFI networks. Known as the KRACK attack, it affects most devices. For more information on the research and the implications, checkout the details here.
2: Docker announces native Kubernetes support
Docker has announced native support for Kubernetes. This means that anyone developing for Docker has the option of testing locally using both Swarm and Kubernetes schedulers.
On of the advantages of using Docker is the promise that the application runs the same way in development as it does in production.
This announcement means, that this promise now extends to scheduling and orchestration of our containers. For more information, see the announcement here.
3 : Apache HTTP server gets native Let’s Encrypt support
Another item relating to native support. This time, it’s the apache http server (http), announcing native support for the ACME protocol used by Let’s Encrypt.
Hopefully this means that the process of deploying secure websites should become simpler.
See here for more details on what this means.
4 : Servless computing – economic and architectural impact
This is less of a news item, but more of an interesting paper discussing the impact of so-called ‘serverless’ computing.
For those not aware, it’s an architectural style that means as developers we are deploying executable functions and configuring routing when delivering web applications or services.
It obviously does not mean there are no servers, only that the platform we deploy on is responsible for maintaining them, and scheduling our functions in response to a valid request.
I think it’s an approach that certainly does hold some merit, but would be very wary of a lot of the hype going on around this at the moment.
Take a look at the paper here.
5 : Facbook open sources RacerD
The final item for this week, is an announcement by Facebook, open sourcing their ‘RacerD’ tool.
This tool is a static code analysis tool that analyses Java code for potential race conditions.
Being a static analysis tool, it obviously does not require running the application in order to look for potential race conditions.
I find it interesting that even now, Java demonstrates it serves it’s purpose in modern large scale applications, and that organisations are still pushing the boundaries and developing new toolsets around Java dev.
Checkout their page here for more info.
So, that’s it for this week. If you have any articles, announcements, tutorials, or anything else you think should be included next week, then just drop me an email.