Category: All

All posts across the whole website belong to this category. They might also belong to some other categories as well, but this one holds all of them. Hence the descriptive name – All.

F5 acquires NGINX

NGINX, the company behind one of the most popular web servers, has been acquired by F5. Of course, I’m glad for the NGINX team and founders, for who this is quite an accomplishment. But at the same time, much like many of the recent acquisitions, this one worries me. NGINX and F5 were competing in certain areas. That competition is now gone.

As always, they say that they will keep NGINX brand, team, technology, and even invest more in the Open Source side of things. But I’m not holding my breath. We’ve seen way too many screw ups on that front in the last few years.

Having the Open Source offering is good though. If it continues to grow and develop – even better. But if not, at least there is an option of forking, rebranding, and building on top.

Headless CMS: REST vs JSON:API vs GraphQL

“Headless CMS: REST vs JSON:API vs GraphQL” is an interesting comparison of the REST, JSON:API, and GraphQL:

In this blog post, we will compare REST, JSON:API and GraphQL. First, we’ll look at an architectural, CMS-agnostic comparison, followed by evaluating some Drupal-specific implementation details.

Markdeep – Markdown on steroids

Markdown is of the best formats for writing documentation. It’s intuitive, cross-platform, and can be read or written without any special tools. But it does have a variety of limitations too (no includes, no special formatting for advanced things like charts or formulas, etc).

Markdeep is one of the tools that tries to extend Markdown and solve some of its limitations.

Markdeep is a technology for writing plain text documents that will look good in any web browser, whether local or remote. It supports diagrams, calendars, equations, and other features as extensions of Markdown syntax.

GitGuardian API Security Best Practices

The team behind GitGuardian, a tool that helps developers to keep credentials and other secrets outside of the source code, shares their documentation for the API security best practices.

The cool bit about their documentation is that it covers both how to avoid the issues and how to solve them if they happened.