Common questions about microservices
Adopting cloud native application development brings daunting questions to the cost benefits associated with an earlier era of cloud computing and the more recent promise of quicker deployment schedules. What should we do with our existing workloads running on premises? How should begin building cloud natively? What parts of existing apps should we migrate to the cloud?
Answering these questions clarifies a path to meeting and possibly anticipating customer needs. Along the way are choices of what compute services to use and when, with a view to coordinating all choices with the best practices of using a microservices app architecture.
Microservices architectures for building new cloud native apps
By reducing the components that deliver a user experience into small, modular services that are independently deployed and operated, microservices minimize the need for communication and collaboration across different development teams, promoting faster iterations wherever needed.
Microservices architectures for moving existing workloads to the cloud
Because many companies don’t have the advantage of building greenfield cloud-native applications like many startups do, the first step is to map out the steps of refactoring an existing monolith. Using a microservices approach along with DevOps tools and practices means pinpointing a very crucial problem — what’s hindering your Devops?
Learn how an online retailer identified DevOps hindrances and refactored a monolith in order to learn more about customers and quickly update new features.
To continue mapping out the next steps of cloud native development, join IBM STSM Gang Chen and Rick Osowski, and IBM CTO Roland Barcia in a discussion of the important aspects of microservices by focusing on a specific cloud enhanced and cloud native microservice reference applications.
What you’ll learn:
How development teams work faster
How customer requests power DevOps processes
How to deploy an app on a managed Kubernetes service