Mark Russinovich, Chief Technology Officer of Azure, gives an overview of Microsoft Microservice strategy at the Cloud Networking Meetup 2018 event hosted by Microsoft. https://t.co/QljAtSWp1n
#Microservices should be built around business capabilities and should be independently deployable by fully automated deployment machinery - aka Kubernetes.https://t.co/7IzyAVJqic
Microservices architecture on paper sounds amazing but unless the business as a whole is not committed to it, then your department will end up with low morale, low productivity, and tones of code debt.https://t.co/bxEu1d7PFN
Serving millions of requests per minute with a microservices environment is not an easy task. Every request is routed to many applications, and may potentially stall or fail at any step in the flow. https://t.co/gC9AiSQPES
You can try to improve your organization directly, by proposing more automation and cross-team collaboration. But don’t be surprised if things go easier if you start with a magic stone.https://t.co/F8FZeR2fPm
Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services, and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable.https://t.co/Wg3D4JgkP6
This reference architectures shows a #microservices application deployed to Azure Kubernetes Service (AKS). It shows a basic AKS configuration that can be the starting point for most deployments. https://t.co/P3pIz3Lj2x
We chose to evolve Shopify into a modular monolith, meaning that we would keep all of the code in one codebase, but ensure that boundaries were defined and respected between different components.https://t.co/YEIEqvKrNF
Designing #microservices with BDD concentrates on the semantics of the operations and not the underlying syntax of the implementation.https://t.co/I0Ls5F0oC4
"As with any software system, the combination of organic growth and large code bases creates challenges. I want to share some of these challenges and our solutions."https://t.co/MXQHqtlhZC
Functional decomposition is a way to decompose break down a system into its most simplistic components and functionshttp://www.waynecliffordbarker.co.za/functional-decomposition-for-microservices/
Testing #Microservices is a complex problem. There is no magic bullet, neither there is a set of rules that can be easily used in any situation. https://t.co/sV955r6lQR
Building applications based on #microservices does not guarantee that the application will be a success, however it’s an approach that will teach you to manage your logical resources, components or modules.https://t.co/Ne0k6kl3zM