I don't get it. Why are they supposed to be dropped only because the
logging service is down?
Making a service between P and the logger is an interesting way to go
>
Another service which could be down then as well? Why not a Queue?
Am Donnerstag, 14. Februar 2019 10:05:40 UTC+1 schrieb Michel
>
> What about queuing
>
I cannot edit my post so a new answer here with more explanation: Just have
a RabbitMQ or whatever in between and every logging sends a message to it
while the logging service consumes it. As long as the logging service is
down the messages remain in the queue.
Your r
What about Queuing?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/
You mean, loading the files in parallel take the ~same time as loading them
sequentially? It seems that there is somewhere else a bottleneck...
Am Sonntag, 16. September 2018 14:08:50 UTC+2 schrieb Thomas Solignac:
>
> Hello,
>
> I have a loading step, where I have something like 60 files to read
