• News
  • Security
  • Products
  • About Seqrite
Blogs on Information Technology, Network & Cybersecurity | Seqrite Blog
  • News
  • Security
  • Products
  • About Seqrite
Home  /  Android • Application • automation • Cloud Computing  /  The Evergreen ‘Make’ Utility: A cost-effective way of deployments on Cloud.
The Evergreen ‘Make’ Utility: A cost-effective way of deployments on Cloud.
01 October 2020

The Evergreen ‘Make’ Utility: A cost-effective way of deployments on Cloud.

Written by Prafulla Ranadive
Prafulla Ranadive
Android, Application, automation, Cloud Computing

It might be difficult to find a software engineer who does not know ‘Make’ utility. ‘GNU Make’ is a tool which controls the generation of executables and other stuff related to the application code building.

Capabilities of ‘Make’ are many ranging from simple code compilation and installation to collection of all the dependencies of an application. It is designed so nicely that we can even use it for implementing the deployment pipeline for your solution. Let us see how we can achieve this.

One of our recent needs was to automate the deployment of our services onto the cloud. Since our system is central to many other products and services, we ended up needing multiple environments to be used for distinct purposes such as functional testing, performance testing, integration, etc.

To cater to this demand for a dedicated environment, we thought of using ‘Make’ utility instead of any other cloud-specific tools. And we are so happy that our technology choice worked well. Let us walk you through the details.

We had decided to keep the number of new tools and technologies minimum and stick to the opensource technologies only, as keeping the cost of operation to the minimum was one of the constraints. We were already using the ‘Make’ tool for building our components written in ‘Go’ language. The next step for us was to use it for triggering docker image build operation, pushing the image to the private repository, and for launching/creating all cloud services required for the functioning of our services.

Makefile target rule helped us to divide the entire flow into smaller independent modules. We wrote separate target rules for each step such as building a docker image, pushing image and launching clusters, etc.

Code build and Docker image creation

 

build:

@echo “Code compilation …”

# Language specific build commands go here.

docker-build: build

@echo “Building docker image …”

$(DOCKERBUILD) . -t $(ENV)$(BINARY_NAME) -f $(PROJBASE)/Dockerfile

Pushing the docker image to the private repository

 

docker-push:

@echo “Pushing docker image to cloud hub …”

# This contains, cloud service-provider specific commands to push the docker image to the respective repository

Deploy the application to the respective cloud

 

deploy:

@echo “Deploying application to the environment …”

# This contains, cloud service-provider specific commands to deploy the application to the cluster.

# For example, for the AWS cloud, this will contain a cloudformation command to create a stack.

# Likewise, Terraform can also be used to deploy the application to the respective cloud.

Initiate table creation

 

create-table:

# This contains, creation of all the applications tables.

@sh deployment/table_creation.sh

Initiate end to end deployment

 

e2e-deploy: docker-build docker-push create-table deploy

That is it. Isn’t it a simple yet effective approach to trigger application deployment? Moreover, it enables one to achieve application deployment to any cloud in a cost-effective manner. And, it is a cloud-agnostic way of deployment, so nothing is tightly coupled.

 Previous PostThe return of the Emotet as the world unlocks!
Next Post  Are you making these common public cloud migration mistakes?
Prafulla Ranadive

About Prafulla Ranadive

Prafulla is Architect in Quick Heal Technologies. He has 16 years of experience in software industry. Prafulla brings in vast amount work experience of various...

Articles by Prafulla Ranadive »

Related Posts

  • What is EDR? Endpoint detection and response

    Why Endpoint Detection and Response (EDR) Is The Future of Endpoint Protection?

    May 27, 2024
  • SEQRITE Cloud Security Solution

    Cloud Security Under Siege: Fortify Your Defences Against Emerging Threats

    September 5, 2023
  • Moving to the cloud? Learn how to manage your cyber risks on the journey to cloud transformation

    August 12, 2021
Featured Authors
  • Seqrite
    Seqrite

    Follow us for the latest updates and insights related to security for...

    Read more..
  • Sanjay Katkar
    Sanjay Katkar

    Sanjay Katkar is the Joint Managing Director of Quick Heal Technologies...

    Read more..
  • Mahua Chakrabarthy
    Mahua Chakrabarthy

    A tea connoisseur who firmly believes that life is too short for dull content....

    Read more..
Topics
apt (21) BYOD (11) Cyber-attack (36) cyber-attacks (58) cyberattack (16) cyberattacks (13) Cybersecurity (326) cyber security (34) Cyber threat (33) cyber threats (48) data breach (55) data breaches (28) data loss (28) data loss prevention (34) data privacy (13) data protection (28) data security (15) DLP (49) Encryption (16) endpoint security (108) Enterprise security (17) Exploit (14) firewall (11) GDPR (12) hackers (11) malware (76) malware attack (23) malware attacks (12) MDM (26) Microsoft (15) Network security (22) Patch Management (12) phishing (27) Ransomware (67) ransomware attack (30) ransomware attacks (30) ransomware protection (14) security (12) Seqrite (35) Seqrite Encryption (27) Seqrite EPS (33) Seqrite Services (16) UTM (34) Vulnerability (17) windows (11)
Loading
Resources
  • White Papers
  • Datasheets
  • Threat Reports
  • Manuals
  • Case Studies
About Us
  • About Seqrite
  • Leadership
  • Awards & Certifications
  • Newsroom
Archives
  • By Date
  • By Category
Loading

© 2025 Quick Heal Technologies Ltd. Cookie Policies Privacy Policies