These are chat archives for spring-cloud/spring-cloud

30th
Apr 2018
Prashant Ladha
@prashantladha
Apr 30 2018 01:18
with SCDF, do we have any example of reading a file and dump it in the database column ?
alfsender
@alfsender
Apr 30 2018 04:06
Hi All, I am integrating my application with other app using REST. API accepts JSON payload. this JSON payload varies for each request. so, i can't generate POJO classes and then covert them to json before sending requests. What will be best way to generate in such cases..
on option i am looking at is using thymeleaf templates, which creates json for me... but i would like to explore few more options before i settle with one. so, request all to share thoughts please. Thanks.
CH4:D
@chad_d_stud_twitter
Apr 30 2018 05:23
Does Feign support reactive communication?
vikrantch-hk
@vikrantch-hk
Apr 30 2018 10:34
@spencergibb can I use a non spring boot java client as discovery client while using eureka server for registry
Marcos Barbero
@marcosbarbero
Apr 30 2018 11:18
@vikrantch-hk what do you mean by that? Do you mean using spring-cloud-starter-eureka in a non-boot app or using netflix-eureka directly?
Prashant Ladha
@prashantladha
Apr 30 2018 11:59
@alfsender if you want to re-use the same API .... I think you will still need a generic POJO ... then in the Processor part . .you can handle them case-by-case basis....
vikrantch-hk
@vikrantch-hk
Apr 30 2018 12:01
@marcosbarbero I am using non spring boot application as discovery client so I woudn't be able to use spring-cloud there
Marcos Barbero
@marcosbarbero
Apr 30 2018 12:06
You actually can, it just requires a lot more steps. However, maybe it will be easier to use netflix-eureka library directly @vikrantch-hk
vikrantch-hk
@vikrantch-hk
Apr 30 2018 12:12
@marcosbarbero actually we want to add one of our spring web app as client adding spring cloud dependency creates too many conflicts there so want to avoid it. Do you have any example for non spring boot discovery client?
Marcos Barbero
@marcosbarbero
Apr 30 2018 12:14
I don't have it by now, in my current job there was a requirement to make it work for boot apps as well for non-boot apps, for that I created a wrapper for spring-cloud-started-eureka where I manually create the required beans and import the required auto config classes.
Before this version (wrapping spring-cloud-started-eureka) the non-boot apps were using netflix-eureka-client directly
it will also works and maybe it's an easier way to go
of course you won't have all the functionalities provided by spring-cloud implementation such as zone affinity, so the decision depends on your use case.
vikrantch-hk
@vikrantch-hk
Apr 30 2018 13:03
@marcosbarbero thanks I'll try netflix-eureka-client
Jon McEwen
@jonmcewen
Apr 30 2018 14:40
I've added spring-cloud-config to my app, and if there's any kind of error at startup it exits silently without logging an ERROR. What am I missing please?
This is with Spring Boot 2.0.1
Which also seems far less helpful than 1.x with startup problems
Jon McEwen
@jonmcewen
Apr 30 2018 14:46
I made some progress before by removing deprecated validation annotations and replacing them with javax ones
Is there separate logging config for the bootstrap phase?
Tyler Van Gorder
@tkvangorder
Apr 30 2018 15:18
@kaidowei We just recently refactored a legacy scheduler with similar requirements. Prior to any refactoring we were running many ETL "Tasks" via a scheduler + a task executor in a single JVM and that model does not scale well in an enterprise environment. For your use case, I would build each workflow as a spring cloud task, which end up being small, independent spring boot applications that startup, do some work, and then shutdown. You then use spring cloud data flow to register your applications (with either maven coordinates or docker coordinates) and the data flow server provides and API for launching those tasks. Finally, you can build a scheduling application that simply makes calls into the data flow server to launch your tasks. This is an overly simplified description of those technologies but if you have not explored using the data flow server for "task-driven" workflows...you should, it is amazing. For ETL workloads, I would recommend that you use Spring batch within each of your spring cloud task applications.