Discussion about java chassis roadmap

we need to plan roadmap for the next stage i create below issues to trace what i think is important. please feel free to add your opinions/new isses/ and so on [SCB-719 ] automated integration testing support complex processes [SCB-748

Re: [DISCUSS] Service-Center Docker images version numbering

+1 >From a chassis user's perspective YangYongZheng <342906...@qq.com> 于2018年7月18日周三 上午10:43写道： > +1 > > Best Regards! > YangYongZheng > > -邮件原件- > 发件人: Kirin Wang [mailto:wangqilint...@gmail.com] > 发送时间: 2018年7月18日 10:32 > 收件人: dev@servicecomb.apache.org > 主题: Re: [DISCUSS]

Re: [DISCUSS]Simplify Dynamic Config (Apollo) Integration Test in Java Chassis

No, What I mean is that Apollo itself is complex. It have multiple components and uses eureka for registry/discovery. So it will take a long time for booting an Apollo instance for testing, which is the problem we are facing in our test cases. The other problem is that if used in production, it

Re: [DISCUSS]Simplify Dynamic Config (Apollo) Integration Test in Java Chassis

+1 to using this way to reduce load of integration testing. But I am also interested in what Yangbo mentioned, "apollo is too complex a system for our use case". My doubt is is there any way to reduce this complex, any user guide blog for it? Best Regards, --- Zen Lin