Microservices management: While some might be happy to rise to the challenge, there are others that may cringe at the thought. And there's no reason microservices shouldn't make even the most experienced developer or application manager even just a little bit nervous; there are all sorts of management complexities and even security concerns that all add to the challenge of implementing and running microservices.
On top of that, there are plenty of decisions you'll have to make along the road. For instance, where does it make sense to run a microservices architecture rather than keeping things monolithic? How will the implementation of microservices affect the rest of your architecture, especially those parts still buried in legacy technology? Will you depend on containers or virtual machines (VMs)? And how will you ensure your microservice architecture will sustain for the long term?
These are all questions we aim to answer in this essential guide. Here you will find tips, feature articles, Q&As, videos and other content that will help you gain a better grasp on microservices management and all the baggage that comes with it. Dive in, and let our experts provide the insight that will help you move beyond the monolith and into microservices nirvana.
1Preparing your architecture-
Upfront microservices management considerations
More planning is always better. When it comes to microservices, there are a number of planning considerations that must be taken into account, such as what functions your microservices will or should support, what will happen to the other components of your possibly existing architecture and even deciding when microservices simply don't make sense.
In this section, we review the considerations that any developer or architect should take upfront during the shift to microservices -- particularly where and when it makes sense to fit microservices into your business plans. We also look at the top use cases for microservices, why mobile is a driver for microservices and what to expect in the aftermath of implementation.
In this Q&A, Randy Shoup of Stitch Fix talks about the 'reality' of microservices adoption and shares three telltale signs that your monolith has reached its limit. Continue Reading
Microservices development requires organizations to abandon the monolithic models they are familiar with. But what can an enterprise architecture gain from microservices? Continue Reading
A microservice approach offers agile and durable architecture. However, it's possible it might not be the best for your enterprise. George Lawton explains. Continue Reading
2Assembly and production-
Managing microservices development and deployment
You've done the planning, and now, it's time to develop and deploy your microservices. But will you achieve a resounding success, or will your initiative fall flat on its face?
Unfortunately, like many things, there is nothing necessarily automatic about managing microservices development and deployment. Application managers will be forced to learn new architectural and design patterns, learn about concepts like state and threading, decide what role VMs or containers will play and find a platform that takes the headache out of development and deployment.
In this section of the guide, we present content from our experts that takes a head-on look at the challenges of microservices development and deployment. Read on, and discover the problems that all developers and architects face when it comes to microservices, the critical concepts you need to understand, how to choose the right technology and tools and platforms that will help streamline the development and deployment process.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
3Operation and maintenance-
Post-deployment considerations and practices
When it comes to managing microservices, deployment is hardly the end of the road. Once your microservices roam free, there's still plenty of dirty work to be done in order to keep things running smoothly.
For instance, many organizations will need to continue running their microservices alongside legacy technologies and architectures, like service-oriented architecture (SOA). Governance will need to be put in place in order to consistently apply business logic to services and keep them secure. And certain architectural practices will need to be put into place to ensure that you and those who come after you can keep your microservices architecture up and running without major headaches.
The content in this section will help you learn more about maintaining the productivity, usability, security and sustainability of your microservices architecture and the services running within it. Our experts take an in-depth look at the post-deployment issues you can expect to arise -- all to help you make the most of your distributed architecture.
Automated continuous integration and software testing are musts for businesses and 'Jenkins refugees' breaking into microservices and containers, CircleCI's CEO says. Continue Reading
4Terms and phrases-
Glossary of microservices-related definitions
When it comes to talking about microservices management, knowing the terminology can help. In this section, we take a deep view of the meaning behind some of the common terms associated with microsersvices and with software architecture management in general.