Big fan of Tim Berglund's talks, He doesn't dissapoint with another great one here: Starting from the Monolith- [3:46] , Re-integrating Challenge - [5:34] , Integrating Micoservices through a Database [7:39], Integrating MicroServices via RPC mechanisms [9:46], Event Driven Microservices [14:56], Kafka and its components [18:36] , Peeling Database Logical Layers[44:01] , Microservices as Inside-Out distributed DB [46:57]
Is this a disguised propaganda to keep building better monoliths and stay away from all this madness?? Is this even working in real life when your json schema changes? How to handle a simple error that prevents you to move forward in the log because your data is not consistent anymore...
I did not learn anything new or useful from this talk. After externalize the log, dont you need to build the table in order to create meaningful entity? dont you need to join/merge the entities to consume and serve meaningful information? dont you need to govern the consistent state of the information? Has not the database done all of them so well for you? I am pretty on this: if people can't build monoliths properly, microservices won't help. Neither Kafka.
I'm a big fan of the podcast and maybe this wasn't tailored to me. Just to simple and watered down. Maybe this is old and just posted recently. Still will upvote because it was well done.
So kafka (a distributed log) should be used as an ESB (enterprise service bus) to integrate/connect microservices? Why would kafka be a better fit than FuseESB or Mulesoft or Apache ServiceMix? Is it because most conventional/traditional ESBs don't have streaming APIs?
Před 4 lety
Datomic is that database to be shared between all services that could solve the problem described.
Big fan of Tim Berglund's talks, He doesn't dissapoint with another great one here:
Starting from the Monolith- [3:46] ,
Re-integrating Challenge - [5:34] ,
Integrating Micoservices through a Database [7:39],
Integrating MicroServices via RPC mechanisms [9:46],
Event Driven Microservices [14:56],
Kafka and its components [18:36] ,
Peeling Database Logical Layers[44:01] ,
Microservices as Inside-Out distributed DB [46:57]
The way Tim connects the dots together and delivers his idea is absolutely amazing! Great job!
Awesome talk.
I believe in the last 30 seconds is so much knowledge that the rest of uf will understand in years to come.
Is this a disguised propaganda to keep building better monoliths and stay away from all this madness?? Is this even working in real life when your json schema changes? How to handle a simple error that prevents you to move forward in the log because your data is not consistent anymore...
I did not learn anything new or useful from this talk. After externalize the log, dont you need to build the table in order to create meaningful entity? dont you need to join/merge the entities to consume and serve meaningful information? dont you need to govern the consistent state of the information? Has not the database done all of them so well for you? I am pretty on this: if people can't build monoliths properly, microservices won't help. Neither Kafka.
I'm a big fan of the podcast and maybe this wasn't tailored to me. Just to simple and watered down. Maybe this is old and just posted recently. Still will upvote because it was well done.
So kafka (a distributed log) should be used as an ESB (enterprise service bus) to integrate/connect microservices? Why would kafka be a better fit than FuseESB or Mulesoft or Apache ServiceMix? Is it because most conventional/traditional ESBs don't have streaming APIs?
Datomic is that database to be shared between all services that could solve the problem described.