Here Comes Microservices

  Innovation   Knowledge Management   Lessons Learned   Strategy   ProjectsAtWork  

Microservices is an emerging approach to software development that breaks down complex applications into smaller components or processes. It embraces DevOps, complements agile, and can provide better scalability and resilience, among other benefits. But it also requires significant organizational change, and it isn’t a silver bullet; in fact, it can make a mess. Is it for you?

A software project today begins by selecting a technology stack such as Java, .NET or Ruby on Rails, followed by working on the database design, creating the infrastructure and then ramping up the right team. A detailed six-to-12 month plan is made as soon as the scope of the project is frozen — and now it’s time to start cranking code. But ask yourself:

1. What if you chose the wrong technology stack and only realized it after drowning six to eight months of development resources and time?
2. What happens if the key members of the team leave the company and take all the knowledge with them, leaving the rest of the team bewildered?
3. Have knowledge-transfer sessions ever worked?
4. What happens when the code has been launched in production and you realize that a major bug has been released?
5. What happens when the code is not scaling and the productivity is reducing by the day because the system has become too large to maintain and manage?
6. How do you handle technology stack upgrades a …

Please log in or sign up below to read the rest of the article.