Common utility methods, providing more power to streams and functions in general.
When streaming in an I/O context for example, it's not always guaranteed that the receiving end of the stream will be non-blocking. For example, when writing to the OutputStream of a slow HTTP connection, ultimately the stream which is being consumed is kept open for too long.
If the stream that you're consuming is a streaming resultset which keeps open an expensive data connection, then you want to close that stream as soon as possible. So it's best not to rely on the consuming capacity of the receiving end. A BufferedOutputStream is also not enough to catch that up.
That's where the BufferedStream comes in. It will consume the entire input stream as soon as the output stream polls for the first element. BufferedStream relies on an internal FIFO-stack, onto which the incoming stream is consumed and from which the going stream is going to grab items at the same time.
Remember that you can always build in multiple BufferedStreams, this way you can go from pile to (cheaper) pile. (💨 → 🍔 → 🥪 → 🥓 → 🐌)
It's possible upon construction to provide a Deque supplier, which will then be used as internal cache.
There are two built-in default cache implementations.
-
The default cache is just a class extending ConcurrentLinkedDeque. It's thread-safe, that's that.
-
This cache extends the default cache, but blocks pushing as long as a maximum allowed number of items is reached. It will keep the incoming stream open for a longer amount of time, but it will reduce memory usage.
Predicates is a set of helper methods which can help a lot when writing clean functional code. It's designed to replace common lambda's, using logical naming.
optional.filter(against(Person::getName, "John"));optional.filter(against(Person::getEmail, not(String::isEmpty)));There are helpers which create null-safe Predicates for usage with method references of Boolean-methods.
stream.filter(safe(SomeObject::getBoolean));There are also helpers methods for creating cached Predicates, which will only evaluate once for each distinct value. This can be helpful when the Predicate houses an expensive operation, which does not change within the lifespan of the Predicate.
stream.filter(cached(ExpensiveMethod::call));This sneaky caretaker has to be taken with care. It makes checked exceptions behave like runtime exceptions, by making them generic. This bypasses the Java compiler and is perfectly allowed within the JVM, which doesn't even know about checked exceptions.
The trick is done by turning the common java functions such as Consumer, Function, Supplier, ... into throwing ones. These throwing ones are just sub interfaces of the originals, so the original superclass is then returned. The throwing method is then caught and the exception is thrown genericly.
stream.forEach(sneaky(Files::readAllBytes));The problem is now that everything is fine, but you know it may possibly throw an IOException. So in this case, it's advisable to have your method throw IOException too. It hands over resposibility to the caller of your method and everything is checked again.
It just comes in real handy when working with streams, but always remember that you're just hiding exceptions you would otherwise had to handle. And it's better to throw these exact exceptions, than to just throw a RuntimeException(e); out of lazyness. It keeps the code clean, but it requires responsibility.