I still surprised what cloud function does. Looks llike every time I use it I create new endpoint. It potentially can cause harm like I open api endpoint I don't want to open. Another way It looks cool, but I can't customize with another http features like headers, params, token, methods, statuses and handlers. So many questions
This kind of programming (just write a function and it will work) doesn't work for me: if I write a function and it doesn't uppercase the input, where can I know where I am wrong? It seems that Spring hides too much information from me.
i think only glen can understand what they are speaking, i didnt understand what are they talking about clearly, they are not able to communicate well about the agenda, normal java developers cant even understand
Thanks Glenn and Oleg for the progressive approach to explain Spring Cloud Steams!
great explanation. been using spring cloud stream functions for quite some time. pretty cool
I still surprised what cloud function does. Looks llike every time I use it I create new endpoint. It potentially can cause harm like I open api endpoint I don't want to open. Another way It looks cool, but I can't customize with another http features like headers, params, token, methods, statuses and handlers. So many questions
can we integrate poller with some kind of distributed lock in case when we run multiple instances
This kind of programming (just write a function and it will work) doesn't work for me: if I write a function and it doesn't uppercase the input, where can I know where I am wrong? It seems that Spring hides too much information from me.
i think only glen can understand what they are speaking, i didnt understand what are they talking about clearly, they are not able to communicate well about the agenda, normal java developers cant even understand
Nice.
Jar according java functional interfaces
CreekProducer: Supplier
CreekTransformer: Function
CreekConsumer: Consumer