Apache Mesos, Apache Hadoop, Apache Spark + Custom Enterprise Applications: This stack combined is greater than the sum of each of the pieces of this stack. Mesos can manage resources across an entire data center, Hadoop provides a distributed data store and scalable data processing, and Spark delivers great in-memory and disk-based performance of data processing as well as streaming capabilities. Couple all of that with custom enterprise applications, and the data center turns into a well-oiled machine. When combined, this software stack delivers unlimited flexibility for the entire data center.
Jim Scott, Director of Architecture and Enterprise Strategy | Strata + Hadoop World | Barcelona, Spain, November 2014
Static partitioning was used to create isolation. This enabled people to know that when a problem occurred what was causing the issue. This is something containers can fix.
Additionally, when we statically partition, we cannot fully leverage all the resources for all the most important work.
Most server types are busy at different times of day, or can be.
Which work is the most important? Whichever is deemed the most important now!
The problem with this business continuity story is that you are still limited to generally scheduled backups and not real-time.
Pluggable, because we need an architecture that platforms can be modeled after.
If we have to rethink an enterprise architecture every time the next greatest thing comes out we end up redoing a lot of work.
These technology concepts are now mature enough that they will stick around and the specific implementation is flexible.
NOTE: The solution architecture can integrate remote platforms and is a conceptual model and thus isn’t necessarily managed by a global resource manager
“Google is living a few years in the future and sends the rest of us messages” –Doug Cutting, Hadoop Founder
Server crashes before a file is rolled and the data is lost.
Leveraging the distributed file system means that the data is NOT lost.
Scales without the pain of figuring out how to move that data, the platform handles it for you.
From the solution architecture perspective this is likely going to be utilized in monitoring the operations of an environment, or perhaps revenue management.
These parts are expensive. They are difficult to test because production is often drastically different from dev and qa.
NOTE: The billing database is an external entity, likely an RDBMS and is still a part of the solution architecture to deliver the business objectives
As pointed out in the advertising example. The billing system is still in an RDBMS. It still integrates via the solution architecture, but the RDBMS is not running on this platform architecture.
The benefits are plentiful
They rely heavily on Borg and Omega
They perform 2 billion container deployments per week
Follow me on twitter to get updates for documentation on the Zeta Architecture