Go在持续交付中的实践

MicroServiceandContinuousDelivery 郭峰@DaoCloud Let’s Imagine that you are build an online store OrderCustomerItem PaymentDashboardCartReportRecommendMonitoringCommentsSupply IntimidateDevelopers ObstacletoFrequentDevelopment •Needtoredeployeverythingforanewfeature •Interruptslongrunningbackgroundjobs •Increasingriskoffailure •Updateswillhappenlessoften–reallylongQAcycles OverloadsYourIDEandContainer Slowdowntheloop Requirelong-termcommitmenttoatechstack Smaller,simplerapps •Easytounderstandanddevelop •Lessdependences •Fastertobuildanddeploy •Even,Failurefaster BestTechnologyforEachService Cdudkno
Cdoknx
Rb`kd
ThereareDrawbacks ComplexitiesonCdudkno
Sdrs
@ChrsqhatsdcRxrsdl
Cdoknx
AutomationisImplicit ContinuousIntegration ContinuousIntegrationtoContinuousDelivery ContinuousDelivery?ContinuousDiverse! That’sAll? I’m handing >ckets for running apps! •Node.js•Python •Ruby •Golang•Java •PHP •…  Duang,Duang… “Works for me” “Can’t you reproduce” “Upgrade to 1.2.5‐xx” “I would appreciate if you could test b/w 3 and 4 am” “So to trigger the bug you have to install X and Y then configure A, B and C, then download the extra file, put it in this directory.  HowDockerHelps Docker&MicroService Develop simplest possible solu>on  Configura>on is a run>me constraint  DevNot extra‐extra‐complex applica>on new WebServer().start(8080);Manage hardware / infrastructure  OpsMonitoring / backups Not appsimplementa>ondetails UnifiedIntegration ReproducibleDelivery DockerizedApps TheLandscapewithContainers Q&A