You can hybridize your use of third party services by hosting your own API on your server that then accesses the third party service. This also enables you to host different versions of your own API for different versions of your gizmo in the field without having to roll field software updates - although an update mechanism would be one of the first systems I'd build before deploying to the field. ;)
@MarcdeVinck2 жыл бұрын
Oh you definitely can! But that goes beyond the scope of this tutorial. Haha. OTA programming is a whole other topic that gets really complicated, but it can be done too.
@BinaryRhyme.JackOfArts2 жыл бұрын
@@MarcdeVinck Agree. Just wanted to toss that comment out for consideration. Encapsulating web services becomes even more important when authentication and billing get involved, lol. Great vid series, btw. I just started in on the whole electro-mechanical thing to engineer an automated dumbwaiter for a family member. My background is principally software - so very helpful. ;)
@MarcdeVinck2 жыл бұрын
@@BinaryRhyme.JackOfArts Thank you! And thanks for the comment, it's much appreciated. I totally agree! I've worked on a project where the web service shut down. Then what!? At some point, you roll your own.