Microservices - 72 resources
blog.arkency.com
Microservices - 72 resources
1–10 of 48 posts
Re: Microservices - 72 resources
#2What is actually the difference between a "microservice" architecture, and a component based architecture?
Re: Microservices - 72 resources
#3What is actually the difference between a "microservice" architecture, and a component based architecture?
You can install a component and never upgrade it. You might fall behind on security concerns and be running different code from your counterparts but you can do that if you like.
If you consume some service, you're going to have to keep your app up-to-date should the service chage, go away, or fail. Therefore one could argue that services are easier to manage centrally at the expense of some overhead and less flexibility.
Re: Microservices - 72 resources
#4I was expecting a list of 72 micro services, instead there are 72 articles on the subject. Feels like it's the opposite of "curated list" - a list everything.
Re: Microservices - 72 resources
#5What do people recommend for learning about SOA / microservices? I liked Patterns of Enterprise Application Architecture and Enterprise integration patterns, but didn't have a great experience with the SOA design with Rails book - it felt much to focused on very basic details (e.g., here is how you consume JSON).
Re: Microservices - 72 resources
#6Why do we need a new term for this? Isn't this just Unix philosophy applied to SaaS? No need to learn about "micro services" when you can learn about Unix/Linux and why it's built the way it is, then apply that knowledge to your SaaS product.
Re: Microservices - 72 resources
#7Why do we need a new term for this? Isn't this just Unix philosophy applied to SaaS? No need to learn about "micro services" when you can learn about Unix/Linux and why it's built the way it is, then apply that knowledge to your SaaS product.
I agree with your sentiment. As an industry we spend way too much time rediscovering principles that are well known to previous generations of programmers. That said, I'm grateful to see these ideas showing up where they're desperately needed.
Re: Microservices - 72 resources
#8This article would be way better if each resource was in a separate blog post. :) #snark
Re: Microservices - 72 resources
#9What is actually the difference between a "microservice" architecture, and a component based architecture?
You can install a component and never upgrade it. You might fall behind on security concerns and be running different code from your counterparts but you can do that if you like. If you consume some service, you're going to have to keep your app up-to-date should the service chage, go away, or fail. Therefore one could argue that services are easier to manage centrally at the expense of some overhead and less flexibi…
That doesn't sound like a primary difference between the two? You can certainly leave up an old service.
Re: Microservices - 72 resources
#10What is actually the difference between a "microservice" architecture, and a component based architecture?
This might help http://petritsch.co.at/download/SOA_vs_component_based.pdf
It seems like a distinction is between organization-wide, discoverable services (SOA -> microservices) and reusable components that may or may not communicate via a remote protocol.
EDIT - From reading more about component-based, another difference is that services are less tightly coupled. They often run on different machines & OS's, and are also often written in different languages. In the case of microservices, a common theme in these resources is that each microservice is owned by the part of the organization that created it, which is pretty interesting.