On Monoliths and Microservices – InApps is an article under the topic Software Development Many of you are most interested in today !! Today, let’s InApps.net learn On Monoliths and Microservices – InApps in today’s post !
Read more about On Monoliths and Microservices – InApps at Wikipedia
You can find content about On Monoliths and Microservices – InApps from the Wikipedia website
Welcome to InApps Context, a podcast where we discuss the latest news and perspectives in the world of cloud native computing. Today we’re talking to InApps news correspondent Mike Melanson, about his recent coverage of the ongoing debate over the value of microservices. We also discuss the top podcasts and news stories for the week, covering topics such as developer relations, mobile platform development and optimization, and distributed architectures.
Listen to all TNS podcasts on Simplecast.
We have been covering the debate over the relative merits of microservices for a while now. Microservices offer a number of advantages on the development side. Separate teams can work different parts of a language, even in their preferred languages and tools. Updates can be quietly inserted without needing to refresh the entire application. But while the hype around microservices is considerable, industry observers have been starting to recognize the limitations as well. Many have been advocated returning to the opposite approach: building single large “monolithic” applications.
Recently, Melanson wrote about Google cloud native evangelist Kelsey Hightower’s belief that monoliths are the future.
“Monoliths are the future because the problem people are trying to solve with microservices doesn’t really line up with reality,” Hightower wrote in his own blog post. A company lacking coding discipline that ends up with a disaster of a codebase may see microservices as an answer, but in reality, it is just trading class instantiation for function calls. “They’re initiating things and throwing it over a network and hoping that it comes back,” Hightower writes.
For the podcast of the week, we discuss TNS London Correspondent Jennifer Riggins’ interview with Mary Thengvall, over the value — and how to measure the value — of developer relations. We also discuss how Tricentis tools could have been used to prevent the app failure that led to the U.S. Democratic Iowa Caucus disaster, eBay’s performance-improvement tweaks, Microsoft’s new Dapr distributed computing architecture, Humio’s advice for migrating to the cloud, and a recent Istio service mesh bug unearthed by Aspen Mesh.
TNS editorial and marketing director Libby Clark hosted this episode, alongside founder and publisher Alex Williams.
InApps is a wholly owned subsidiary of Insight Partners, an investor in the following companies mentioned in this article: Tricentis, Hightower.
Feature image by Christine Sponchia from Pixabay.
Let’s create the next big thing together!
Coming together is a beginning. Keeping together is progress. Working together is success.