Open APIs

Hi - What are micro services & how do they differ from SOA, ESB, API Management. Any Thoughts & experiences?

------------------------------
Mohammad Hasan Ayaz
Telenor Pakistan
------------------------------

Microservices is the new Reality .

Please find below the comparison on how its different from the rest

Microservices, SOA, and APIs: Friends or enemies?

Ibm		remove preview
Microservices, SOA, and APIs: Friends or enemies? Comparing a microservices architecture and service-oriented architecture (SOA) is a sensitive topic and often cause for a swift source of disagreement. This article examines where these controversies stem from and considers how best to resolve them. It then looks forward to see how these concepts are combining with those of API management to enable more agile, decentralized, and resilient enterprise architectures. View this on Ibm >

------------------------------
Umer Shahbaz
Telenor Pakistan
------------------------------

Hi everyone, I want to know if TMForum has an official definition or statement about microservices. Thank you!

------------------------------
Maria Eugenia Armijo Marchant
CableVision, SA
------------------------------

Original Message:
Sent: 02-03-2017 01:35
From: Umer Shahbaz
Subject: Microservices - Myth or Reality

Microservices is the new Reality .

Please find below the comparison on how its different from the rest

Microservices, SOA, and APIs: Friends or enemies?

Ibm		remove preview
Microservices, SOA, and APIs: Friends or enemies? Comparing a microservices architecture and service-oriented architecture (SOA) is a sensitive topic and often cause for a swift source of disagreement. This article examines where these controversies stem from and considers how best to resolve them. It then looks forward to see how these concepts are combining with those of API management to enable more agile, decentralized, and resilient enterprise architectures. View this on Ibm >

------------------------------
Umer Shahbaz
Telenor Pakistan
------------------------------

Hi,

like in most of the cases, Martin has a good view on this topics.
I suggest you give Microservices

martinfowler.com		remove preview
Microservices "Microservices" - yet another new term on the crowded streets of software architecture. Although our natural inclination is to pass such things by with a contemptuous glance, this bit of terminology describes a style of software systems that we are finding more and more appealing. View this on martinfowler.com >

a read.

So there are different takes on what Microservices are. My take is that it is not conflicting with SOA, but putting it on the next level by applying more constrains on how services are modelled and - even more important - how they are implemented.
 We made experiences with Microservices already and I'm happy to share those too.

Kind Regards
Stefan Christoph

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group
------------------------------

@Stefan Can you share your experiences so far.

------------------------------
Puneet Dhawan
Saudi Telecom Company
------------------------------

Original Message:
Sent: 02-03-2017 04:15
From: Stefan Christoph
Subject: Microservices - Myth or Reality

Hi,

like in most of the cases, Martin has a good view on this topics.
I suggest you give Microservices

martinfowler.com		remove preview
Microservices "Microservices" - yet another new term on the crowded streets of software architecture. Although our natural inclination is to pass such things by with a contemptuous glance, this bit of terminology describes a style of software systems that we are finding more and more appealing. View this on martinfowler.com >

a read.

So there are different takes on what Microservices are. My take is that it is not conflicting with SOA, but putting it on the next level by applying more constrains on how services are modelled and - even more important - how they are implemented.
 We made experiences with Microservices already and I'm happy to share those too.

Kind Regards
Stefan Christoph

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group
------------------------------

sure thing - what are you interested in?
Shall we setup a call to discuss this=

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group
------------------------------

Original Message:
Sent: 02-05-2017 01:20
From: Puneet Dhawan
Subject: Microservices - Myth or Reality

@Stefan Can you share your experiences so far.

------------------------------
Puneet Dhawan
Saudi Telecom Company
------------------------------

Hi,

I build over the years some monolithic applications, SOA and microservices. Microservices are definitely a reality and the way to go in my opinion.
The main difference I have noticed between the all different approaches to architecting software and microservices is that microservices take longer to develop: it's not just anymore a function call via Inversion of Control (to follow best practices), but you add an API layer in front of that function, so it's added code for the caller and the called. It also adds complexity in terms of the transport layer you are using.
HTTP REST is great, but even on internal networks, you need to handle retries, or asynchronousity.
Message queues (like kafka, rabbit MQ), scale really well, have guaranteed delivery features, but are a bit harder to implement.
You could even try an ESB, although I think these are a dead idea now.

