3 ms·
I really like the acronyml ( Plonk = Prometheus + Linux/Linkerd + OpenFaas + Nats + Kubenetes ) I miss some long-running ETL/dataflow pipeline-like service lik
by eb0la 7y ago
I really like the acronyml ( Plonk = Prometheus + Linux/Linkerd + OpenFaas + Nats + Kubenetes )
I miss some long-running ETL/dataflow pipeline-like service like Apache Beam or something similar.
The reason is I don't like to chain more than 3 cloud functions together because operations tend to be complex after that.
Instead I like to use something like Beam where I can _drain_ the data pipeline before stopping it.
- alexellisuk 7y agoThank you. What do you use for your microservices at work right now? PLONK is positioned as an answer for that as well as for functions when required.
- alexellisuk 7y agoI think this article shows how the two can co-exist as polymorphic deployments: https://www.openfaas.com/blog/asp-net-core/ https://www.openfaas.com/blog/asp-net-core/
- eb0la 7y agoOf course they can co-exist :-) ! I guess I should write am essay about _when_ one is better than the other... just to see FaaS catch up in short, short, time :-D
- eb0la 7y agoMostly containers with K8s and Istio. Works good but it's complex to start (for my taste). For data we still have VMs with Spark or traditional ELTs like Talend (depending on the customer); but are moving forward to Apache Beam running on containers even for stuff that can be done concatenating lambdas/cloud functions.