Uploaded August 2020 | Updated November 2026, 3 hours ago
This is a short video that provides information about the Field class in Java. This video was taken out of the 'Reflection in Java' course that was published in Udemy at bit.ly/3fS3q2B It is a small showcase for the premium professional training services we provide.
This is a short video that provides information about the Field class in Java. This video was taken out of the 'Reflection in Java' course that was published in Udemy at bit.ly/3fS3q2B It is a small showcase for the premium professional training services we provide.

![Effective Strategies for Microservices Decomposition and Architecture [Free Meetup]
Microservices decomposition is not about splitting an application into as many services as possible. It is about defining boundaries that allow teams to change software faster, deploy safely, own decisions, and scale only where necessary.
These slides present practical strategies for decomposing applications into microservices while avoiding the distributed coupling that often replaces a monolith. They explain how to identify service boundaries through business capabilities and subdomains, and why high cohesion and low coupling should guide every decomposition decision.
You will learn how service-owned data supports autonomy, why other services should not access a service’s internal tables, and how APIs, events, and read models support collaboration. The slides also introduce a practical test for service independence: can the service be deployed, tested, rolled back, monitored, and owned by one team without coordinating every change with others?
The presentation covers incremental migration using the Strangler Fig pattern: extract one capability at a time, redirect traffic gradually, preserve rollback options, and leave legacy functionality in place until it is safely replaced.
A practical decomposition process is presented: discover capabilities, users, workflows, and pain points; select a boundary candidate; validate cohesion, coupling, data ownership, and deployability; then extract incrementally and measure whether coordination has been reduced.
The final section highlights common anti-patterns, including technical-layer services, shared databases, nano-services, synchronous call chains, and boundaries that do not match team ownership. It concludes with the essential questions architects and development teams should ask before extracting a service.
You can find more info about the meetup at https://www.meetup.com/lifemichael/events/315133312
You can find the post that was published about this meetup at https://lifemichael.com/en/microservices-decomposition-strategies-that-work-highlights-from-our-latest-meetup/
You can find the slides at https://www.slideshare.net/slideshow/effective-strategies-for-microservices-decomposition-and-architecture/288998744
#microservices #architecture Effective Strategies for Microservices Decomposition and Architecture [Free Meetup]](https://i.ytimg.com/vi/wLaeGoxuu1E/mqdefault.jpg)
![Coroutines in Kotlin [Free Meetup]
This video captures the meetup we had on September 10th, 2024. That meetup focused on the Coroutines in Kotlin. You can find more information about that meetup at https://www.meetup.com/lifemichael/events/301540171/
If you still havent joined the life michael meetup group, do it now and join us at https://www.meetup.com/lifemichael.
You can find the slides at https://www.slideshare.net/slideshow/introduction-to-coroutines-in-kotlin-free-meetup/271696343 Coroutines in Kotlin [Free Meetup]](https://i.ytimg.com/vi/wi9XhAX1cXo/mqdefault.jpg)







