• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Microservices in Action: What's new in microservices?

 
Ranch Hand
Posts: 144
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Microservices is still a trending buzzword among the companies and programmers.
But, what have changed in the microservices landscape, apart from deployment techniques, in the last 5 years?

About the last chapter "Building Microservice Teams". I think this is very important as there is NO many people talking about how to have effective teams for building microservices.
Question, when would you say that it's necessary to start talking about to change the team's dynamic to build microservices? In terms of the size or the type of the project/system?

I hope my questions are understandable
 
Author
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Jorge,

what have changed in the microservices landscape, apart from deployment techniques, in the last 5 years



I think the biggest change is maturity.  5 years ago, microservices were primarily an architectural approach where only big tech companies (Amazon, Netflix, Google...) had a known record of success; now, it's achievable, with much less cost, by companies operating at a much smaller scale.

As you say, deployment technique maturity - containers, schedulers, even FaaS - have played a huge part. Microservices aren't feasible if you can't deploy and operate many services independently and rapidly!

But I think it's also the availability of mature microservice frameworks in multiple languages; tracing and monitoring tools that can cope with the scale of microservice data; wider understanding of design techniques and failure modes in distributed systems...

when would you say that it's necessary to start talking about to change the team's dynamic to build microservices? In terms of the size or the type of the project/system?



The two things that change the dynamic the most are:

1. having more than one team building services
2. having multiple services in production - let's say, exceeding more services than engineers ;)

I think these are two crucial starting points to consider your team dynamic.  However, you might not see actual dysfunctions or reduced effectiveness until much later; so it's always good to change iteratively - adjust the behaviour, review how that works, and repeat - until you have a model that works well and drives a healthy culture in your team(s).
 
Jorge Ruiz-Aquino
Ranch Hand
Posts: 144
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you for your great answers.
I agree, all in software development matures. And 5 years is too much for a technology.

About microservice teams. You are right, it's always good to change iteratively. I would say adaptatively.
 
You've gotta fight it! Don't give in! Read this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic