This blog post is one in a series that will give you some insight into the full day training class (Microservices Solution Architectures) I will be teaching at the ITARC Austin on October 6th, 2016. A better question may be "If I can't/don't change , am I going to create business value?" In my opinion,
Phil Helm: There are lots of ways to do microservices architecture. The way we're doing this POC right now is we've got a bunch of VMs that sit out. This is Azure, for us, and then inside these VMs, we've got a jar. This could be a business capability, this could be ... This would
Paul: Micro-services. Venky: Micro-services. Okay. Micro-services is the definition and the way they are implemented. They do a very specific function that can be completely contained and packaged. They will never give you something that an end-user can really make use of. Paul: Can you give me an example of that? Is Calculate Premium a
We are using Spring Boot and Spring Cloud to do that. Essentially, we've got several jars that are just bootable jars. In each one of those jars is either a core infrastructure piece. It's something that you need from a micro-services architecture perspective. Monitoring, audit, logging, whatever it is. Configuration, you need all those individual
Simon Brown says it nicely: I'll keep saying this ... if people can't build monoliths properly, microservices won't help. #qconlondon #DesignThinking #Modularity— Simon Brown (@simonbrown) March 4, 2015 Architect Clippy is a bit more snarky: I see you have a poorly structured monolith. Would you like me to convert it into a poorly structured set
In my part of the world, it's not uncommon for people to say that someone wouldn't recognize something if it "bit them in the [rude rump reference]". For many organizations, that seems to be the explanation for the state of their enterprise IT architecture. For while we might claim to understand terms like "design", "encapsulation",
Over the last fifteen months, many electrons have been expended discussing the relative merits of the application architecture styles commonly referred to as microservices and monoliths. Both styles have their advocates, and the interesting aspect is not their differences, but their agreement on one core principle - modularity. Both camps seem to agree that "good"
Technical Empathy - the ability to see the system from the point of view of the caller of your code, not just the point of view of your code— Michael Feathers (@mfeathers) January 26, 2015 Michael Feathers' tweet about technical empathy packs a lot of wisdom into 140 characters. Lack of technical empathy can lead