Hi there! How are you? Have you received my email? I am waiting for your reply. Thank you.

Your presentation style demands that people read the screen. It would be better if you didn’t force this necessity

They're really not, they're nowhere near as complex.

Excellent video Gary! We had worked together in J. P. Morgan, Bothwell Street! and it was a great pleasure working with you. Believe me, every word that you speak is an learning experience in itself!

I really think transparent distribution is a trap. If two modules are inside a process and there's a function call, it's not the same thing as doing a network call with all the failures mode this imply. A distributed monolith can be great, but it should almost never just be a single monolith broken up and connected with "transparent" network.

🌟 "PromoSM"

Thank you for this presentation. Very informative.

Can you please share the promptflow zip file want to try it

where can i access the code from?

This architecture works when there's no relations between tenants or customers.

*PromoSM* 💘

For this to work the modules need to own specific sub-domains in the database, the entities in a module's sub-domain need to be private, e.g. separate schemas with database users that can only access one schema.

Best breed bundles will replace Monoliths.

The scalability argument for micro services has always been a little suspect to me. It’s not really universally true, and most of the time the scaling is not totally linear anyway. There will be a point at which there will be a bottleneck in the system as a whole.

First isn't this known as partitioning or single tenancy multi user/multi resources?

Question: I have a north American customers and European customers in different regions. In the micro services world I can have eventual consistency of data and close endpoints in each region. So micro services buys more scalability options.Obviously this is harder with a Monolith.. I feel it is naive to say later break out of the monolith something as a service without again ending up back in the boat where proper well designed micro services is important otherwise you end up back at old style SOA "distributed monolith". To be fair as you say, if you do not need micro services start with a well designed modular monolith. Our company went through the Java OGSI modular phase and it also ended in frustrated tears when a small bug or VM crash bring down the entire building... We ended back with teams rethinking their previous mistakes taking up micro services yet again. Back again at the advantage of micro services to isolate subsystems with if one fail its ok and recovery is possible without impacting other micro services.. Biggest sin in micro services we make is not decoupling the system enough with regards to data, data model aaaand communication since messages also couples if changes to them impact other services. Anyway, my question to people turning to Monoliths is: Are you sure you understand the difference between a Service Oriented Architecture and Micro Services? Are you implementing an SOA aka a distributed monolith and choking on the consequences? Or are you properly applying yourself to design your micro service architecture according to good practice.

i <3 microservices!!!!1111one

10:00 I lived the statement in my prev company. The other agile team started their project as ms, worked for 6 months and the output was nothing was working. In my team, although I was pretty sure that our app will be broken into ms"s in the future, we were very careful in that 6 month period, wrote the project following modular monolith approach. Then once the project has matured, we split it into multiple almost-independent services. Martin is definitely right. You cannot predict future, what kind of changes will be requested and will cause what kind of problems to you in the future.

Very well presented!

back in 2003 when I was in college I got into a course for clusters and making programs to run in clusters with an mpi library in c, I learned that moment that the cost of sending a message to another computer is extremely high that is so much better to run super optimized single threaded monoliths and partition by data than sending mini packages. micorservices was just used as a pretext to incorporate new technologies or to make work different technologies in the same project, like java for somethings, ruby for others, python for others, etc. Even in Erlang they suggest you to start with a monolith process and then fragment in processes as you progress and learn how your program performs. Then in my first work, it was a bank, and the whole site was divided in different applications, all connected by a single gateway application, the frontpage that had all the links to everything, this apps were written in ASP2, .Net1.1, .NET2 and Java, they all had the same assets and the site looked with a standard style and the only way you could knew you were changing of app is through the url. So it was a modular monolith.

Somewhere along the way we forgot to let software work for us and instead started working for software. The system is at the mercy of the business architecture (ala Conway). Why then do we not address the business architecture first and THEN look at the software solutions to solve for it?

in a large company hundreds of developers commit to the same repository of this module monolith. For sure you'll have some dependent, shared files made by junior\middle developers. you'll get +100 commits each day and rebase will become something like crazy conflicts resolving of <100 times. Otherwise you'll say - no rebase, lets merge, after that you'll have a crazy graph of branches. Once you'll try to scale, you'll need to buy super-pooper hardware just to create 2 instances. Once you need have some part as CPU dependent and another part as RAM dependant modules, you'll need to buy both: more RAM and latest processors. Once you need to pass some complex security certification, you'll got crazy, because have to fix all the modules, instead security and user services only. And direct interface calls makes high cohesion. No more, thanks.

All the things discussed were available and considered best practice in mid to late 2k's. Microservices never made sense, it was all marketing and PR. MacroServices is just SOA. old hat.

monolyth...microservice...modular monolyth... distributed monolyth... at this point I'm just going to claim the word hieroglyph for apps that you're not sure what they're supposed to be. everybody tailors their apps to their needs and services they provide. there's no such thing as good or bad until they've experienced PROD.

First of all, many thanks for the very informative great talk. I want to access the reference links in the presentation. Where can I download the presentation?

kzbin.info/www/bejne/fHq3e4CAn6aGi9U

This man has occupied 50% of the screen space, codes are hardly visible. 720p resolution makes it all the more worse. I spent over 30 minutes and learnt nothing.

Really good talk😊

Little bit hard to see sometimes but overall good explanation.

Thank you Dorrin ! where do i put a router if i am running APIs on Aws ApIGW backed by aws ECS.

can you provide the link of the google colab notebook for this code

I was struggling to understand my work setup for vue dev, then I found your video.. thank you so much

What if you’re deploying locally and not to azure web services?

This was an excellent talk!

I agree with the other comment. Every engineer needs to watch this. Micro services should be rarely used

I can't believe this video has only 1700~ views. It should be mandatory watching material for every single architectural astronaut and developer.

👏👏👏

I highly recommend this video to anyone who wants a verbose understanding of SSDT. All to often other videos glaze over or completely ignore important information in how these tools function.

Thank you so much for this great topic - you have discussed it very well. How can I access this code?

Nice explanation... what about render 100 page for printing in chrome ?

This is a hidden gem. So far the best I have seen on Function programming in C#.

Excellent Topic ! pls share the sample code as well

Yeah, that's correct

I can not see anything

Has anyone got the PDF file from the speaker? When I visited their company's website, all I can download is a single chapter from the ebook and not the whole book itself.

How are you handling the Handlers using the MediatR pipeline, since MediatR uses transient scope for their handlers?

This moves me another step closer towards understanding the functional programming paradigm. Finally I understand the terms like: "Treat function as data" or "Higher-order function (function composition)". That gives us different level of abstracting "things" compared with traditional OOP interfaces which requires different mindset indeed. Great simple examples! Thanks! Well done!

yes ! i come in.

Are you interested in getting help and private lessons via email in exchange for a small donation to a charitable organization ? You may find my email address in the stackoverflow site under the profile for the "enet" user.

Are you interested in getting help and private lessons via email in exchange for a small donation to a charitable organization ? You may find my email address in the stackoverflow site under the profile for the "enet" user.