In a previous post we covered the history and rules behind capabilities. In this post, we'll go through some examples of how Linux capabilities work and can be used, and the tooling available. We will also take a look at why capabilities are important when working with containers.

As Container Solutions grows, so does the number of projects we commit to every year. To keep quality high and continue to serve our clients well, we have learned to streamline the way we deliver our services.

I’d like to share with you the architecture and programming pattern we've been using to build Cloud Native applications. The use case I'm going to present is a RESTful application deployed on AWS, using AWS API Gateway and AWS Lambda. I want to show how by adopting specific AWS components and programming paradigms, we can increase the reliability of the applications we write, while also improving their maintainability.

Container Solutions is a consulting company that focuses on Cloud Native transformations. Working as a Cloud Native engineer here means you get assigned to work on projects for particular clients. When you finish one project, you are moved to the next one.

Debugging Docker containers can be a very challenging process. Here, I’ll share a few basic techniques for debugging containers—mostly Docker ones, but the techniques are also valid for many other types of Linux container engines. (The methods I’ll detail here are intended for Linux-based systems.)