Eventually Consistent HTTP with Statebox and Riak
Bob Ippolito explains how to solve concurrent update conflicts with Statebox, an open source library for automatic conflict resolution, running on top of Riak.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Agile Development: A Manager's Roadmap for Success
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
Anatomy of a Deployment Pipeline – free chapter from the book "Continuous Delivery"
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Hi,
Can anyone explains to me the difference between the three ? I have read some debate about enterprise and technical architect, and now the presentation mention software architect ?
Presentation slides are not downloadable.
+1 Special thanks for mentioning a need to provide a legend for diagrams - one of my biggest pet peeves. I also want to stress that providing diagrams in UML doesn't relieve you from the responsibility of providing a legend, especially explaining all the arrows. UML tools may enforce the standard notation as far as individual elements are concerned, but everyone is still free to arrange those elements in a surprising way, and even assign a different meaning to the elements.
-1 In the beginning the speaker said that he wants us to have a take away that nobody can agree on the roles of an architect. It may be true, but as far as a take away from an hour long presentation - it's pretty weak. In this way, the talk is only adding to a confusion, not helping it.
In many small to medium size organizations Software, Technical and Solution architects are essentially synonymous.
Medium size organizations often equate Enterprise and Solution architects.
In medium to large organizations Enterprise and Business architects may be the same.
In large organizations Enterprise architect is often a chief architect with other architects reporting to him or her.
IASA is trying to standardize those roles but it's still a long way from a broad acceptance. Currently there is still too much variation between different companies.
Hi,
Can anyone explains to me the difference between the three ?
Even at this point in history, definitions are not hard and well-defined, but more or less will follow the following interpretation. I'm sure others will agree and others will disagree, so take it with a grain of salt in the hope that it helps you do your appropriate research and come with similar or better interpretations and definitions.
Software architecture deals with the architecture, the fundamental structures and constrains within an existing software-intensive system (or the structures and constrains that guide the building of one.) Within this concept, some architectures are more common or widely applicable - as a solution - to a class of problems in a particular domain. For example, JEE. Applications that fall within JEE architecture possess what is typically called application-specific software architecture, or application architecture.
Technical architecture deals with infrastructure, typically, but not always, network architecture, hardware selection/acquisition, and the processes by that govern the life cycle of these elements (investigation/selection, deployment, testing, maintenance and decommissioning/replacement.) This domain works closely with IT Operations/Operations Architecture which can be seen (not quite correctly, though) as a liason or in-between domain between Software/Application Architecture and Technical Architecture.
Enterprise architecture deals with how an enterprise is made, organized, structured. It deals with the business units that drive the enterprise (and which justify/enables its existence), the business processes that makes it profitable, and the technology (hardware and software) that enables these processes to operate. It also deals with how business processes drive the adoption or abandonment of a given type of technology as well as (in the other direction) how technology can be used to improve or even change business processes.
Technical and Software architecture are subdomains of enterprise architecture. In large/critical systems (say within the DoE, DoD or in commercial sectors dealing with the implementation of large/critical equipment), you also deal with hardware (electrical, mechanical, etc) architecture and systems architecture.
The later (systems architecture) is the architectural science of bringing architectures and designs from multiple disciplines (software, electrical, mechanical, aerospace, nuclear, chemical, etc) into a solution within an enterprise domain (with enterprise being either commercial or public/Defense/DoE/etc.)
Hope that clears it up.
Enterprise architecture deals withI have read some debate about enterprise and technical architect, and now the presentation mention software architect ?
It shouldn't surprise you much to see a reference to software architecture since that concept is far more common than enterprise architecture ;)
Bob Ippolito explains how to solve concurrent update conflicts with Statebox, an open source library for automatic conflict resolution, running on top of Riak.
Erik Onnen attempts to demonstrate that Java is still the best programming language for the JVM if simplified idioms are used along with proper tooling.
Approaches to integrating data are changing with emergence of cloud computing.
Michele Ide-Smith presents the lessons learned in the process of introducing UX principles and techniques into a large organization through a series of small steps.
Dave Farley and Martin Thompson discuss solutions for doing low-latency high throughput transactions based on the Disruptor concurrency pattern.
Rajneesh Namta shares his thoughts, experiences, and some of the critical lessons learned while implementing software test automation on a recent Agile project.
Dale Schumacher presents several patterns of actor interaction that can be used in collaborative programs written in any language.
Rúnar Bjarnason discusses Scalaz, a Scala library of pure data structures, type classes, highly generalized functions, and concurrency abstractions to perform functional programming in Scala.
5 comments
Watch Thread Reply