That being said, whilst the initial developing time is increased (I would say by 50% in worst case scenarios), the maintenance time is drastically reduced by over 400% in my experience. Iterations are easy, agile scrum fits well, with a good application scaling strategy (like consul + zuul) you can only duplicate the services which require it, rather than your whole vertical slice. Adding new (significant) features is a breeze: Add a new service, you are not messing up with old code, potentially introducing bugs or breaking it (even with a good 95% unit test coverage). In short once you have gone through the pains of creating your first microservice stack, ironed out the continuous development, continuous integration, the transport layer resilience etc... everything else become so much more easier, and cheaper. You also have the freedom to use the best programming language for the job. Java Spring can talk to golang services, or even some python running some deep learning algorithms. 

If you have any specific questions or technology suggestions, let me know.

------------------------------
Julien
------------------------------

Original Message:
Sent: 02-14-2017 13:02
From: Stefan Christoph
Subject: Microservices - Myth or Reality

sure thing - what are you interested in?
Shall we setup a call to discuss this=

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group
------------------------------


Original Message:
Sent: 02-05-2017 01:20
From: Puneet Dhawan
Subject: Microservices - Myth or Reality

@Stefan Can you share your experiences so far.

------------------------------
Puneet Dhawan
Saudi Telecom Company
------------------------------

You might consider the Backends For Frontends pattern to start with Microservices. We've used BFFs to build new APIs for Frontends while Backend services are still offered by SOA, ESB or legacy monoliths.

Sam Newman - Backends For Frontends

Samnewman		remove preview
Sam Newman - Backends For Frontends Backends For Frontends solve a pressing concern for mobile development when using microservices. In addition they provide a compelling alternative to the general-purpose API backend, and many teams make use of them for purposes other than just mobile development. View this on Samnewman >

------------------------------
Dennis Kieselhorst
------------------------------

Original Message:
Sent: 02-20-2017 02:09
From: Julien Frisquet
Subject: Microservices - Myth or Reality

Hi,

I build over the years some monolithic applications, SOA and microservices. Microservices are definitely a reality and the way to go in my opinion.
The main difference I have noticed between the all different approaches to architecting software and microservices is that microservices take longer to develop: it's not just anymore a function call via Inversion of Control (to follow best practices), but you add an API layer in front of that function, so it's added code for the caller and the called. It also adds complexity in terms of the transport layer you are using.
HTTP REST is great, but even on internal networks, you need to handle retries, or asynchronousity.
Message queues (like kafka, rabbit MQ), scale really well, have guaranteed delivery features, but are a bit harder to implement.
You could even try an ESB, although I think these are a dead idea now.

That being said, whilst the initial developing time is increased (I would say by 50% in worst case scenarios), the maintenance time is drastically reduced by over 400% in my experience. Iterations are easy, agile scrum fits well, with a good application scaling strategy (like consul + zuul) you can only duplicate the services which require it, rather than your whole vertical slice. Adding new (significant) features is a breeze: Add a new service, you are not messing up with old code, potentially introducing bugs or breaking it (even with a good 95% unit test coverage). In short once you have gone through the pains of creating your first microservice stack, ironed out the continuous development, continuous integration, the transport layer resilience etc... everything else become so much more easier, and cheaper. You also have the freedom to use the best programming language for the job. Java Spring can talk to golang services, or even some python running some deep learning algorithms. 

If you have any specific questions or technology suggestions, let me know.

------------------------------
Julien
------------------------------


Original Message:
Sent: 02-14-2017 13:02
From: Stefan Christoph
Subject: Microservices - Myth or Reality

sure thing - what are you interested in?
Shall we setup a call to discuss this=

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group
------------------------------

Hi Julien

Congratulations and thanks for sharing your great feedback.  
I really liked the facts and challenges you mentioned upfront and the benefits of moving over to micro-services.

In this age of Agility and innovations, micro-services is the only way to go.

Regards

 

------------------------------
Manoj Saxena
Tata Communications Ltd
------------------------------

Original Message:
Sent: 02-20-2017 02:09
From: Julien Frisquet
Subject: Microservices - Myth or Reality

Hi,

I build over the years some monolithic applications, SOA and microservices. Microservices are definitely a reality and the way to go in my opinion.
The main difference I have noticed between the all different approaches to architecting software and microservices is that microservices take longer to develop: it's not just anymore a function call via Inversion of Control (to follow best practices), but you add an API layer in front of that function, so it's added code for the caller and the called. It also adds complexity in terms of the transport layer you are using.
HTTP REST is great, but even on internal networks, you need to handle retries, or asynchronousity.
Message queues (like kafka, rabbit MQ), scale really well, have guaranteed delivery features, but are a bit harder to implement.
You could even try an ESB, although I think these are a dead idea now.

