Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Tue, 17 Nov 2020 23:59:04 -0800 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0AI7oJjq021762; Wed, 18 Nov 2020 02:50:39 -0500 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0AI7oIKW021740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 18 Nov 2020 02:50:18 -0500 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 0AI7oHOa031642 for ; Wed, 18 Nov 2020 02:50:18 -0500 Received: from oc11expo12.exchange.mit.edu (18.9.4.17) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 18 Nov 2020 02:50:04 -0500 Received: from oc11exhyb7.exchange.mit.edu (18.9.1.112) by oc11expo12.exchange.mit.edu (18.9.4.17) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 18 Nov 2020 02:50:17 -0500 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.175) by oc11exhyb7.exchange.mit.edu (18.9.1.112) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 18 Nov 2020 02:50:17 -0500 Received: from DM5PR20CA0015.namprd20.prod.outlook.com (2603:10b6:3:93::25) by MN2PR01MB5807.prod.exchangelabs.com (2603:10b6:208:18b::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3589.20; Wed, 18 Nov 2020 07:50:15 +0000 Received: from DM6NAM11FT027.eop-nam11.prod.protection.outlook.com (2603:10b6:3:93:cafe::9d) by DM5PR20CA0015.outlook.office365.com (2603:10b6:3:93::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3589.20 via Frontend Transport; Wed, 18 Nov 2020 07:50:15 +0000 Received: from mail-lf1-f44.google.com (209.85.167.44) by DM6NAM11FT027.mail.protection.outlook.com (10.13.172.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3564.28 via Frontend Transport; Wed, 18 Nov 2020 07:50:13 +0000 Received: by mail-lf1-f44.google.com with SMTP id 74so1594799lfo.5 for ; Tue, 17 Nov 2020 23:50:13 -0800 (PST) From: "Forrest Christian (List Account)" To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 17 Nov 2020 23:50:01 -0800 Subject: Re: [EE]: How to find & hire firmware people Thread-Topic: [EE]: How to find & hire firmware people Thread-Index: Ada9gK9SMstD6BAXQx2TtOzEAR1fhA== Message-ID: References: <5FB358FA.5040207@narwani.org> <70249b66-1d70-0428-fc9d-a4332ebf0eae@linuxha.com> <20201117204949.GE20895@laptop.org> <69f35b01-aa4d-6ee2-d0f4-53989d80d084@linuxha.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of packetflux.com designates 209.85.167.44 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.167.44; helo=mail-lf1-f44.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetflux-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Aprkod0bdoW/fYqKCOLnHPuP5uvRqnabHZy2qaKA8zo=; b=1zQbWREh3Rq546w722T1PdBw53clnluFNQFmCOMGsVKtMfnJkBW8/nKQgC0lDyNvTp gGVjhMhmBI5KaZHoUHxZ3FPjln3KuewpUqjzebLOcX0M3qyHnOpysvd/notq0UQoQlch K3VCL4Rt1AG5n+daGEKDOLj31uRSBJ+uoEc0I3oD4LHNHUjTaZ8/VFOrde8Kin8+8SW/ 16wn3lFDrd9NK/o3lU0mL+S5StYfNDo16OmSoF8TwCcKYo14s+ztYgX9bshqHKin3pPn 4Tg3V9mO82yU1yrcP5DSwsGVWEpdju8BCZjuDKMXzD6NfxKpvOhufPg4kFxxYaitloln vQlw== authentication-results: spf=pass (sender IP is 209.85.167.44) smtp.mailfrom=packetflux.com; mit.edu; dkim=pass (signature was verified) header.d=packetflux-com.20150623.gappssmtp.com; mit.edu; dmarc=bestguesspass action=none header.from=packetflux.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a19:7e94:: with SMTP id z142mr2995966lfc.268.1605685812018; Tue, 17 Nov 2020 23:50:12 -0800 (PST) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 On Tue, Nov 17, 2020 at 4:30 PM Neil Cherry wrote: > This terminology is getting worse and having less meaning. Serverless > servers? Actually "Serverless" is a pretty accurate term, and I'm starting to experiment with it with MQTT messaging from the embedded world. In short serverless just says that you tell your cloud provider (Amazon AWS, Google Cloud, Microsoft Azure), etc. what you want it to do and don't worry about the underlying servers at all. I.E. things like "When you get a temperature reading via MQTT from a device, stick it in a database". Then another serverless service could say 'if you see a temperature over a certain amount, send an email', and so on. Because you're paying per transactions it can be really cheap...for instance, AWS costs $1 per million MQTT messages. So if you have a device that sends data once a minute it's going to cost you around 4 cents per month for message reception for that device. Oh and just over 4 cents per *year* to maintain the connection to the device. And you'll end up paying for the database storage, etc. Yes it can add up, but generally at least at the low end it's cheaper than running a full server infrastructure for services like this. Plus you don't have to think about how you're going to manage the underlying services. --=20 - Forrest --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .