The core building blocks of DevOps in Microservices

  • Continuous Integration
  • Continuous Deployment
  • Scaling
  • Metrics
  • Monitoring

Continuous Integration

  • The primary goal of CI is to keep everyone in sync with each other(Developer’s code)
  • CI servers can detect if the code has been committed, can check the code, compile, and test it as well
  • CI also builds the artifact(s) that are used for further validation like the deployment of a running service to run tests against it
  • Ideally, we should build these artifacts only once and use them across all the series of deployment of a single version of code
  • The leading open-source automation server today is Jenkins. This server provides hundreds of plugins to support building, deployment, and automation of any project

Continuous Deployment

  • In this approach, the application will be released to the production environment in short cycles, ensuring that the latest changes can be released at any time, reliably
  • It aims at building, testing, and releasing applications with greater speed and in better frequency
  • CD helps to reduce the cost and time and the risk of delivering the changes by allowing for more incremental updates to be implemented on the applications in the production environment
  • A simple, straightforward, and repeatable deployment process is important for continuous delivery.

Scaling

  • Maintain performance — This includes adding more resources to meet the performance targets of the application
  • Control costs — This is the process of automatically removing unutilized resources and avoiding overspending
  • Simplify scaling — This involves the discovery of scalable resources and building a scaling plan in a limited number of steps of execution
  • Predictive Scaling — Use historical load metrics to learn about an application’s traffic patterns and proactively scale resources in advance in order to meet the requirements

Metrics

  • The metrics used need to ensure the visibility of user actions for all services
  • Changes must be tracked on an individual level of services and for a wider number of systems across services
  • Track the number of requests that are served in a second by our services
  • Track the number of requests that fail in a second
  • Track the time that each of this service is taking to complete

Monitoring

  • We should be able to monitor the application logs, alarms, and other parameters
  • Set alarms on any of your metrics
  • Monitor Application logs
  • Dashboards can be created to monitor all the AWS resources in a single location
  • Should deliver a real-time stream of system events that describe changes in the Cloud Service resources

Summary

--

--

--

WalkingTree is an IT software and service provider recognized for its passion for technology.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Web Image Optimization: Compress, WebP or both?

Logging in Action with Fluentd, Kubernetes and more is finally available in print and…

Logging In Action Cover

How to Reset Zigo Eon 73i

reset my phone

http://twitter.com/SQLstream/status/824676427895222273

Why the Dinosaurs will be extinct in next decade….

Run the Parch & Posey DB Locally in Postgres

pgAdmin View Tables 1

How quick coding slows down productivity —A talk about maintainability

FUN COMMANDS IN LINUX 😆

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
WalkingTree Technologies

WalkingTree Technologies

WalkingTree is an IT software and service provider recognized for its passion for technology.

More from Medium

In-Memory API Deployment

YAML Ain’t Markup Language

Git/GitLab, How to upload your first project

7 Useful technologies to know as a Software Developer to catch errors and security risks before and…