That being said, whilst the initial developing time is increased (I would say by 50% in worst case scenarios), the maintenance time is drastically reduced by over 400% in my experience. Iterations are easy, agile scrum fits well, with a good application scaling strategy (like consul + zuul) you can only duplicate the services which require it, rather than your whole vertical slice. Adding new (significant) features is a breeze: Add a new service, you are not messing up with old code, potentially introducing bugs or breaking it (even with a good 95% unit test coverage). In short once you have gone through the pains of creating your first microservice stack, ironed out the continuous development, continuous integration, the transport layer resilience etc... everything else become so much more easier, and cheaper. You also have the freedom to use the best programming language for the job. Java Spring can talk to golang services, or even some python running some deep learning algorithms. 

If you have any specific questions or technology suggestions, let me know.

------------------------------
Julien
------------------------------


Original Message:
Sent: 02-14-2017 13:02
From: Stefan Christoph
Subject: Microservices - Myth or Reality

sure thing - what are you interested in?
Shall we setup a call to discuss this=

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group
------------------------------

Microservices are excelling approach if services are consumed by multiple clients like Mobile Apps, iPhone Siri, Amazon Alexa, Chat Bots etc

------------------------------
Ankur Doshi
Head of integration Platform,
MobileAware USA Inc.
------------------------------

Original Message:
Sent: 02-21-2017 10:03
From: Manoj Saxena
Subject: Microservices - Myth or Reality

Hi Julien

Congratulations and thanks for sharing your great feedback.  
I really liked the facts and challenges you mentioned upfront and the benefits of moving over to micro-services.

In this age of Agility and innovations, micro-services is the only way to go.

Regards

 

------------------------------
Manoj Saxena
Tata Communications Ltd
------------------------------


Original Message:
Sent: 02-20-2017 02:09
From: Julien Frisquet
Subject: Microservices - Myth or Reality

Hi,

I build over the years some monolithic applications, SOA and microservices. Microservices are definitely a reality and the way to go in my opinion.
The main difference I have noticed between the all different approaches to architecting software and microservices is that microservices take longer to develop: it's not just anymore a function call via Inversion of Control (to follow best practices), but you add an API layer in front of that function, so it's added code for the caller and the called. It also adds complexity in terms of the transport layer you are using.
HTTP REST is great, but even on internal networks, you need to handle retries, or asynchronousity.
Message queues (like kafka, rabbit MQ), scale really well, have guaranteed delivery features, but are a bit harder to implement.
You could even try an ESB, although I think these are a dead idea now.

That being said, whilst the initial developing time is increased (I would say by 50% in worst case scenarios), the maintenance time is drastically reduced by over 400% in my experience. Iterations are easy, agile scrum fits well, with a good application scaling strategy (like consul + zuul) you can only duplicate the services which require it, rather than your whole vertical slice. Adding new (significant) features is a breeze: Add a new service, you are not messing up with old code, potentially introducing bugs or breaking it (even with a good 95% unit test coverage). In short once you have gone through the pains of creating your first microservice stack, ironed out the continuous development, continuous integration, the transport layer resilience etc... everything else become so much more easier, and cheaper. You also have the freedom to use the best programming language for the job. Java Spring can talk to golang services, or even some python running some deep learning algorithms. 

If you have any specific questions or technology suggestions, let me know.

------------------------------
Julien
------------------------------


Original Message:
Sent: 02-14-2017 13:02
From: Stefan Christoph
Subject: Microservices - Myth or Reality

sure thing - what are you interested in?
Shall we setup a call to discuss this=

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group
------------------------------

Hi everyone!

Just to ilustrate how it can be done, I'm sharing my experience: I'm using Netflix OSS stack to implement the microservices. There are a lot of tecniques to deal with the problems like availability and retries like circuit breaking and client-side load balance. Our architecture consists in a segregated channel layer - where the backend-for-frontends resides - and in a microservices layer. I'm using Spring Cloud framework + Docker to implement the microservices but in near future I'm considering to have some of them implemented in Lagom Framework.

Cheers!

------------------------------
Rafael Stirling
Oi S/A
------------------------------

Original Message:
Sent: 02-21-2017 17:48
From: Ankur Doshi
Subject: Microservices - Myth or Reality

Microservices are excelling approach if services are consumed by multiple clients like Mobile Apps, iPhone Siri, Amazon Alexa, Chat Bots etc

------------------------------
Ankur Doshi
Head of integration Platform,
MobileAware USA Inc.
------------------------------


Original Message:
Sent: 02-21-2017 10:03
From: Manoj Saxena
Subject: Microservices - Myth or Reality

Hi Julien

Congratulations and thanks for sharing your great feedback.  
I really liked the facts and challenges you mentioned upfront and the benefits of moving over to micro-services.

In this age of Agility and innovations, micro-services is the only way to go.

Regards

 

------------------------------
Manoj Saxena
Tata Communications Ltd
------------------------------


Original Message:
Sent: 02-20-2017 02:09
From: Julien Frisquet
Subject: Microservices - Myth or Reality

Hi,

I build over the years some monolithic applications, SOA and microservices. Microservices are definitely a reality and the way to go in my opinion.
The main difference I have noticed between the all different approaches to architecting software and microservices is that microservices take longer to develop: it's not just anymore a function call via Inversion of Control (to follow best practices), but you add an API layer in front of that function, so it's added code for the caller and the called. It also adds complexity in terms of the transport layer you are using.
HTTP REST is great, but even on internal networks, you need to handle retries, or asynchronousity.
Message queues (like kafka, rabbit MQ), scale really well, have guaranteed delivery features, but are a bit harder to implement.
You could even try an ESB, although I think these are a dead idea now.

That being said, whilst the initial developing time is increased (I would say by 50% in worst case scenarios), the maintenance time is drastically reduced by over 400% in my experience. Iterations are easy, agile scrum fits well, with a good application scaling strategy (like consul + zuul) you can only duplicate the services which require it, rather than your whole vertical slice. Adding new (significant) features is a breeze: Add a new service, you are not messing up with old code, potentially introducing bugs or breaking it (even with a good 95% unit test coverage). In short once you have gone through the pains of creating your first microservice stack, ironed out the continuous development, continuous integration, the transport layer resilience etc... everything else become so much more easier, and cheaper. You also have the freedom to use the best programming language for the job. Java Spring can talk to golang services, or even some python running some deep learning algorithms. 

If you have any specific questions or technology suggestions, let me know.

------------------------------
Julien
------------------------------

Someone Asked for a  handy definition of Microservices.

This is one we like from Gartner

A microservice is a tightly scoped, strongly encapsulated, loosely coupled, independently deployable and independently scalable application component. Microservice architecture (MSA) is a design paradigm, based on a combination of SOA and domain-driven design (DDD), that enables ability and scalability.

The important part is 'independently deployable and independently scalable application component' Its the backend implementation that makes a micro service not the interface or how its exposed.

John-

------------------------------
John Basevi
Telefonica UK Limited
------------------------------

Original Message:
Sent: 03-06-2017 07:35
From: Rafael Stirling
Subject: Microservices - Myth or Reality

Hi everyone!

Just to ilustrate how it can be done, I'm sharing my experience: I'm using Netflix OSS stack to implement the microservices. There are a lot of tecniques to deal with the problems like availability and retries like circuit breaking and client-side load balance. Our architecture consists in a segregated channel layer - where the backend-for-frontends resides - and in a microservices layer. I'm using Spring Cloud framework + Docker to implement the microservices but in near future I'm considering to have some of them implemented in Lagom Framework.

Cheers!

------------------------------
Rafael Stirling
Oi S/A
------------------------------


Original Message:
Sent: 02-21-2017 17:48
From: Ankur Doshi
Subject: Microservices - Myth or Reality

Microservices are excelling approach if services are consumed by multiple clients like Mobile Apps, iPhone Siri, Amazon Alexa, Chat Bots etc

------------------------------
Ankur Doshi
Head of integration Platform,
MobileAware USA Inc.
------------------------------


Original Message:
Sent: 02-21-2017 10:03
From: Manoj Saxena
Subject: Microservices - Myth or Reality

Hi Julien

Congratulations and thanks for sharing your great feedback.  
I really liked the facts and challenges you mentioned upfront and the benefits of moving over to micro-services.

In this age of Agility and innovations, micro-services is the only way to go.

Regards

 

------------------------------
Manoj Saxena
Tata Communications Ltd
------------------------------


