Migrating a Monolithic Application to Microservices (Cloud Next '19)

preview_player
Показать описание
Last year, Google Cloud’s Release Engineering team migrated a monolithic application into dynamic microservices. We leveraged Google Kubernetes Engine and Spring Cloud Kubernetes to make the migration seamless. In this talk, we will show you how we migrated to microservices using the right tools and approaches. We will also cover architecture concepts, using GKE, Cloud Pub/Sub, Cloud Datastore, Stackdriver, etc.

Watch more:

Speaker(s): Soeren Walls, Sergio Felix

Session ID: DEV105
product:Cloud - Containers - Google Kubernetes Engine (GKE),Cloud - Compute - App Engine,Cloud - Data Analytics - PubSub,Cloud - General; fullname:Sergio Felix,Soeren Walls; event: Google Cloud Next 2019; re_ty: Publish;
Рекомендации по теме
Комментарии
Автор

Very nice interesting explanation 👍, slids are pretty easy to understand with the story.

ismile
Автор

Although a challenging process, moving from monoliths to microservices is a rewarding journey especially once a business starts to see growth and success delivered by a refactored application system.

reazromen
Автор

i enjoyed the way you presented all topics here, thank you guys!.

juanpabloosorioalvarado
Автор

Thanks for your way to explanations both are awesome guys, I really enjoyed the session.

pavanagrari
Автор

Just goto 14:19 basically setup a proxy infront of your monolithic app and slowly separate functionality into microservices till everything is migrated

mwaikul
Автор

Liked the way it is presented. Good job guys.

chmaheshkrishna
Автор

it is very crisp and to the point presentation. Once catch however, earlier in presentation it is mentioned that it is easy to debug a monolith which is true but later in the presentation he mentioned that they were having hard time debugging their monolith????

IrfanAhmedShaikh
Автор

As was mentioned: "Migrate from the monolith to microservices". In the most of the cases it is impossible, especially for the large scale enterprise. Just cuz enterprise companies are not ready to pay for this, they are paying for the new functionality to be implemented. Such a migration is time, which should be paid. The only thing that is possible in this case is a complete modernization which is bought by enterprises in a couple of decades.

sergejsvisockis
Автор

Thanks guys, clear explanation of many aspects involved into the migration.

midclock
Автор

Can anyone help me understand how to segregate the bounded context of an object which is used across modules. For example, a mapping data between Shipping and Inventory. How do we access the data from 2 different databases?

leonardfrederick