Apps that send harassment complaints directly to senior leaders may give executives a sense of problems in workplace, but without HR guidance, will senior leaders know what to do? https://goo.gl/NymJ1z #GlobalHR #HRTech
Bully Bosses Can Inflict More Damage with Negative References
Employees trying to escape a bullying boss, and even those who have managed to land a new position, may be surprised to learn that their workplace nemesis is causing further damage by providing negative job references. https://goo.gl/mzNiU1 #GlobalHR #HRTech
API Is Not Just REST, Part 3
gRPC Using HTTP/2
While I am forced to use Websockets for some existing integrations such as with Twitter, and other legacy implementations, it isn’t my choice for next-generation projects. I’m opting to keep things within the HTTP realm, and embracing the next evolution of the protocol, and follow Google’s lead with gRPC. As with other RPC approaches, gRPC is based around the idea of defining a service, specifying the methods that can be called remotely with their parameters and return types. gRPC embraces HTTP/2 as its next-generation transport protocol, and while also employing Protocol Buffers, Google’s open source mechanism for the serialization of structured data.
At Google, I am seeing Protocol Buffers used in parallel with OpenAPI for defining JSON APIs, providing two speed APIs using HTTP/1.1 and HTTP/2. I am also seeing Protocol Buffers used with HTTP/1.1 as a transport, making it something I have had to integrate with alongside SOAP, and other web APIs. While I am integrating with APIs that use Protocol Buffers, I am most interested in the usage of HTTP/2 as a transport for APIs, and I am investing more time learning about the next generation headers in use, and the variety of approaches in which HTTP/2 is used as a transport for traditional APIs, as well as multi-directional, streaming APIs. https://goo.gl/45nEy9 #DataIntegration #ML