Original Message:
Sent: 02-20-2017 02:09
From: Julien Frisquet
Subject: Microservices - Myth or Reality

Hi,

I build over the years some monolithic applications, SOA and microservices. Microservices are definitely a reality and the way to go in my opinion.
The main difference I have noticed between the all different approaches to architecting software and microservices is that microservices take longer to develop: it's not just anymore a function call via Inversion of Control (to follow best practices), but you add an API layer in front of that function, so it's added code for the caller and the called. It also adds complexity in terms of the transport layer you are using.
HTTP REST is great, but even on internal networks, you need to handle retries, or asynchronousity.
Message queues (like kafka, rabbit MQ), scale really well, have guaranteed delivery features, but are a bit harder to implement.
You could even try an ESB, although I think these are a dead idea now.

That being said, whilst the initial developing time is increased (I would say by 50% in worst case scenarios), the maintenance time is drastically reduced by over 400% in my experience. Iterations are easy, agile scrum fits well, with a good application scaling strategy (like consul + zuul) you can only duplicate the services which require it, rather than your whole vertical slice. Adding new (significant) features is a breeze: Add a new service, you are not messing up with old code, potentially introducing bugs or breaking it (even with a good 95% unit test coverage). In short once you have gone through the pains of creating your first microservice stack, ironed out the continuous development, continuous integration, the transport layer resilience etc... everything else become so much more easier, and cheaper. You also have the freedom to use the best programming language for the job. Java Spring can talk to golang services, or even some python running some deep learning algorithms. 

If you have any specific questions or technology suggestions, let me know.

------------------------------
Julien
------------------------------

Thank you @John Basevi, I agree with that definition as the most precise and useful.

------------------------------
María Eugenia Armijo Marchant
CableVision, SA
------------------------------

Original Message:
Sent: 03-09-2017 03:09
From: John Basevi
Subject: Microservices - Myth or Reality

Someone Asked for a  handy definition of Microservices.

This is one we like from Gartner

A microservice is a tightly scoped, strongly encapsulated, loosely coupled, independently deployable and independently scalable application component. Microservice architecture (MSA) is a design paradigm, based on a combination of SOA and domain-driven design (DDD), that enables ability and scalability.

The important part is 'independently deployable and independently scalable application component' Its the backend implementation that makes a micro service not the interface or how its exposed.

John-

------------------------------
John Basevi
Telefonica UK Limited
------------------------------


Original Message:
Sent: 03-06-2017 07:35
From: Rafael Stirling
Subject: Microservices - Myth or Reality

Hi everyone!

Just to ilustrate how it can be done, I'm sharing my experience: I'm using Netflix OSS stack to implement the microservices. There are a lot of tecniques to deal with the problems like availability and retries like circuit breaking and client-side load balance. Our architecture consists in a segregated channel layer - where the backend-for-frontends resides - and in a microservices layer. I'm using Spring Cloud framework + Docker to implement the microservices but in near future I'm considering to have some of them implemented in Lagom Framework.

Cheers!

------------------------------
Rafael Stirling
Oi S/A
------------------------------


Original Message:
Sent: 02-21-2017 17:48
From: Ankur Doshi
Subject: Microservices - Myth or Reality

Microservices are excelling approach if services are consumed by multiple clients like Mobile Apps, iPhone Siri, Amazon Alexa, Chat Bots etc

------------------------------
Ankur Doshi
Head of integration Platform,
MobileAware USA Inc.
------------------------------


Original Message:
Sent: 02-21-2017 10:03
From: Manoj Saxena
Subject: Microservices - Myth or Reality

Hi Julien

Congratulations and thanks for sharing your great feedback.  
I really liked the facts and challenges you mentioned upfront and the benefits of moving over to micro-services.

In this age of Agility and innovations, micro-services is the only way to go.

Regards

 

------------------------------
Manoj Saxena
Tata Communications Ltd
------------------------------

The flexibility and modularity of microservices are what make them so appealing. They may be installed in containers, such as Docker, making scaling and management a breeze. Furthermore, it is an excellent fit for contemporary DevOps practises, allowing for a more agile development process. These services may be independently designed, deployed, and maintained, which is a game changer for developers. 

------------------------------
Micro services
TO BE VERIFIED
------------------------------

Original Message:
Sent: Feb 03, 2017 04:15
From: Stefan Christoph
Subject: Microservices - Myth or Reality

Hi,

