About me

 I'm an enthusiastic and self-motivated software architect with:

  • experience in cloud solutions architecture and DevSecOps
  • 11+ years of polyglot experience in hands-on: .NET, Java, Node/JS/TS/Angular, Python
  • proficient in SQL, NoSQL, SOA, μSOA, EDA, TDD, design principles and patterns
  • excellent understanding of current enterprise software technologies and development practices/tools, including virtual environments, source control, remote development, issue tracking, build and test automation, and networking management
  • research and development for Conversational AI/Vision AI/DL/ML

I've obtained the following certifications:

  • Microsoft Certified: Azure Solutions Architect Expert
  • Google Certified: Professional Cloud Architect
  • AWS Certified: Solutions Architect Associate
  • The Linux Foundation Certified: Kubernetes Application Developer (CKAD)
  • Microsoft Certified: Azure Developer Associate
  • Google Certified: Associate Cloud Engineer
  • AWS Certified: Developer Associate
  • The Linux Foundation Certified: Kubernetes and Cloud Native Associate (KCNA)
  • Microsoft Certified: Azure Fundamentals
  • Google Certified: Cloud Digital Leader
  • AWS Certified: Cloud Practitioner

My hobbies are:

  • science and technology
  • gaming

You can see some of my independent activity on my blog and on my GitHub profile.

Comments

Post a Comment

Popular posts from this blog

Rebalancer for RabbitMQ, SQS, etc.

Image
Rebalancer (forked from Jack Vanlightly  and improved)      Create Kafka style consumer groups in other technologies. Rebalancer was born of the need for consumer groups with RabbitMQ. But Rebalancer is completely technology agnostic and will balance activity over any group of resources across a group of participating nodes. Use cases Create Kafka-like "consumer groups" with messaging technologies like RabbitMQ, SQS, etc. Consume a group of resources such as file shares, FTPs, S3 buckets between the instances of a scaled out application. Single Active-Consumer / Active-Backup Create an application cluster that consumes a single resource in a highly available manner. The cluster leader (Coordinator) consumes the single resource and the slaves (Followers) remain idle in backup in case the leader dies. Balancing assignment of multiple resources over multiples nodes Consuming from a single resource with backup nodes in case of failure Concepts ...
Read more

Securing workloads with ClamAV: Helm chart for an OpenShift ready Docker image

     In today's era of enterprise-grade container orchestration, OpenShift stands out as a robust platform, providing enhanced security and management features built on Kubernetes. As organizations increasingly rely on OpenShift for deploying mission-critical workloads, ensuring comprehensive security measures becomes imperative. One essential component of a robust security strategy is protecting against malware and viruses that could potentially compromise sensitive data and infrastructure.      In this guide, we'll explore how to integrate ClamAV, a powerful open-source antivirus software, into OpenShift deployments using a custom Docker image built on top of the official Docker image and a tailored Helm chart. Understanding ClamAV and OpenShift      ClamAV is a trusted antivirus engine renowned for its ability to detect and neutralize a wide range of malware, including viruses, trojans, and other malicious software. While ClamAV is traditi...
Read more

Poison message handling RabbitMQ

Image
     Poison message handling in RabbitMQ it is available as of RabbitMQ 3.8.0, by using the new type of queue:  Quorum Queues .      Quorum queue support handling of poison messages, that is, messages that cause a consumer to repeatedly requeue a delivery (possibly due to a consumer failure) such that the message is never consumed completely and positively acknowledged so that it can be marked for deletion by RabbitMQ.      Be aware, some features are not currently supported by quorum queues:      Quorum queues keep track of the number of unsuccessful delivery attempts and expose it in the "x-delivery-count" header that is included with any redelivered message.      It is possible to set a delivery limit for a queue using a policy argument, delivery-limit. When a message has been returned more times than the limit the message will be dropped or dead-lettered (if a DLX is configu...
Read more