IoT Core will be discontinued on Aug. 16, 2023

• django-nats-nkeys

  1 5 2.7 Python

  

  I'm in the process of migrating PrintNanny.ai's remote command/event system off Cloud IoT Core. I've been running on IoT Core for 1.5 years. Here's my breakdown of the costs...

  - $236.99 in usage, approx 1% of project's total revenue

  - ~20 hours to implement pub/sub applications running on a mix of Raspberry Pi & GCP VMs. Implementations were in Rust and Python. It would have taken much, much longer to stand up a managed MQTT broker and identity/key management that I felt comfortable using in my own home, let alone providing to customers.

  - Hundreds of hours implementing and debugging glue between GCP's Pub/Sub product, websocket-based subscribers, and MQTT subscribers/publishers.

  I don't regret my decision (wouldn't have shipped otherwise), but I'm looking forward to the next phase. Here's what I'm migrating towards:

  - NATs message broker. NATS supports connections via MQTT and Websocket protocols, besides NATS own protocol.

  - django-nats-nkeys for org, identity, and JWT management (not production-ready, don't use this until I've been eating my own dog food for a few months) [1]

  - AsyncAPI schemas [2] for core message APIs, including schemas for 3rd-party printer software events (OctoPrint, Moonraker, Repetier, etc). This will underpin PrintNanny's plugin system.

  [1] https://github.com/bitsy-ai/django-nats-nkeys

  [2] https://www.asyncapi.com/

• spec

  42 3,828 7.9 JavaScript

  The AsyncAPI specification allows you to create machine-readable definitions of your asynchronous APIs. (by asyncapi)

  

  I'm in the process of migrating PrintNanny.ai's remote command/event system off Cloud IoT Core. I've been running on IoT Core for 1.5 years. Here's my breakdown of the costs...

  - $236.99 in usage, approx 1% of project's total revenue

  - ~20 hours to implement pub/sub applications running on a mix of Raspberry Pi & GCP VMs. Implementations were in Rust and Python. It would have taken much, much longer to stand up a managed MQTT broker and identity/key management that I felt comfortable using in my own home, let alone providing to customers.

  - Hundreds of hours implementing and debugging glue between GCP's Pub/Sub product, websocket-based subscribers, and MQTT subscribers/publishers.

  I don't regret my decision (wouldn't have shipped otherwise), but I'm looking forward to the next phase. Here's what I'm migrating towards:

  - NATs message broker. NATS supports connections via MQTT and Websocket protocols, besides NATS own protocol.

  - django-nats-nkeys for org, identity, and JWT management (not production-ready, don't use this until I've been eating my own dog food for a few months) [1]

  - AsyncAPI schemas [2] for core message APIs, including schemas for 3rd-party printer software events (OctoPrint, Moonraker, Repetier, etc). This will underpin PrintNanny's plugin system.

  [1] https://github.com/bitsy-ai/django-nats-nkeys

  [2] https://www.asyncapi.com/

• SurveyJS

  surveyjs.io

  sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• Killed by Google

  2,301 2,340 6.9 TypeScript

  Part guillotine, part graveyard for Google's doomed apps, services, and hardware.

  'Stadia isn't going anywhere soon, or the people working in the division haven't been told and have continued spending money left and right with partnership deals, which would be a weird waste of money.'

  LOL, that is Google 101.

  Allow me to introduce you to the Google Graveyard[1]

  [1] https://killedbygoogle.com/

Suggest a related project