The latest articles on DEV Community by tamusjroyce (@tamusjroyce). https://dev.to/tamusjroyce https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F146293%2Ff6c38265-2caf-487d-a0e5-bf14e5f11eb3.jpeg https://dev.to/tamusjroyce en tamusjroyce Tue, 25 Apr 2023 12:33:50 +0000 https://dev.to/tamusjroyce/stop-using-the-terms-monolith-and-microservice-3aj5 https://dev.to/tamusjroyce/stop-using-the-terms-monolith-and-microservice-3aj5 <p>Stop using the terms monolith and microservice.</p> <p>The concepts are distributed vs remoting. You can even setup API’s to do both. And I said can. Not that it should do both.</p> <p>Martin Fowler is wrong in using monolith. He should say big-ball-of-mud. Linux 1.2a kernel was the last monolith. And the famous debate changed it, to this day, from being one.</p> <p>gRPC, GraphQL, and message queues/event stores are not microservices. No matter how closely you try to get it to fit. Or even by extending microservices.</p> <p>These are all remoting</p> <p>Distributed means a registry like npmjs, nuget, github/gitlab, local, has a copy you pull into your project and use. Or an installer you download.</p> <p>The question isn’t how remoting and distributed are different. But how are they similar? How are they the same?</p> <p>It a website needs to do something secure, use remoting.</p> <p>If functionality needs distributed, use distributed.</p> <p>If what that otherwise distributed resource needs protected, use remoting.</p> <p>There is more value in discussing the type of app you are writing:</p> <p>Is a website too complex?<br> Should I create a desktop app? At least at first<br> etc…</p>