https://blog.sonos.com/en/end-of-software-updates-for-legacy...
1,575 karma · joined February 1, 2009
hn [Shift + 2] adamfeldman.net
@AdamFeldman on Twitter, GitHub, and elsewhere.
Now: B2B SaaS, and building malleable software.
Past: Healthcare B2B SaaS, E-commerce consulting, from shipping and operations to software, sales, and marketing.
[ my public key: https://keybase.io/adamfeldman; my proof: https://keybase.io/adamfeldman/sigs/_Xoj4dMcQIQehierULEwoVdOJetDZPatmEbc4jStc5g ]
meet.hn/city/29.7589382,-95.3676974/Houston
github.com/adamfeldman - linkedin.com/in/adamrfeldman - x.com/adamfeldman
https://blog.sonos.com/en/end-of-software-updates-for-legacy...
Edit: These tools can be self-hosted and integrated to provide out-of-the-box auth functionality to your application.
* The ORY ecosystem of tools [1]
* Gluu [2]
* Keycloak [3]
[1]: https://www.ory.sh/docs/next/ecosystem/overview
[2]: https://www.gluu.org
For an open-source solution that largely revolves around the React frontend, consider react-admin [1] + its adapter for Hasura [2].
[1]: https://github.com/marmelab/react-admin [2]: https://github.com/hasura/ra-data-hasura, https://github.com/hasura/graphql-engine/
In Ruby/Rails-land, there is https://bullettrain.co.
[1]: https://github.com/hasura/graphql-engine/blob/master/event-t...
In Elixir-land, there is https://github.com/commanded/eventstore (which AFAICT is closely tied to the Commanded CQRS/RS framework https://github.com/commanded/commanded)
I too wish it was a built-in Proxmox feature, or at least officially documented...
[1]: https://blog.jenningsga.com/private-network-with-proxmox/
node-red is available as a hass.io add-on [1], with the Home Assistant node-red plugin pre-installed
Without Anthos, I can only use the fully-managed edition of Cloud Run. Or, presumably, I can set up self-managed Knative in my non-Anthos GKE cluster...
I'd wager that Dapr's virtual actors [1] were inspired in-part by Microsoft's work on Orleans [2]. I've read through some of the Orleans docs, and Dapr looks to be a more accessible (cross-language, non-CLR!) way to build using some of Orleans' concepts and capabilities.
!! this is super cool: "You can also perform aggregate queries across actor instances, avoiding the common turn-based concurrency limitations of actor frameworks [3].
[1]: https://github.com/dapr/docs/tree/master/concepts/actor [2]: http://dotnet.github.io/orleans/ [3]: https://github.com/dapr/docs/blob/master/concepts/state-mana...
If I understand it correctly, it will make it easier for me to build applications by separating the "plumbing" (stateful & handled by Dapr) from my business logic (stateless, speaks to Dapr over gRPC). If I build using event-driven patterns, my business logic can be called in response to state changes in the system as a whole.
I think an example of stateful "plumbing" is a non-functional concern such as retrying a service call or a write to a queue if the initial attempt fails. Since Dapr runs next to my application as a sidecar, it's unlikely that communication failures will occur within the local node.
There seem to be extensive, nice docs on the concepts behind Dapr: https://github.com/dapr/docs/tree/master/concepts.
https://www.cockroachlabs.com/blog/serializable-lockless-dis...
Accessible through this page via the hamburger menu > click “Read the docs”: