Because microservices and containers are Natural born“ A pair”, So use them together, It doesn't seem to be a problem. When we put this pair“ A heaven-made match” After putting into production system, You'll find out, With you IT
Foundation improvement, What's waiting for you is the rising cost. Is that right?-- Kevin Casey
Navigation in this article◈ 1, On deploying microservices and containerization, Trying to start from zero at the same time26%◈ 2, Start with a customer facing or critical business application39%◈ 3,
Introduced too much complexity before there was no right team52%◈ 4, Ignore important needs: automation75%◈ 5, as time goes on, Microservices are becoming more and more bloated85%
Compile and compile |
  author | Kevin Casey
  Translator | qhwdw
Micro service and container match naturally, But you need to avoid some common pitfalls.

Because microservices and containers are  Natural born“ A pair”[1], So use them together, It doesn't seem to be a problem. When we put this pair“ A heaven-made match” After putting into production system, You'll find out, With you IT
Foundation improvement, What's waiting for you is the rising cost. Is that right?

( Let's wait, When people laugh)

Yes, Unfortunately, This is not what you want. Although the combination of these two technologies is very powerful, however, Without good planning and adaptation, They don't perform very well. In the previous article, We sorted it out if you want to 
Use them what you should know[2]. however, These are common problems that organizations encounter when using microservices in containers.

Know these problems in advance, Can help you avoid these problems, Lay a solid foundation for your success.

The emergence of microservices and container technology is based on the needs of organizations, knowledge, Resources and more realistic requirements.Mac Browning say,“ The one they do most often [ error]
It's trying to think once‘ Settle’ everything”, He is DigitalOcean[3]  Engineering manager of.“ And the real problem is, What kind of containers and microservices should your company adopt.”

[ Try to explain microservices to your boss and colleagues? Read our primer how to explain microservices in a simple and clear way[4].]

Browning And others IT
The professionals shared what they met, Five pitfalls in using containerized microservices in an organization, Especially in the early stages of their production system life cycle. When microservices and containers need to be deployed in your organization, Understand this knowledge, It will help you evaluate microservices and containerized deployment strategies.

1, On deploying microservices and containerization, Trying to start from zero at the same time

If you're just starting to change from a complete single application, Or if your organization doesn't have enough knowledge on microservices and containerization, that, please remember: Microservices and containerization are not tied together, Not separately deployable. That means, You can use the technical expertise of your company's internal experts, Start by deploying one of them.Sungard
Availability Services]5[5]  Senior CTO architect Kevin McGrath
proposal, Build knowledge and skills for your team by first using containerization, Through container deployment of existing application or new application, Then migrate them to the microservice architecture, So we can finally feel their advantages.

say,“ Microservices want to run well, It takes years of iteration, This enables rapid deployment and migration”,“ If the organization cannot achieve rapid migration, It will be difficult to support microservices. Enable rapid migration, Containerization can help you, So you don't have to worry about overall business downtime”.

2, Start with a customer facing or critical business application

For organizations, A related trap is precisely from the container, Micro service, Or both: Before trying to conquer a lion in the jungle, You should conquer some small animals at the bottom of the food chain first, To gain some practical experience.

You can expect some mistakes in your study —— You want these errors to happen in customer facing business critical applications, still, Only on IT Or other low-risk applications visible to internal teams?

DigitalOcean Of Browning
say,“ If the whole ecosystem is new, To gain some experience in microservices and containers, that, Apply them first to areas with lower influence faces, Like your continuous integration system or internal tools, It could be a low-risk approach.” After you have gained experience in this field, Of course, these technologies will be applied to the production system that provides services for customers. And the reality is, No matter how well prepared you are, It's inevitable to encounter problems, therefore, It is necessary to formulate countermeasures for possible problems in advance.

3, Introduced too much complexity before there was no right team

Due to the flexibility of microservice architecture, It can create complex management requirements.

Act as Red Hat[6]  Technology enthusiasts,Gordon Haff[7]  Recently wrote,“ A coincidence OCI
The standard container runtime itself is good at managing individual containers, however, When you start using multiple containers and containerized apps, And decompose them into hundreds of nodes, Managing and orchestrating them will become extremely complex. Final, You will need to go back and group containers to provide services
—— such as, Cross container network, security, Measurement and control”.

Haff Hint,“ Fortunately,, Because containers are portable, also, The related management stack is also portable”.“ The matching technology appeared at this time, Like example Kubernetes[8] , Make this kind of
IT Requirements are simplified”( For more information, please refer to Haff Articles: Containerization brings 5 One advantage[1]).

in addition, You need the right team to do these things. If you already have DevOps shop[9], that, You might be better suited to this transformation. because, From the beginning, you have gathered talents with relevant skills.

Mike Kavis say,“ as time goes on, More and more services deployed, It will be very inconvenient to manage”, He is Cloud Technology Partners[10]
  Vice president and chief cloud architect of. He said,“ stay DevOps In the key process of, Ensure experts in all fields —— Development, test, security, Operation and so on ——
All involved, And in container based microservices, In building, deploy, Function, Collaboration on Security.”

4, Ignore important needs: automation

In addition to having a suitable team, Organizations that are successful in container based microservice deployment tend to“ Automate as much as possible” To solve the inherent complexity.

Carlos Sanchez say,“ Implementing distributed architecture is not easy, Some common challenges, Like data persistence, Journal, Troubleshooting, etc. It will become very complex in microservice architecture”, He is 
CloudBees[11]  Senior Software Engineer. By definition,Sanchez
Distributed architecture mentioned, As the business grows, It will become a huge and extremely heavy operation task.“ Proliferation of services and components, Will make operational automation a very strong demand”.Sanchez
Warning.“ Manual management will limit the size of the service”.

5, as time goes on, Microservices are becoming more and more bloated

It's not magic to run a service or software component in a container. however, That doesn't mean you must be using microservices.Manual Nedbal, ShieldX Networks
[12]  Of CTO, He warned.IT Professionals should ensure that, as time goes on, Microservices are still microservices.

say,“ as time goes on, Some software components accumulate a lot of code and features, Putting them in a container will produce micro services that are not needed, It's not going to bring the same benefits”, In other words,“ As the components grow, Engineers need to find the right time to break them down again”.


author:Kevin Casey[14]  Translator:qhwdw  Proofreading:wxy

This article is composed of LCTT  Original compilation,Linux China  Honor roll out
LCTT Translatorqhwdw ? ? ? ? Total translation:50  Contribution time:81 day

Recommended articles

< Slide left and right to view related articles >










Click on the picture. Input articles ID Or identification QR code direct

Please visit“ Original link” Get clickable in text links, Full size original drawing and related articles.