Microservices / Cloud-native / service mesh by tgogos

"We burnt our hands enough and we have too many roughhouses around us. By infusing microservices architecture gratuitously, you’re just going to turn your bad code into a bad infrastructure." "There are numerous amounts of tried & tested solutions available, but they all come with a price - Latency. Moving away from an in-memory transaction to network based communication will change your latency unit from nanoseconds to microseconds." "Microservices shouldn’t be your default application architecture. They’re not the silver bullet you were looking for. Keep yourself steady with KISS and YAGNI."

#design principles #devops #microservices #soa #kiss-principle #latency

over 6 years ago

The Service Mesh: What Every Software Engineer Needs to Know about the World's Most Over-Hyped Technology

https://servicemesh.io/

#service mesh

over 6 years ago

Are We Really Cloud-Native?

https://www.infoq.com/presentations/cloud-native-intro/

- it’s not about picking a framework or two. It is a transformational journey and getting DevOps right - Getting to know the services of what your cloud provider has to offer, and really tuning your software to the underlying infrastructure, that is what cloud-native is basically all about. Technologies or frameworks are not going to make you cloud-native - it’s hooking stuff together, because if you want to reap the benefits of the cloud, you really have to know all the services that your cloud provider has to offer (e.g. there’s at least four or five ways to run Docker containers on AWS) - Figuring out which way actually suits that particular application or that particular component, that is what cloud-native is actually about - Gluing the software and your infrastructure together is something which is not an end state. This is a continuous journey. - It’s not thinking about servers and managing servers at scale; it is thinking about managing a mixture of both software and infrastructure at scale. It’s about services and consuming everything as API’s, and gluing that together as a deployment. - it’s about modernizing your infrastructure and the process of actually moving faster and not breaking things - The organizational culture plays a large role in it (see Conway’s Law…)

#devops #cloud-native #infrastructure at scale #continuous journey #transformational journey

over 6 years ago

Service Mesh Ultimate Guide: Managing Service-to-Service Communications in the Era of Microservices

https://www.infoq.com/articles/service-mesh-ultimate-guide/

#architecture #devops #microservices #service mesh #observability #east-west

over 6 years ago

Monitoring in the time of Cloud Native

https://medium.com/@copyconstruct/monitoring-in-the-time-of-cloud-native-c87c7a5bfa3e

#kubernetes #monitoring #observability #opentracing #prometheus #logs #metrics #traces

over 6 years ago

Metaswitch CTO sets the record straight on what "cloud native" really is

https://www.youtube.com/watch?v=abAWczMCSdA

5:40 -> A network control plane like for example an IMS or the control plane of a 5G packet core, it's essentially a transaction processing engine. I mean you're getting messages coming in from from handsets or from phones or whatever requesting sessions and so on and you know it's conceptually not dissimilar to what building a web app is. You know --where people are submitting web page requests-- so the concepts of stateless processing and all that kind of stuff it's directly transferable from the web scale world to the telco world, there really is no fundamental difference. On the user plain... user plains are doing packet processing. They're inherently stateful. You can't build a cost-effective stateless user plan, just doesn't make sense...

#telcos #cloud-native #culture #practices #5g

over 6 years ago