I just posted a question asking the difference between MapR and Cloudera's architecture and used "architecture" and "infrastructure" interchangeably. Is this appropriate?
To put this in context, MapR and Cloudera are distributions of Hadoop. They each contain various daemons that interact with each other in various ways. When I refer to infrastructure/architecture, I am referring to the daemons, their actions, and the relationships between the daemons.
What is the correct word I am looking for - architecture or infrastructure?
What is the difference between the two?
Technology Infrastructure vs Software ArchitectureTechnology infrastructure are basic foundational services such as networks, computing and storage services upon which software services are built. Software architecture defines the structure of software.
Infrastructure is the foundation or framework that supports a system or organization. In computing, information technology infrastructure is composed of physical and virtual resources that support the flow, storage, processing and analysis of data.
One of the biggest differences between the jobs seems to be that building architects deal with physical design and software architects with software design. Also, software architects require an understanding of both the design and implementation.
Infrastructure Architecture is a structured and modern approach for supporting an organization and facilitating innovation within an enterprise. It concerns modeling the hardware elements across an enterprise and the relationship between them.
Infrastructure describes the actual set of components that make up a system, while architecture describes the design of the components and their relationships. In a nutshell, a system is built on an infrastructure that has a particular architecture.
For example:
Many multiplayer game backends provide a client-server infrastructure.
Many multiplayer game backends use a client-server architecture.
@MooseBoys provides a good summary, however for those looking for a little more detail and examples:
Describes the actual set of components that make up a system.
Typically, an enterprise Information Technology (IT) implementation is built on a Infrastructure.
Describes the design of the components and their relationships.
IT Infrastructures' Architecture first necessitates IT Agility, providing decisions to subsequently explain the infrastructure components' relationships, agility, lifecycle events and more to provide automations, workflows, agility and relationships of each part of the infrastructure.
"IT Agility" also known as "Infrastructure Agility," is an extremely important measurement when designing the IT Architecture to focus efforts of how efficiently the IT Infrastructure may respond to stimuli, while providing an ability to scale the IT Infrastructure in line with the demands of the business, rapidly.
Many multiplayer game applications' backend provides a client-server infrastructure.
"We provide core infrastructure technology services to the campus." — (source)
"A hybrid cloud approach could involve a public cloud environment and a private cloud environment with infrastructure (facilitated by application programming interfaces, middleware, or containers) facilitating workload portability." — (source)
Many multiplayer game applications' backend use a client-server architecture.
"This portability is facilitated by microservices, an architectural approach to writing software where applications are broken down into their smallest components, independent from each other." (source)
"In order for a microservices architecture to work as a functional cloud application, services must constantly request data from each other through messaging. Building a service mesh layer into an application simplifies interservice communication, but a microservices architecture may also need to integrate with your legacy applications and other data sources." — (source)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With