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; Wed, 18 Nov 2020 00:18:47 -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 0AI8BraA029637; Wed, 18 Nov 2020 03:12:01 -0500 Received: from outgoing-exchange-5.mit.edu (OUTGOING-EXCHANGE-5.MIT.EDU [18.9.28.59]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0AI8BqXh029634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 18 Nov 2020 03:11:52 -0500 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 0AI8BcSI023884 for ; Wed, 18 Nov 2020 03:11:52 -0500 Received: from w92expo10.exchange.mit.edu (18.7.74.64) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 18 Nov 2020 03:11:32 -0500 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by w92expo10.exchange.mit.edu (18.7.74.64) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 18 Nov 2020 03:11:45 -0500 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.104) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 18 Nov 2020 03:11:44 -0500 Received: from DM5PR12CA0024.namprd12.prod.outlook.com (2603:10b6:4:1::34) by MN2PR01MB5341.prod.exchangelabs.com (2603:10b6:208:10d::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3564.28; Wed, 18 Nov 2020 08:11:43 +0000 Received: from DM6NAM11FT041.eop-nam11.prod.protection.outlook.com (2603:10b6:4:1:cafe::68) by DM5PR12CA0024.outlook.office365.com (2603:10b6:4:1::34) 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 08:11:43 +0000 Received: from mail-ej1-f48.google.com (209.85.218.48) by DM6NAM11FT041.mail.protection.outlook.com (10.13.172.98) 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 08:11:43 +0000 Received: by mail-ej1-f48.google.com with SMTP id i19so1447225ejx.9 for ; Wed, 18 Nov 2020 00:11:43 -0800 (PST) From: Ryan O'Connor To: "Forrest Christian (List Account)" CC: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 18 Nov 2020 00:11:30 -0800 Subject: Re: [EE]: How to find & hire firmware people Thread-Topic: [EE]: How to find & hire firmware people Thread-Index: Ada9g3BiVrphb7QxT7O3wQWtdyhkaA== 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 gmail.com designates 209.85.218.48 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.48; helo=mail-ej1-f48.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zuadF97ob1oCnFGeaP303WnVyjXM+6bse2F/4ey8DSM=; b=MtZ2Cz0Wwt9tagsbOZnVEsMvaCKfWKYFuorx8JybQEySGZW2vJ7oXPS15zno2DhLfY hQBN5OGrLWyH26wT7a1zFo3v7s/nfI2hznAKGbtpBuAeLpNbDtZZfjxpuAb3ClKA0LDW BXyJK89X6hGjKOfgfyjsrg7flRo7YO3itbYR+I448w5jLL/Uqfh1RyE2/9020EAYjDfu E7d1U1LoNX+jG7hspKAa+i9byXfkNk8DeNNVAVUyLgqB1IWdwE4/0QgtzLIlisa+Fgz3 wtaj2C7P0LgTHHJqOCoi/SzbbUHPHUfaGQCJ1ONl7LnEfhmGZGcz1DlKzMeVmLZmIWSA +DUA== authentication-results: spf=pass (sender IP is 209.85.218.48) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.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:a17:906:1159:: with SMTP id i25mr21563219eja.398.1605687102229; Wed, 18 Nov 2020 00:11:42 -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 Exactly. If you run a server then you risk paying for resource allocation you don't use (cpu, memory). On Wed, 18 Nov 2020 at 20:50, Forrest Christian (List Account) < lists@packetflux.com> wrote: > > > 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 g= et > 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 devi= ce > 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 infrastructu= re > for services like this. Plus you don't have to think about how you're > going to manage the underlying services. > > -- > - 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 .