Development, Startup, Technology

DevOps: Start Slow and Go Long

Whenever any CIO, CTO wants to introduce DevOps practices within organisation, they face lots of push backs and low adoption rate. DevOps is not about setting up all the tools and stitching them together in one go. Its cultural shift for all. Every one from business to development to operations needs to understand ROI and agree on adoption.

We suggest Start slow from each level and Go Long.

Steps to take for DevOps Readiness:

  • Automate repetitive tasks with small scripts first rather than putting Bulky tools. Examples for small product teams:
    • Developers can first Implement Git pre-commit hooks for static code analysis locally
    • Developers can implement Git Post-commit hooks for Build generation.
    • Operations can write shell scripts to rake git pull on servers if they are doing manually every time.
    • Operations can write shell scripts to monitor infra and send email notifications to relevant team members.
    • QA can implement automated test scripts for Load and Security Tests.
    • Everyone should look for any possibility for quick automations tasks that reduces repetitive tasks.
  • Start introducing tools best fit for job on all levels that costs nothing initially. Examples:
    • Static code analysis can be done with SonarQube, it’s free and quick to setup.
    • Peer code review can be done with ReviewBoard, it’s open source.
    • You can still all pieces of DevOps and build Pipelines with Jenkins
    • Jenkins have lots of ready to use plugins for quick integrations like, AWS Code Deploy, if you are using AWS Infrastructure Code Deploy is free to use.
    • Separate Dev, QA and Production environments to avoid any not tested deployments.
    • Implement tools like Nagios and GreyLogs for monitoring.

This will give you start of your DevOps journey. For DevOps consultancy or end-to-end implementation, feel free to contact us.

Read More
Development, Startup, Technology

Building Serverless e-commerce Platform

If you are worried about recurring cost of infrastructure even your actual user transactions haven’t started yet and you want to avoid upfront and recurring cost. Go Serverless!

Focus on your application, not the infrastructure

What is Serverless e-commerce?

Most of cloud providers AWS, Azure, Google Cloud, provides functionality to execute code by allocating dynamic resources. With Dynamic allocation they charge for only execution time.

Imaging in e-commerce you get charges only for User Login/Logout, Product Catalogue Search and Listing and then Order Creation. After Order creation your start processing payments, warehouse routing and initiate delivery process. This flow can be handled with small small functions and sticking various available services.

Advantages of Serverless:

  • Cost reduction
  • Realtime Scalability
  • Simplified Code (Implementation of Single Responsibility Principle as core)
  • Quicker turnaround deployment and go to market.

Reference Architectures

Looking for Serverless e-commerce technology owner for your team. Contact us http://fromdayone.work/contact-us

Read More
Development, Startup, Technology

Benefits of API First Approach to Product Development

Web APIs or RESTFul APIs are gaining lots of traction within development communities. The approach is helping Backend and Frontend developers to work in parallel. API designers work with product development teams and create API contract documents for both the team to kick start product development. Eventually, this reduces the cost of development and fast go to the market by reducing the risk of failure.

Benefits of API First Approach

  1. Backend, Frontend, and Mobile app development teams can work parallel.
  2. When all teams work in parallel it reduces cost for product development buy reducing ideal time and pre-defined contract documents.
  3. Time to the market reduces with this API-First approach.
  4. Products can expose their APIs to external Developers for third-party development.
  5. High Success Rate as API request-response is already frozen and development teams don’t see work repetition.
  6. API Unit Testing Framework can be introduced from the very beginning.

Available Tools for API-First Approach

  1. Swagger.io https://swagger.io/
  2. Postman https://www.postman.com/
  3. apiray https://cloud.google.com/apigee
  4. Apigee https://cloud.google.com/apigee

Looking for API-First approach or API Design team. React us at hello@fromdayone.work

Read More