like in most of the cases, Martin has a good view on this topics.
I suggest you give Microservices

martinfowler.com		remove preview
Microservices "Microservices" - yet another new term on the crowded streets of software architecture. Although our natural inclination is to pass such things by with a contemptuous glance, this bit of terminology describes a style of software systems that we are finding more and more appealing. View this on martinfowler.com >

a read.

So there are different takes on what Microservices are. My take is that it is not conflicting with SOA, but putting it on the next level by applying more constrains on how services are modelled and - even more important - how they are implemented.
 We made experiences with Microservices already and I'm happy to share those too.

Kind Regards
Stefan Christoph

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group
------------------------------

It's fun to have these kind of discussions in TM Forum!

I don't think TM Forum should take side in the monolith vs microservices debate. both approaches have merits and problems.
Recently Amazon Video have shown that they regretted their move to microservices and have reverted to a "monolith".

And many OSS and BSS vendors, members of TM Forum, still use a monolith while some have adopted micro services.

One of the ODA guides says that what matters most is that business capabilities are exposed via API. We are here to help businesses and their customers.

------------------------------
Kind regards,

Matthieu Hattab
Lyse Platform
------------------------------

Original Message:
Sent: May 31, 2023 14:59
From: Micro services
Subject: Microservices - Myth or Reality

The flexibility and modularity of microservices are what make them so appealing. They may be installed in containers, such as Docker, making scaling and management a breeze. Furthermore, it is an excellent fit for contemporary DevOps practises, allowing for a more agile development process. These services may be independently designed, deployed, and maintained, which is a game changer for developers. 

------------------------------
Micro services
TO BE VERIFIED
------------------------------


Original Message:
Sent: Feb 03, 2017 04:15
From: Stefan Christoph
Subject: Microservices - Myth or Reality

Hi,

like in most of the cases, Martin has a good view on this topics.
I suggest you give Microservices

martinfowler.com		remove preview
Microservices "Microservices" - yet another new term on the crowded streets of software architecture. Although our natural inclination is to pass such things by with a contemptuous glance, this bit of terminology describes a style of software systems that we are finding more and more appealing. View this on martinfowler.com >

a read.

So there are different takes on what Microservices are. My take is that it is not conflicting with SOA, but putting it on the next level by applying more constrains on how services are modelled and - even more important - how they are implemented.
 We made experiences with Microservices already and I'm happy to share those too.

Kind Regards
Stefan Christoph

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group

To be fair, Matthieu, there is an implication, if not explicitly stated, that an ODA component will likely be implemented as a microservice (or a coherent collection thereof). The ODA technical architecture (such as deployment within K8s, event based communications, etc.) "smells" like microservices :) .

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Original Message:
Sent: Jun 01, 2023 08:19
From: Matthieu Hattab
Subject: Microservices - Myth or Reality

It's fun to have these kind of discussions in TM Forum!

I don't think TM Forum should take side in the monolith vs microservices debate. both approaches have merits and problems.
Recently Amazon Video have shown that they regretted their move to microservices and have reverted to a "monolith".

And many OSS and BSS vendors, members of TM Forum, still use a monolith while some have adopted micro services.

One of the ODA guides says that what matters most is that business capabilities are exposed via API. We are here to help businesses and their customers.

------------------------------
Kind regards,

Matthieu Hattab
Lyse Platform
------------------------------


Original Message:
Sent: May 31, 2023 14:59
From: Micro services
Subject: Microservices - Myth or Reality

The flexibility and modularity of microservices are what make them so appealing. They may be installed in containers, such as Docker, making scaling and management a breeze. Furthermore, it is an excellent fit for contemporary DevOps practises, allowing for a more agile development process. These services may be independently designed, deployed, and maintained, which is a game changer for developers. 

------------------------------
Micro services
TO BE VERIFIED


Original Message:
Sent: Feb 03, 2017 04:15
From: Stefan Christoph
Subject: Microservices - Myth or Reality

Hi,

like in most of the cases, Martin has a good view on this topics.
I suggest you give Microservices

martinfowler.com		remove preview
Microservices "Microservices" - yet another new term on the crowded streets of software architecture. Although our natural inclination is to pass such things by with a contemptuous glance, this bit of terminology describes a style of software systems that we are finding more and more appealing. View this on martinfowler.com >

a read.

