How did people in their sane minds managed to conclude Ronaldo was the problem even after they heard him say all these about Manchester United?
His mentality must’ve been bigger than the entire system.
Nyaika 256, Saabaphotozi!
Videographer of all videographers.
The platinum kamanda of lens.
The 1st contributor to the national coffers.
1st of his name.
1st of his talent.
The P in Patriotism.
We Stan a King 👊
#FfeBanno@nyaika256#DevelopingUgandaTogether
@Adam_Karpiak I got strung along for a year by a major org in DC. Interviewed 3 times & sent them notes & ideas. Never heard if they made a hire until an old boss over lunch told me she met the hire. He was coming to her to establish collaborations that were part of my suggestion note plans.
WATCH: In 2003, Pr George Okudi was crowned the “Best East African Male Artist” and “The Best African Male Artist” by the Kora Awards in South Africa for his mega hit single “wipolo”. #tbt
Transitioning from a monolithic architecture to a microservices approach is no joke.
Without the right approach, you can end up in big trouble.
One of the safest ways to manage the migration is the Strangler Fig pattern.
What makes it so safe?
It is a gradual and non-disruptive method of transitioning from a monolithic system to microservices
This pattern lets you build new, modern microservices around your legacy monolith without taking a big-bang approach.
Here’s a simplified approach to how it works:
✅ Identify a module of the monolith that should be replaced with a microservice. Let’s call it Module A
✅ Then, place a Proxy between the Monolith and any clients.
✅ Gradually, all read calls to Module A will be routed to the new service via the Proxy.
✅ At this point, write calls for Module A functionalities will still continue to go to the monolith
✅ Over time, the write calls are also moved to the new microservice.
✅ All requests to the Monolith for Module A functionalities are stopped.
Embracing the Strangler Fig pattern in your migration to a microservices architecture is a no-brainer!
We gradually replace the functionality of the monolith until it can be shut down safely.
It paves the way for a smoother transition while keeping your business running without missing a beat.
===
That’s all for now!
If you enjoyed this post, don’t forget to:
- Destroy the LIKE button
- REPOST so that everyone can use this pattern to migrate from monolith to microservices
- BOOKMARK for future reference
- Follow me for more posts like this.