I recently got my CSPO training and certification and my head is still abuzz with the information overload that was delivered over the course of a weekend. I went in brimming with confidence from having worked as a developer and devops engineer on agile projects throughout my career. But I quickly swallowed my pride when I got ALL my answers wrong on the first spot quiz of the day.
Turns out, most projects are not really agile but follows more of a ‘scrumfall’ methodology to accommodate the whims and demands of the clients. A lot of my previous notions were…
After recently leaving a cushy position at PwC to pursue my MBA degree, I began to realize more and more how similar working at a Big4 was to studying at a top tier business school. As the weeks progressed, the more classes and networking activities I attended, the more obvious the similarities became. Since the topic is on Big4, I will list down the big four similarities I noticed.
Ask any b-school grad and they will all tell you the same thing. The most valuable aspect of any business program is the connections and networking you make with your cohort…
This article by theoretical economist W. Brian Arthur challenges one of the basic economic theories on returns of margin. Up until then, much had been written about the diminishing margins of return by Alfred Marshall and his contemporaries. In Arthur’s words, the old way of thinking was “Well, we have a pretty good product, and if we look after our costs and we manage to execute pretty well, we’ll get our 15% of the market”. This may be true for industrial-age factories or barbershops. …
The first half of the job is relatively straightforward. The job should be executed inside a prod agent (short for production). It defines two parameters. One holds the name of the service that should be scaled. The other expected a number of replicas that should be added or removed. If the value is positive, the service will be up-scaled. A negative value means that it should de-scale.
The job defines only one stage called Scale. Inside it is a single step defined inside a script. It executes the docker service inspect command and retrieves the current number of replicas. It…
We have all used containers. But one of the basic requirements of any client today is optimal costs. And that means keeping your infrastructure as lean as you can, as much as you can.
It's the night before Black Friday. You're logging out of work with the peace of mind that your services are all configured with replica sets and threshold limits. Black Friday will be a walk in the park. And it is. What you don't realize is that you would need to scale down your services once the weekend is over. And now you're on monitoring duty over…
● AWS Elastic Load Balancer
● AWS Elastic Container Service
● Netflix Eureka
● Netflix Zuul
The first task in setting up the infrastructure is to get the microservices containerized and running on ECS/ Docker. Assuming the microservices are Java and built as JAR files, a sample Dockerfile would be:
ADD <path to sample JAR> Sample-Service-0.0.1.jar
ENTRYPOINT [“java”, “-jar”, “Sample-Service-0.0.1.jar”]
Amazon’s ECS is preferred because we could leverage the service to auto-scale depending on the incoming requests to the microservice.
Alternative to ECS could be Docker Swarm.
Docker is an open-source container-based platform, which packages your application and all its dependencies together in form of containers so that your application works seamlessly in any environment ( development, test or production).
It is a platform used for building, shipping and running our applications.
About a year ago, we had a project come in which required automating infrastructure setup, configuration management and change management. I happened to be at the right place at the right time and was given in charge of the whole thing.
The project was designed on the microservices style of architecture and our teams decided on using GitHub as the source code repository, JFrog for storing our build artifacts, a RHEL based Kubernetes cluster as the deployment platform and Jenkins to drive the whole thing through a continuous integration, testing and deployment pipeline. In this way, developers, QA, and automation…
You have probably heard about containers and virtualization in your CS classes back in college, and now you hear the ‘cool’ devs at your job talk about Docker (or Vagrant) at the coffee machine. Docker is hotter than hot because it makes it possible to get far more apps running on the same old servers and it also makes it very easy to package and ship programs.
First things first.
To put it simply, Docker is a type of virtualization which is faster and lighter than other VMs thanks to a different attitude to the infrastructure. If we compare it…
DevOps evangelist getting his business degree