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 03:26:24 -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 0AIBGqcP018463; Wed, 18 Nov 2020 06:17:18 -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 0AIBGopS018454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 18 Nov 2020 06:16:51 -0500 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 0AIBGfu7012992 for ; Wed, 18 Nov 2020 06:16:50 -0500 Received: from oc11expo28.exchange.mit.edu (18.9.4.99) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 18 Nov 2020 06:16:34 -0500 Received: from oc11exhyb4.exchange.mit.edu (18.9.1.100) by oc11expo28.exchange.mit.edu (18.9.4.99) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 18 Nov 2020 06:16:46 -0500 Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.101) by oc11exhyb4.exchange.mit.edu (18.9.1.100) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 18 Nov 2020 06:16:46 -0500 Received: from DM5PR2201CA0016.namprd22.prod.outlook.com (2603:10b6:4:14::26) by SJ0PR01MB6336.prod.exchangelabs.com (2603:10b6:a03:294::9) 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 11:16:45 +0000 Received: from DM6NAM11FT055.eop-nam11.prod.protection.outlook.com (2603:10b6:4:14:cafe::5) by DM5PR2201CA0016.outlook.office365.com (2603:10b6:4:14::26) 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 11:16:45 +0000 Received: from mail-lf1-f48.google.com (209.85.167.48) by DM6NAM11FT055.mail.protection.outlook.com (10.13.173.103) 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 11:16:44 +0000 Received: by mail-lf1-f48.google.com with SMTP id z21so2361226lfe.12 for ; Wed, 18 Nov 2020 03:16:44 -0800 (PST) From: "Forrest Christian (List Account)" To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 18 Nov 2020 03:16:32 -0800 Subject: Re: [EE]: How to find & hire firmware people Thread-Topic: [EE]: How to find & hire firmware people Thread-Index: Ada9naZFWKjncH9rSjKAHKCMfkkJKw== 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.48 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.167.48; helo=mail-lf1-f48.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; bh=1OoLFPRmhgbarAO0o5quLFaN9MJjkfmv49qMnFPAv34=; b=O/3YHVhLrdvsSKN+vzcoegjdRpOJ2D9IgMrHPCsK9BFDf590roYSMUJoR489MyNb/w KR207VsODs6Mj0jrHhByOUr7Y7LbyvBeHnRaOAWtKVm4QJNrFQWiltbE22vNurhvXfXk 49Eqdo35i609qt3kJ+mUPE1Oxof/RFGSU6ZtHCj0Bb3Bfq5W6j9cfH0L8KYqYKotDPQn +nMoIfXTBeYvpLYk6VHP7hpLqcZguRApZda6EbhoZcGqjVabzduDv4K0iR6KFcvTIke0 6KcBEfjIc3gWjRhesEJa+Allt4/WT+/md6U9VIT5lGtjacHCzJkTMumiiS2voO8f5G+c y8dA== authentication-results: spf=pass (sender IP is 209.85.167.48) 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:d0d:: with SMTP id 13mr3335984lfn.176.1605698203012; Wed, 18 Nov 2020 03:16:43 -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 The point of serverless is that I'm buying transactions, NOT a server. It could be a MQTT transaction, or a web page delivery, or a DNS response or storage in a Database, or whatever. Let me see if I can use a different item to describe why I think the term serverless is fine: If you were to state that buying power from the electric grid is "generatorless" I wouldn't have a problem with that. Technically there are generators in the power grid, but I don't need to know about them. As far as I'm concerned the power arrives at my place of consumption over wires and I sure don't have to know or care that there are generators at the other end. So from my perspective, the electricity I get from the grid is 'generatorless', meaning I don't have any generators, I don't have to manage any virtual generators, and I don't really care if there are generators at the other end as long as I get power. But yes, technically it's not 'generatorless' power but again, it could be solar panels and batteries or a zero point energy source for all I care. So "serverless" more has to do with what is visible to the consumer of the service. I don't know how the service is put together, I don't need to know if there are any servers at all. Maybe they've implemented the MQTT broker in a pile of FPGA's, are those servers? Regardless of how the service is architected (whether it has a server on the other end or not), I don't care, as long as the service I'm paying for is delivered. In a traditional 'server' architecture, I'm going to spin up a MQTT broker server, and a database server, and a web server, and probably a few other servers to do housekeeping work, and pay for all of them to be available 24x7 or as needed. With serverless, from my perspective I have no servers. Yes, these pieces probably exist in some form, but someone else does that and I don't care if there are zero or a million servers as long as my workload gets done. So serverless really means that I don't need to have any servers that I really know about, virtual or otherwise. Someone else might, but I'm able to put together an entire product without knowing or caring if they do or do not exist as long as the function is completed. On Wed, Nov 18, 2020 at 1:33 AM Manu Abraham wrote= : > > I guess you need to connect to a MQTT broker. ;-) > And by broker means a MQTT server (eg: mosquitto, or any other > proprietary server) .. > Even if it runs on a virtual machine, it is still a virtual server .. > > Just because you do not have that machine on your premises, does not mean > that > it does not exist, meaningless! > > Someone said; It is all a matter of perception. > Yesterday's fiction is almost today's reality. How true! > > Manu > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=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 .