<commit_before>---
layout: post
cover: 'assets/images/future-technologies.jpg'
title: Intro on Migrating to Microservices
date:   2017-02-14 05:00:00
tags: technologies
subclass: 'post tag-content tag-technologies'
categories: 'jt'
navigation: True
logo: 'assets/images/logo.png'
---

## Why Microservices?

This is an obvious question raised when applications or companies move to a microservices approach. There is a massive use case for the migration to microservices. The perfect time is you are at a scale or a place in your application's life cycle where you cannot iterate fast enough on top of your monolithic application. There are so many more resources out there on when or why to switch to this architecture it's not really worth "beating a dead horse" on the subject.

#### Technologies to Migrate With?

You might be wondering where to start and what approach to take -- if you have the luxury to migrate and refactor everything without a time constraint you're lucky! Majority of us don't have that luxury and really don't have the full buy in from our management or superiors to even "fix" our already working application. Invest in your products and invest in the future of your products is all I can say. This means containers and efficiency. Containers are here.. and here to stay. When I say that majority of companies or teams are just dabbling in containers and what to do with Docker or Rkt ("Rocket" -- a CoreOS product) it's understandable but **invest** in modern technologies. Invest in yourselves and your application's future start getting up to speed with containers it is so simple to spin up applications with these to proof them for teams/management. The ease of use to manage and bundle up applications is a major selling point! 

#### After Approval

Uh-oh... Now what right? You need a team to fully focus and sell out on these technologies. Regardless of the learning curve you will probably face when moving to containers and orchestration tools you will make it through it! The best things in life aren't always the easiest things to come by -- but a team focused on the future of the application and in turn the company's future success. 

![team](./../assets/images/small-team.jpg){:class="img-responsive"}<commit_msg>new title<commit_after>---
layout: post
cover: 'assets/images/future-technologies.jpg'
title: Introduction on Migrating to Microservices
date:   2017-02-14 05:00:00
tags: technologies
subclass: 'post tag-content tag-technologies'
categories: 'jt'
navigation: True
logo: 'assets/images/logo.png'
---

## Why Microservices?

This is an obvious question raised when applications or companies move to a microservices approach. There is a massive use case for the migration to microservices. The perfect time is you are at a scale or a place in your application's life cycle where you cannot iterate fast enough on top of your monolithic application. There are so many more resources out there on when or why to switch to this architecture it's not really worth "beating a dead horse" on the subject.

#### Technologies to Migrate With?

You might be wondering where to start and what approach to take -- if you have the luxury to migrate and refactor everything without a time constraint you're lucky! Majority of us don't have that luxury and really don't have the full buy in from our management or superiors to even "fix" our already working application. Invest in your products and invest in the future of your products is all I can say. This means containers and efficiency. Containers are here.. and here to stay. When I say that majority of companies or teams are just dabbling in containers and what to do with Docker or Rkt ("Rocket" -- a CoreOS product) it's understandable but **invest** in modern technologies. Invest in yourselves and your application's future start getting up to speed with containers it is so simple to spin up applications with these to proof them for teams/management. The ease of use to manage and bundle up applications is a major selling point! 

#### After Approval

Uh-oh... Now what right? You need a team to fully focus and sell out on these technologies. Regardless of the learning curve you will probably face when moving to containers and orchestration tools you will make it through it! The best things in life aren't always the easiest things to come by -- but a team focused on the future of the application and in turn the company's future success. 

![team](./../assets/images/small-team.jpg){:class="img-responsive"}
{'fraction_non_alphanumeric': 0.0539703605397036, 'fraction_numerical': 0.0061933200619332, 'mean_word_length': 4.409090909090909, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1077232', 'n_tokens_mistral': 1107, 'n_tokens_neox': 1032, 'n_words': 698}