未加星标

Go from Node.js app to microservices with MONOLITHSPL/T

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二05 | 时间 2017 | 作者 红领巾 ] 0人收藏点击收藏

I've been working a lot with microservices in the past couple of years. It is during this time that I found how many issues can arise from putting an accent on delivery while disregarding architecture.

This is why I decided to create MONOLITHSPL/T .

I want to help businesses migrate their monolithic Node.js applications to a microservices architecture, improve the quality of their products as well as their overall delivery. My goal is to provide clear, actionable steps, to move away from poor architectural decisions made under pressure.

Through MONOLITHSPL/T , I will provide microservices migration strategies, driven only by your business goals. I will be putting all the knowledge and experience I accumulated over the past years into the service of businesses struggling with monolithic Node.js application architectures.

To get notified about the launch subscribe to the pre-launch list . The launch date is close and the list is very tight.

In a nutshell

If you feel like reading some marketing material, head over to monolithsplit.com and enjoy. On the other hand, if you're not that much of a reading fan, here's the core idea behind MONOLITHSPL/T and how I plan to help businesses implement microservices out of their Node.js monolith applications.

First, we need to talk. We will have one or two Skype calls to assess your current situation and more important, your goals. The whole strategy is built around and driven by your business goals. It will not be driven by software architects, developers, class hierarchies, etc. While highly valuable, their input will only be treated as reference material, used for guidance.

The architecture of your software ecosystem should represent your organisation and should be driven by it, not the other way around.

We will also create a list of people who could have valuable input regarding the past, present and future of your business. This may involve conducting interviews with people such as the head of the sales department, your software architect or the head of IT operations.

I will also go through your current codebase as well as your architecture/software documentation. I need a clear, unbiased ponit of view, before discussing with your technical staff.

This raw information will form the basis on which to identify your core needs. It is only after this information is gathered and processed that I will create a customized strategy for you to use in your microservices migration.

I want to make sure you are on track and making the best out of the strategy. I expect you and your team to have questions and need clarification and this is why I will follow up via email, periodically. The follow-up process consists of an email I will send out to you once every two weeks, for a period of up to six months.

For businesses requiring closer guidance I can also act as a sounding board. I will make myself available to a set of designated people who can contact me directly and I will grant them access to my knowledge and experience.

Everybody wins!

Yes, you and your business win! Remember that mobile app you postponed because it was too complicated to reuse your current data handling logic? Did you need to code extra functionality to pull the data independently, for the mobile app?

With microservices that problem doesn't exist!

You can mix and match services and quickly experiment with any new business idea that comes to mind! The fun part is that the impact (blast radius) is close to none. If the experiment fails, there's no harm done. It's as simple as updating a load balancer configuration and switching off a feature flag.

Some might say you migrate from monolith problems to microservices problems.

I agree, but in the long run, microservices are easier to maintain than monoliths. A monolith's increased complexity puts a lot of pressure on the team's morale also, not only on their capacity to deliver. For each risk others bring up when talking about microservices, there's also a 10-fold benefit.

Why not have problems that help your team grow and bond? Problems they actually want to solve, instead of dragging them from one release to the next!

Photo credits: Steve Jurvetson ― Beer Keg Blastoff!

P.S.In case you were wondering what is on the tip of the rocket, it's a doughnut! :yum:

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

主题: Node.jsSkype
分页:12
转载请注明
本文标题:Go from Node.js app to microservices with MONOLITHSPL/T
本站链接:http://www.codesec.net/view/531709.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(45)