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:50:53 -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 0AIBgvL1021362; Wed, 18 Nov 2020 06:43:08 -0500 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0AIBguvL021359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 18 Nov 2020 06:42:56 -0500 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 0AIBgrXl031530 for ; Wed, 18 Nov 2020 06:42:56 -0500 Received: from w92expo9.exchange.mit.edu (18.7.74.63) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 18 Nov 2020 06:42:40 -0500 Received: from oc11exhyb6.exchange.mit.edu (18.9.1.111) by w92expo9.exchange.mit.edu (18.7.74.63) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 18 Nov 2020 06:42:53 -0500 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.176) by oc11exhyb6.exchange.mit.edu (18.9.1.111) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 18 Nov 2020 06:42:53 -0500 Received: from MWHPR15CA0053.namprd15.prod.outlook.com (2603:10b6:301:4c::15) by PH0PR01MB6247.prod.exchangelabs.com (2603:10b6:510:18::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Wed, 18 Nov 2020 11:42:52 +0000 Received: from CO1NAM11FT055.eop-nam11.prod.protection.outlook.com (2603:10b6:301:4c:cafe::3f) by MWHPR15CA0053.outlook.office365.com (2603:10b6:301:4c::15) 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:42:52 +0000 Received: from mail-yb1-f182.google.com (209.85.219.182) by CO1NAM11FT055.mail.protection.outlook.com (10.13.175.129) 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:42:52 +0000 Received: by mail-yb1-f182.google.com with SMTP id t33so1401821ybd.0 for ; Wed, 18 Nov 2020 03:42:52 -0800 (PST) From: Manu Abraham To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 18 Nov 2020 03:42:38 -0800 Subject: Re: [EE]: How to find & hire firmware people Thread-Topic: [EE]: How to find & hire firmware people Thread-Index: Ada9oRIS0eHem7o9T9ybcU8MBKZS8g== 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.219.182 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.219.182; helo=mail-yb1-f182.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; bh=xTv1b+3UwkRFuXTjOQYZbqyYswt0hWAaH8J3ySzhSm4=; b=o5nWQT9cxm6u3Kk3AwBkPO0+gGExTM4ydUUHHVpHAxpB0XAE3v8Y2x0nOOKEeeuyKq r4TJr6l4MelutmEzHB/d2uG3TwpIClN8bpzxr6BelOM5cQ+ElS5tkDEztbLOVZfVioXj /FI/Uyoom8rbEIxteeNo2vVDrAQ30pFhzN4CW41vMe0TwpgJqXKPNR2zmu/LRon3gmIO Rj4yboCeUPRtSP8IHF2RBXJh/V3e6RosFIHXCzP09zks6RuVi+e4/3sZEbk3TbPAZ3Yt 3mP8HgV0ivUINteFA+pvc0yxpI2+MbsnuOkTywqNeeoWHchgPPhakgUs8wpBYS7eCGZK ZwEA== authentication-results: spf=pass (sender IP is 209.85.219.182) 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:a25:b090:: with SMTP id f16mr6310633ybj.466.1605699771053; Wed, 18 Nov 2020 03:42:51 -0800 (PST) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 On Wed, Nov 18, 2020 at 4:47 PM Forrest Christian (List Account) wrote: > > 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: "Actually "Serverless" is a pretty accurate term" "Then another serverless service could say 'if you see a temperature over a certain amount, send an email', and so on." The whole point is: 1. Someone else implements the server side for you. 2. you are buying services, 3. you only have a client implementation. 4. You still need to configure the MQTT Server and the client with the cryptographic keys, if you are doing anything serious over the internet That does not mean that the system is serverless. There are other serverless systems, which use P2P modes of operation. It is still a well defined Client Server architecture. That's what I was trying to assert. Just because, I bought email services from a third party, the system topolo= gy is not "serverless". You still need to configure the client for server connectivity. When the provider is down, it is termed as Server down, not anything else! Manu --=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 .