Neo4j - How KGs are shaping the future of Generative AI at AWS Summit London ...
Container cicd
1. Portability
Same Immutable Images. Run anywhere.
Flexibility
Create Modular Environments. Decompose Apps
Speed
Speeds up build and release cycle
Efficiency
Optimize resource utilization
Agility
2. Use Cases
• Consistent environment between Development & Production
• Service-Oriented Architectures / Microservices
• Short lived workflows
• Isolated environments for testing
3.
4.
5. Continuous delivery service for fast and reliable
application updates
Model and visualize your software release process
Builds, tests, and deploys your code every time there is a
code change
Supports manual approvals
Integrates with other AWS services and third-party tools
AWS CodePipeline
Containers gives us many of the abilities developers want:
Makes it easier to build & deploy things more rapidly, because the environment is the same. Build the container in dev, push to test, release to prod. This can also be useful for customers running hybrid environments.
Makes it easier to keep consistent environments for SOAs or Micro-Services. Also, many of these services aren’t very resource intensive, so you can place them together on one instance.
Sometimes customers have short-lived workflows that need to setup environments (e.g. queue systems, CI jobs, etc.), which doesn’t always map too well to EC2’s per-hour billing model. Docker can be one workaround, allowing them to push & pop containers on to the instance.
Can be useful for isolated execution when testing user code. E.g. Go Playground or similar.
