Cloud as a Story - Vunvulea Radu

 Let's talk about Azure autoscaling feature. I found often people that are configure autoscaling without understanding what each item from the configuration panel represents.  THE STORY One of my friends called me a few days ago telling me that the scaling configuration of the App Service that he manages does not work as expected and there might be a bug. It is not common to find such issues on autoscaling capabilities, because of this I suspected from start a miss-configuration. The reported problem was related to how fast the no. of instances are growing. After reviewing the configuration I notified that the cooldown time period was configured wrong. AUTOSCALING INSIGHTS Let's start with an example. We have autoscaling configured for a web app that is using Standard App Service Plan. The scaleout is configured with the following configuration: When the average CPU level is greater than 70, for more than 40 minutes, increase count with 3 When the average CPU level is greater t

This week I had the opportunity to talk about microservices during Connect.IT. The main topic that I wanted to cover was related to the things that we forget about when we build a solution on top of microservices. The online event was organized during the afternoon and gather people especially from Targu-Mures and Cluj-Napoca. You can check below the presentation content: Title : THE MICROSERVICES CONFUSION Abstract :  Nowadays, every new project that we start is around microservices. You cannot build anymore a simple solution that goes into production for a 2-week time frame. Many times we grow the project complexity because of the current IT trends without thinking about what we need. T he focus of the session is around microservices and what is the impact of it during development, automation and operation phase. The purpose is to identify the balance between the size, number and complexity of the services taking into account the delivery time and budget, especially during the first

As you already know, the cloud is already a commodity and is part of the most software solutions available on the market nowadays. Nevertheless, if you do quality assurance or testing activities on cloud application, you have a lot of challenges.  QA and Testers are ignored by cloud The expectation from the marker is to have people on these roles that know how to test applications and to run different procedures to ensure that the systems run as expected. You might say that testing an application that is running inside the cloud is the same as on-premises. It might be similar but not the same. Things like: Logs locations Metrics repositories New interaction with storages Access to resources A point in time restore Mechanisms to run different tests (e.g., DDoS attack) Security ... and many more are different. Personally, I would even say that from the cloud point of view, quality assurance (QA) and testers are left behind and ignored.  If we take a look at the learning paths or certific