Tigera Provides Amazon With EKS Anywhere Users Choice to Use Calico for Container Networking and Security compsmag.com - get the latest breaking news, showbiz & celebrity photos, sport news & rumours, viral videos and top stories from compsmag.com Daily Mail and Mail on Sunday newspapers.
Posted on February 15, 2021 By Lars Larsson
Guest post originally published on Elastisys’s blog by Lars Larsson, Senior Cloud Architect and Branch Manager at
Elastisys
All companies that use cloud services do so for a reason. But those reasons may change. Whether motivated by the need for a multi-cloud strategy, expenditure minimization, legislative or regulatory demands, or simply to get closer to end users, many organizations find themselves migrating from one cloud to another. Cloud-to-cloud migration for a non-trivial application contains a lot of unknown unknowns. This causes stress and uncertainty for a CTO. To help shed some light based on years of experience in the field, we have asked senior cloud architect Lars Larsson at Elastisys, to list some of these issues.
Key Takeaways
Although we can find case studies about microservices migrations, there are still a lot of companies in the industry that haven’t touched the microservices strategy yet.
The current microservices approaches are more complex than they used to be. We build more complex systems, with a more complex architecture, so we have a more complex landscape and a deeper learning curve as consequence.
Monitoring and tracing microservices are some of the biggest challenges, besides its complexity.
The event-driven architecture is a great way to build microservices, especially in terms of communication between different services.
Wes Reisz moderated an InfoQ Live roundtable on the impact of microservices, dealing with operational complexity, and alternatives to the microservices model. The participants were Leif Beaton (NGINX senior solutions architect), Yan Cui (independent AWS and serverless consultant), and Nicky Wrightson (Skyscanner principal engineer).