# Microservices FAQ - [Should I Use A Microservices Architecture? What about the UI? π](https://www.jamesmichaelhickey.com/microservices-architecture/) - [medium.com: STOP!! You donβt need Microservices](https://medium.com/@ebin/stop-you-dont-need-microservices-dc732d70b3e0) - [contino.io: How to Make Enterprise Container Strategies That Last (Part One)](https://www.contino.io/insights/how-to-make-enterprise-container-strategies-that-last-part-one) - [medium.com: Your team might not need Kubernetes](https://medium.com/@alexellisuk/your-team-might-not-need-kubernetes-57240e8d554a) - [cybercoders.com: What Hiring Managers look for in a Full Stack Developer](https://www.cybercoders.com/insights/what-hiring-managers-look-for-in-a-full-stack-developer/) - [nginx.com: Introduction to Microservices πππ](https://www.nginx.com/blog/introduction-to-microservices/) - [Dzone: Programming Styles Compared: Spring Framework vis-a-vis Eclipse MicroProfile ππ](https://dzone.com/articles/programming-styles-spring-boot-vis-a-vis-with-ecli) ## Kubernetes Native - [developers.redhat.com: Why Kubernetes native instead of cloud native? π](https://developers.redhat.com/blog/2020/04/08/why-kubernetes-native-instead-of-cloud-native/) ## Migration Styles. Lift and Shift Cloud Migration Strategy - [From monolith to containers: How Verizon containerized legacy applications on OpenShift π](https://www.youtube.com/watch?v=Q6i0LK4vHsU): - Lift and shift is a cloud migration strategy that refers to removing workloads and tasks from one storage location and placing them in another, usually cloud-based, location. - Moving applications to the cloud can be challenging if you are unprepared. In fact, many businesses experience some level of migration failure because of poor planning. - The lift and shift migration style is one of the approaches that can help you transition to the cloud without the need to redesign applications or disrupt workflow operations. - It all starts with containerizing the applications using platforms like Docker and then moving entirely to a microservices architecture. ---