Many organizations want to implement some type of microservices strategy, commonly by way of containers. Running containers in development can create fast feedback cycles and gives developers additional autonomy while working, but how does this translate to running containers in production? In this webinar we will talk about the main drivers and challenges with containers, as well as the huge divide between running containers in development and operationalizing your application at scale and for production release.
21. They are an Abstraction
• Logical packaging of an application and it’s environment
• Light weight (run at kernel level)
• Portable
• Isolated
21Copyright/Confidential statement.
22. What are they NOT?
22Copyright/Confidential statement.
23. They are not:
• … Virtual Machines
• … meant to be stateful
• … a replacement for best practices
• … a silver bullet
23Copyright/Confidential statement.
24. How do we go from Dev to Prod?
24Copyright/Confidential statement.
27. Create your artifact
• Describe the image in code (ie: Dockerfile)
• Build the image
• Store it (preferably in a registry)
27Copyright/Confidential statement.
33. Describe your Service
• Declare the expected state of your service as code
• The orchestration framework will handle:
• Deployment
• Health
• Scaling
33Copyright/Confidential statement.
37. Monitor Nodes AND Containers
• Gather the standard metrics on the nodes (disk/cpu/mem/network)
• Gather similar stats on the containers.
• Gather application stats
• Utilize a log aggregator
• Alert on important things
37Copyright/Confidential statement.
39. Monoliths are poor containerization candidates
• Containers are better for an SOA or Microservices
• Not a silver bullet
39Copyright/Confidential statement.
40. Containers should be immutable!
• Do not package state or config with the image
• No localized data
• Expect your containers to come and go
40Copyright/Confidential statement.