So there are different takes on what Microservices are. My take is that it is not conflicting with SOA, but putting it on the next level by applying more constrains on how services are modelled and - even more important - how they are implemented.
 We made experiences with Microservices already and I'm happy to share those too.

Kind Regards
Stefan Christoph

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group

I agree with Matthieu.

Microservice is an architecture style. 

Let us consider that if Mr.A and myself are into telecom provider business and have everything same(business type, business drivers, resources, budget, etc - assuming everything is same) then too our earnings/revenue/output/valuation may not be the same - reason being the implementation of the resources(human resources, tools, investments, etc). Similarly, implementation of Microservices is not a silver bullet!!!! It may benefit your business but sometimes it may not or migrating from Monolithic to Microservices may not give you good ROI.

Microservices, typically have few features to follow, again it depends on your implementation whether you want to go strictly by books or tailor them to match your needs to harvest maximum ROI. Let us discuss few of the features : 1. Single Responsibility - The service must implement single functionality/business sub domain ( Eg: Financial Transaction on a customer account / Issuing provisioning commands to customer device/etc). 2. Your application / microservice  must be resilient - Facing an exception and not returning the desired response/output is not a microservice feature, instead, it must be capable to handle such situations. 3. Various Microservice design patterns implementations - use the different patterns for your microservice. 4. Database - Single responsibility database, if you go by books :) , database schema based microservices also work fine. 

Best possible way out is understand your existing Architecture Landscape and then decide on the architecture type for implementation of ODA component / any new component in your Architecture Landscape. 

To answer the original question - SOA, use of ESB, API management using tools like APIGEE/SwaggerHub/etc are again ways with which you manage your Architecture Landscape and now you have Microservices added to this list - hope the details furnished helps.

------------------------------
______________________
Regards,
Sudeep Banerjee
------------------------------

Original Message:
Sent: Jun 01, 2023 08:19
From: Matthieu Hattab
Subject: Microservices - Myth or Reality

It's fun to have these kind of discussions in TM Forum!

I don't think TM Forum should take side in the monolith vs microservices debate. both approaches have merits and problems.
Recently Amazon Video have shown that they regretted their move to microservices and have reverted to a "monolith".

And many OSS and BSS vendors, members of TM Forum, still use a monolith while some have adopted micro services.

One of the ODA guides says that what matters most is that business capabilities are exposed via API. We are here to help businesses and their customers.

------------------------------
Kind regards,

Matthieu Hattab
Lyse Platform
------------------------------


Original Message:
Sent: May 31, 2023 14:59
From: Micro services
Subject: Microservices - Myth or Reality

The flexibility and modularity of microservices are what make them so appealing. They may be installed in containers, such as Docker, making scaling and management a breeze. Furthermore, it is an excellent fit for contemporary DevOps practises, allowing for a more agile development process. These services may be independently designed, deployed, and maintained, which is a game changer for developers. 

------------------------------
Micro services
TO BE VERIFIED


Original Message:
Sent: Feb 03, 2017 04:15
From: Stefan Christoph
Subject: Microservices - Myth or Reality

Hi,

like in most of the cases, Martin has a good view on this topics.
I suggest you give Microservices

martinfowler.com		remove preview
Microservices "Microservices" - yet another new term on the crowded streets of software architecture. Although our natural inclination is to pass such things by with a contemptuous glance, this bit of terminology describes a style of software systems that we are finding more and more appealing. View this on martinfowler.com >

a read.

So there are different takes on what Microservices are. My take is that it is not conflicting with SOA, but putting it on the next level by applying more constrains on how services are modelled and - even more important - how they are implemented.
 We made experiences with Microservices already and I'm happy to share those too.

Kind Regards
Stefan Christoph

------------------------------
Stefan Christoph
Principal Systems Architect
Vodafone Group

Hi,

Microservices is a good pattern but it's not just about scalability and implementation, it's also a different mindset of building application and system. With Microservices, you need to have a full agile style team organization and even the budget management need to be rethink. Topics like network, security, observability, Kubernetes is also a big critical part of this pattern because you have much more components so much more things to manage.

//----------------------------
// Francois Papon
// Yupiik
//----------------------------

Original Message:
Sent: Feb 02, 2017 02:02
From: Mohammad Hasan Ayaz
Subject: Microservices - Myth or Reality

Hi - What are micro services & how do they differ from SOA, ESB, API Management. Any Thoughts & experiences?

------------------------------
Mohammad Hasan Ayaz
Telenor Pakistan
------------------------------