Hey, good morning, everyone. My name is Scott Andreas. I'm an engineering manager at Apple in our cloud services group focused on Apache Cassandra. I'm here this morning to offer a retrospective on where Cassandra has been over the past decade or so and to share some possibilities that recent work like transactional metadata and Accord open up for the database. The features that I'll be sharing today aren't exhaustive, but are some of the ones that I've been a little bit closer to. It's so good to see all of you. I'm glad that we can have an in-person event again. And I hope that we can connect well at the conference. We'll start by framing the context of Cassandra's emergence in the original Dynamo paper. And then I'll take this as a jumping off point to follow how Dynamo derived systems like Apache Cassandra evolved. We'll survey what stuck and some concepts that didn't pan out quite as well, at least for us. And then finally, I'll offer some thoughts on what's new and what I see as next in majority quorum databases. This includes an introduction to the new leaderless Paxos protocol developed to implement cross shard transactions in Dynamo derived systems that execute in one wan round trip, which we call Accord. Other features that we'll talk about aren't necessarily committed, accepted, or even discussed roadmap items within the Apache Cassandra project, but maybe they will be. The question this talk poses, though, is whether systems that begin from humble origins but with a few really uniquely powerful capabilities can build on that architecture as an asset and slowly close the capability gap with traditional databases through about a decade of hard work. You can bet because I'm here today that I think that the answer is yes. So let's dive in. The Dynamo paper and Apache Cassandra, which was modeled after it, were my introduction to distributed systems. I was a liberal arts grad and early career engineer just learning how to build services when a colleague shared it with me. Dynamo described a system for storing shopping cart state, functionality that would have typically been served by a relational database at that time, but in a very un-database-like way. I was fascinated by the path that this paper carved to solve a very specific problem and the set of scenarios that it seemed to anticipate along the way. I'd love to thank all of the Amazonians that are here and everyone involved in that work for what that paper taught me. So what did the paper claim? The paper didn't call Dynamo a database and it seemed really careful in not using that word. The system was a highly available key value store designed with a leaderless architecture focusing on incremental scalability, properties that were pretty uncommon for contemporary databases at that time. The API was very simple. It stored only opaque bytes and let you retrieve them given the key. Availability was paramount for that system and it meant meeting an aggressive latency SLA at the 99.9th percentile. But there's a lot that it left out. There wasn't a query language. There was no query planner or optimizer, much of which was delegated to a smart client. Dynamo had no concept of transactions. There weren't indexes, there was no MVCC, no snapshot isolation. There were no rich data types, no aggregations, views, functions or procedures. The paper didn't even describe a storage engine. It noted that BDB and MySQL were both pluggable options. So if you think about contemporary storage systems that were popular at that time, like Oracle, MySQL, SQL Server, Postgres, these were really glaring omissions for something that acted as a data store. And that paper about 16 years ago sparked a lot of discussion and interest in what became the field of non-relational data stores. Dynamo was successful because it took a use case that typically would have been served by an RDBMS. It framed a very specific set of goals, their availability, latency and scalability. It pivoted its entire universe around those capabilities and then optimized for them with the expensive features that any RDBMS would have offered at that time. And that raised somewhat of an existential question. What is a database among distributed systems practitioners along with some really reasonable eye rolling among people who had worked in the capital D database engineering field for a long time? They were, and are quick to remind the world not to confuse a distributed hash table with a database. But some started to wonder if there were more database adjacent problems that could be solved with an architecture that had unparalleled availability, scalability and latency characteristics and also how much people were willing to give up for it. Crucially, a lot of people agreed with that idea and sometimes a little too readily. If you remember the database landscape around 2010, 2013 or so, and some of the work that followed in Kyle Kingsbury and Jepsen's research, that work taught us that many early data stores from that era were dangerously unsafe and failed to provide the set of properties that they advertised and yet still enjoyed a surprising degree of market success, which surprised a lot of people too. Kyle's still doing this work today and things haven't gotten a whole lot better. This pattern isn't a new one though. If you've read it, Clayton Christensen framed it really well in a book called The Innovator's Dilemma, which featured a case study on the disk drive industry at the time of early personal computers. Christensen identified a pattern and it was that new technology solves a problem in an undeveloped market. It lacks table stakes features that most would regard as critical, but it finds a niche that it can establish itself and succeed in. And then over time, as it gains market share, that technology gains capabilities that are needed to enter minor segments of mature markets, then slowly chips away at that gap while building a moat around what it really excelled at until it can compete with entrenched players. Eventually, those entrenched players retreat upmarket to more sophisticated segments and the new technology becomes firmly established, gaining most of the missing capabilities while renegotiating with the market what requirements really are table stakes. This process of succession maps really well to some of the transformations that we've seen in the database industry over the last decade. Emerging products missing major features carved down a niche, then by time to grow what they lack and move into more established markets, building a moat around what made them disruptive in the first place. And this is where Apache Cassandra comes in. Cassandra was co-authored at Facebook by an original author of the Dynamo paper at Amazon. It took many aspects of the Dynamo design like data placement via consistent hashing, tunable consistency, gossip, hinted handoff, Merkel trees, and timestamp-based conflict resolution. Cassandra added a few features that weren't originally included in the original Dynamo paper, like rich data types and an LSM storage engine. But it sure had a lot of growing up to do. Dynamo's tight framing of its own problem statement was critical to its own success. But what problems faced the Dynamo derived systems like Apache Cassandra try to succeed in today? Most of these are extensions of the design goals of the original paper. For us today, scalability and availability remain paramount with a pretty incredible range from 3 to 1500 database instances per cluster. Availability standards are very high. Dynamo's architecture enables Cassandra to deliver five nines of availability easily and especially with multi-region deployments, six nines or more. This is only possible because all maintenance operations are designed for zero downtime. And we'll talk a bit more about how the majority quorum architecture contributes to that in a bit and why it's so critical that we preserve it. Cassandra also targets wide distribution with databases deployed active active across five regions. It can store many petabytes of data in a single database and serve millions of queries per second. It offers strong consistency and linearizable transactions. There aren't many databases that can do these things in our industry, especially few that are open source. So within our innovators dilemma frame, we've moved up market a lot from Dynamo's origin, which had very loose guarantees and a very slim API. A question that we can ask ourselves is, how far can we push this while building on the strength of Dynamo's scale, availability and distribution characteristics? It's useful to distill some of the most important Dynamo properties that help Cassandra get to this point because we probably wanna double down on those. They're what have really made us successful. For Cassandra, these are Dynamo's leaderless architecture and majority quorum design. The simplicity of the leaderless architecture was brilliant. It avoids bottlenecking on a distinguished transactor. It eliminates the impact of gray mode failures in the case of a leader on failing hardware. Think like a bad disk that's slow to respond or a dead fan that results in thermal throttling that might not otherwise be detected. It eliminates the risk of blips during leader elections or the impact of a failed election or loss of a leader. Quories and transactions can be initiated and led from any region active active. With three or even five regions, this enables Dynamo derived systems to remain available and consistent during even major disruptions to internet infrastructure. Transactions can be initiated from any region with equal latency. And crucially, failure domains in Cassandra aren't global, but they're scoped to a small set of, say, three replicas for a given key. And in a cluster of, say, 1,500 instances, this confines the blast radius of concurrent hardware failure to just 0.2% of the cluster. But individual hardware failures have almost no impact at all thanks to the next attribute that I mentioned a moment ago, which is Cassandra's majority quorum design. This approach was a great design to build a database around. In majority quorum systems, the probability of failure is a function of the likelihood of concurrent failures of replicas across multiple failure domains. That's a powerful concept. Cassandra's data placement strategies can be made aware of the failure domains of the data center and the cloud that they're deployed on to achieve even greater availability. For physical DCs, this means replicating data across rack, power, and networking failure domains. The database's awareness of the physical topology of the data center makes concurrent replica failures incredibly rare. Similarly, control planes that are aware of data center maintenance activities can green light or deny non-essential maintenance like upgrading software on a switch that would take down a rack or deploying a new software release, which can even further mitigate the risk of concurrent failure. This approach maps really well to cloud concepts too with availability zones and regions mapping similarly. Apache Cassandra achieves strong consistency by ensuring that all reads and writes are served by overlapping quorums. And in cases where replicas disagree, locking read repair of the most recent value before returning to the client and publishing that value outside the system. This produces a consistency contract that matches what a user would experience when querying a single machine database like Postgres at a non-transactional isolation level. Together, Dynamo's leaderless architecture and majority quorum designer at the heart of Apache Cassandra's scalability and availability and contributors to the project are designed approaches that enable us to achieve the consistency and even linearizability characteristics of traditional databases. This took a long time. So thinking back to the innovators dilemma example of moving up market by gaining features, let's take a look at Cassandra's evolution of these database-like features that were built on a Dynamo origin. In 2011, Cassandra gained an SQL-like query language called CQL with rich data types as well as secondary indexes. CQL was unique among query languages in that it was designed to allow users to declare a data layout on disk that was optimized for efficient storage and retrieval of what the user had wanted to store rather than something that's meant to be passed to an optimizer for planning and execution. And this is, I think, one of the genius elements of CQL. Like, if you think about SQL, the goal was to refactor queries in terms of a relational algebra that let the database construct a plan and execute it. In this case, CQL's design which focused on declaring the data layout and retrieval strategy mapped very directly the mechanical sympathy of how data was stored on the disk to what the user was trying to access. In 2012, the database properly supported strong consistency and in 2013 added linearizable transactions for a single key in the database built on Paxos which we'll talk more about later. In 2015, Cassandra grew a new storage engine and now Cassandra's gaining strong HTAP capabilities such as deep integration with Apache Spark making it possible to query the database at over 600 gigabits a second which Dinesh presented on yesterday as well as distributed transactions with strict serializable isolation across multiple tables. That's all pretty exciting but what's with this little gap here in the resume? During this gap, the Apache Cassandra project confronted the quality depth that plagued many non-relational databases at the time. This took several years which you might have noticed during Josh's presentation yesterday on the health of the community which touched on some of the time that it took to ship Cassandra 4.0. Becoming a database that competed at the upper tiers of the market really required foundational work to make the system safe and correct. One downside of Dynamo's resilience was that its design can be devilishly good at hiding inconsistency and fiendishly hard to investigate what happened after the fact. Property-based testing was among the most effective strategies that the community adopted to address these issues. These tool chains worked by fuzzing a Cassandra cluster with randomized queries and schemas while keeping track of the responses that the database that the client has observed from the server. These responses provide a signal to the model that enable it to differentiate between what should have been allowed to happen versus what could not have happened inside the database. Some examples would be that acknowledged writes can't be dropped and must be observed by later reads or that timed out writes may or may not be visible to a later read because they're indeterminate. Maintaining this model provided the basis for asserting correctness, a test that's great when paired with fault injections like cluster restarts, range movements and instance replacements. These tests can be executed both on a developer's workstation or at scale in the cloud which really helped the project improve reproducibility given deterministic seeds. Simulation was another technique that project contributors adopted. And this one was invaluable for validating the evolution of our Paxos implementations. By simulation, I mean generating randomized input then taking full control over the execution of Cassandra and modeling it as a single threaded program taking control of all aspects that could introduce non-determinism like time, like disk IO, like thread scheduling activity and lock acquisition to give you what effectively behaves as a single threaded database. This means that from a given seed regardless of the hardware or operating system platform execution of the suite is guaranteed to be completely deterministic. This is a really powerful primitive. In the context of Cassandra's transaction subsystem we simulate thousands of hypothetical clusters and topologies and millions of Paxos transactions paired with a verifier that asserts the linearizability of the result. Simulation enables at scale fuzzing of consensus algorithms with near instant local reproducibility. This has dramatically improved our ability and confidence in evolving Cassandra's Paxos implementations. These techniques have also helped us identify and resolve over 30 critical bugs that resulted in data loss or incorrect query responses. And today provide us tools to think with while we develop new features in Cassandra. In the early days, the project also used to deprecate features in a manner that required action for many users and resulted in users often running database versions that were somewhat far behind the most current release. But we learned that heavy deprecation of features forces work onto those users work that they often won't do or can't do in the event of a vendor deployed product that uses Cassandra, which means that the project risks losing those users. That meant finding strategies to carry forward some previously deprecated features to enable drop-in upgrades across versions, something that we value pretty highly today. And finally, we had some reflecting to do. We've come this far, but what features are we missing? There's a lot of good stuff ahead, some of which you probably heard about so far this week. You might have heard from Piotr's presentation that storage-attached indexes are coming to Apache Cassandra 5.0. SAI is a scalable partition local index. These indexes achieve feature parity with existing secondary indexes, but with much better performance, storage, and operational characteristics. Because they're implemented as SS table components, they get zero copy streaming for free, meaning they get shipped straight over the wire at link rate rather than triggering expensive index rebuilds as they're streamed in. The initial release adds support for AND queries, numeric ranges, fixed-length numeric types, text indexing, and quality queries, as well as optional case sensitivity and unicode normalization. Soon, we expect to incorporate prefixed like and or queries that you might be used to in other databases, as well as case sensitivity and unicode normalization. In the same way that Cassandra moved upmarket from a Spartan feature set 10 years ago, SAI will enable indexes to rapidly gain new capabilities through incorporation of other functionalities in Lucene's search and indexing libraries, another Apache project that the Cassandra community can greatly benefit from. Transactional cluster metadata is a down-to-the-studs remodel of cluster membership in Cassandra that's designed to resolve some of the databases oldest and most persistent problems. As Alex presented yesterday, Gossip and Epidemic broadcast were NVOG around 2007 Distributed Systems Research, and their fun techniques and solutions for systems that might have 100,000 or more nodes, but that typically doesn't describe almost Cassandra deployments. It was impossible to build correct and reliable state machines on Gossip because that model relied on one node deciding to do something, like claim ownership of a token and stomping on it, and then telling everybody else who then have to take compensating action as they learn. You can't build a great state machine on that. TCM enables safe and rapid modifications to cluster state, which improves Cassandra's elasticity. It eliminates schema divergence. So if you've ever found that schemas diverged after making rapid DDL changes, or maybe you used a library like Liquabase and then had a mess to clean up after, this is a problem that just simply won't happen anymore with transactional metadata. And if you've got a lot of scaffolding that orchestrates operations in Cassandra, like instance replacements, repair upgrades, and so on, this work may enable the database to take responsibility of some of those features and some of those in future releases. But this last one here is likely to be pivotal to the future of Cassandra. Today, Cassandra distributes data based on tokens, usually via random partitioning. Ordered partitioning is necessary for cross partition ordered scans and joins, but to do it as a database, you have to be able to split hot or dense ranges. TCM provides the machinery that might allow for efficient range splitting in a future release, as well as a transition from token ownership to range based ownership where those ranges could be redefined and moved. This is gonna be a super heavy lift, but if we complete it, it would enable Cassandra to become a completely new kind of database, pivoting from being a multi-dimensional unordered map to an ordered map, much like Spanner and DynamoDB. Next is witness replicas. This is a feature that was controversial a few years ago, but I'd love to share more about why I find it extremely important to the future of Cassandra. If you've ever had an exec or finance partner come to you and say, we need to get our cloud costs down, you'll probably care a lot about this. This feature could save you about 30% on your storage costs. Today, Cassandra couples quorum size and replication factor. They're the same to the database. That means that if you have three replicas and three data centers, you're paying to store nine copies of the source data. And if you deploy on top of a replicated block device like EBS that replicates data of further two X under the hood, those nine copies of data are actually 18 copies of the original data. This is incredibly inefficient. Witness replicas build on a fundamental invariant of incremental repair. IR guarantees that the repaired set in Cassandra is immutable and consistent across replicas. Because the repaired set is guaranteed to be identical across replicas, there's no point in querying more than one copy of it. This means that we can drop the durable RF from three to two without impact. And then we only have to read one of those copies as well. Quorum reads are guaranteed to be consistent if they include one consistent copy and a quorum of the unrepaired sets. So this feature shift is experimental in Cassandra 4.0, but contributors are working this year to bring it up to scratch and to remove that experimental tag in a future release. So please do not go turn it on now, but think ahead. Saving 30% on storage is a pretty big deal and we hope to have more to share in a year or so. Distributed acid transactions are our next focus. Some of the design goals that we've established are as follows. We think users should be able to transact over any subset of keys in the database, including across tables. We think that Cassandra should support strict serializability, the strongest level of isolation possible. We want to achieve optimal latency, one one round trip for all transactions under normal operation. We also want optimal fault tolerance. The latency and performance must be resilient to a minority of replica failures. In terms of scalability, we don't want a single point of coordination or a bottleneck introduced. We also value portability as an open source project. No specialized hardware should be required by the feature. All of these sound like some of the capabilities that Dynamo was built around and a lot of that are what you see echoed today in our design for the feature of distributed transactions. To achieve this, project contributors have designed a new Paxos protocol that's harmonious with Cassandra's architecture called Accord. The name Accord is a nod to Leslie Lamport's part-time parliament paper that introduced the original Paxos algorithm. Here, adapted to broker consensus between parliaments or sets of replicas that form a consensus group. Think of the name like a grand bargain between parliaments. Enabling transactions over the whole of the database without a leader means that members participating in the Paxos round may vary from transaction to transaction. So when I say leadership here, leadership is scoped to the coordinator of a single transaction, just a single query. Accord achieves this via a hyper logical time and without specialized hardware or time distribution infrastructure. Transactions execute in one round trip if a sufficient number of replicas are available, falling back to two round trips in rare cases. We validated the protocol by specifying a formal proof of the design and asserting linearizability by a simulation of millions of transactions and thousands of logical clusters in the software as implemented. But that still doesn't mean that everything's perfect. So we've continued to collaborate with academic researchers who have identified a couple additional problems with the protocol, then suggested solutions to those. I've never received a bug report in my career in the form of a three page LaTeX typeset document. And it was stunning to get that from a group and then say also we can fix it. So we value that research collaboration very much as well. There's a link to the paper on this slide. You can also find it on the Apache Cassandra Confluence Wiki. So a lot of distributed databases use leader oriented protocols like a distinguished transaction manager, multipaxos or raft. Why is Cassandra thinking leaderless? Well, that comes back to the Dynamo architecture again, which presumes no distinguished nodes. This means that every instance operates as a peer. This eliminates bottlenecks on a leader. It avoids gray mode failures and it leaves a path for scalability if you bound the size of the consensus set that you're transacting over. It also preserves the design simplicity of the database that's the heart of about everything that Apache Cassandra has achieved. For multi-region applications, it also enables initiating transactions from any region with predictable latency. Active, active apps can issue transactional rights from any region without having first to route them to a primary region, unlike multipaxos. Finally, accord achieve single round trip latency, meaning the same network latency that you would incur from a reader right at quorum. This speed improvement down from four round trips for rights just a year ago will make a new class of applications possible. And when you think about distributed transactions or even just a linearizable right becoming as cheap as a quorum read or quorum write, that opens a lot of new possibilities. So I shared this slide yesterday during a keynote with Patrick and Ekaterina, but I'd like to zoom out a bit from the protocol to think about what impact this work can have on Apache Cassandra as a petabyte scale database in relation to the wider field. With this work, Cassandra will become the only distributed database that can scale the petabytes of data, offer strict serializable isolation, can be deployed in any data center or public cloud, offers the availability and performance advantages of a leaderless database, and single round trip latency for transactions whether single key or multiple, local or remote. This slide doesn't mean that Cassandra is the very best database for all applications. There are tons of other characteristics that one could optimize for that aren't captured here. But the set of capabilities is incredibly compelling and something that we wouldn't have expected to be possible at the outset, and something that I certainly don't think was anticipated by the Dynamo paper about 15 or 16 years ago. But there's a lot ahead. There are a lot of new possibilities that distributed transactions open for us. Strong transaction primitives open new possibilities for Dynamo derived systems like rethinking indexes. An index could be modeled as a transactional mutation to a base table and a derived table. The transaction subsystem composes well with SAI today and might allow us to build even more on top of SAI in the future. They let us rethink materialized views, a feature that the project needed to retroactively classify as experimental. You could think of modeling a materialized view as a transactional mutation to a base table and a derived table with a predicate. They provide a basis for enforcing foreign key relationships within the database, something Cassandra's never been able to do. They could be a primitive to enable Cassandra to support multi-version concurrency control or even snapshot isolation via something like an epoch visibility protocol. Autobalancing data placement solves the biggest problem with Cassandra's byte ordered partitioner. This lets us reimagine Cassandra as a multi-dimensional ordered map with keys sorted within the cluster according to their lexical sorting. Snapshot isolation and ordered partitioning are building blocks that could enable the database to support features like cross table joins. This may enable Dynamo derived systems like Cassandra to support a large number of even relational use cases. All of these things can be possible by reimagining a Dynamo derived system as a transactional database. So we've come back to our frame, a cycle in which disruptive innovation slowly moves up market after carving out a niche and gaining new capabilities while building an impenetrable moat around the core competency like scalability and availability. But the news isn't all good because when you get to the end of the book you see that once you reach the top there's usually another technology that's maturing right behind you. Some example modes for future databases might include things like hard multi-tenant isolation, making exceptional use of tiered or disaggregated storage or full SQL support. I think that all of these could be built in Apache Cassandra, but they're things to think about because you've always got to watch your back. Until then though, we should be really proud of what the Dynamo architecture has enabled us to build. A database that can serve petabytes of data and millions of queries per second with up to six nines of availability. One that can replicate active active across five regions. One that can be deployed in any data center or public cloud without specialized hardware. One that can execute leaderless transactions across the entirety of the database from any region. And one that can be downloaded, learned from or modified by anyone. That's a great foundation to build on. Thanks all of you for your time today. It's great to see you here in person. We've got about three and a half minutes for questions if there's anything that folks would like to ask. Thank you. That's a great question. The question was do you ever, as you evolve the database and gain new features do you ever risk forsaking the foundations or straying from what you were? I think that in any software system there's always kind of a constant renegotiation of identity that's usually based on where you've come from and what you need to become. And now and then some of the things that you valued in the past might matter a little less in the future and need to be rethought. And there are some examples of that in Cassandra's history like replacing some foundations like gossip with things that are fundamentally transactional. There's been a shift from a focus on eventual consistency to strong consistency and linearizability. I don't think of those things as necessarily forsaking the history of the project so much as becoming what we need to be in light of where we've been. You mentioned relational, Scott. Can you talk a little bit more about that? What sort of use cases Cassandra might be able to address and which ones it may not? That's a great question. So I think that if we were to try to bite off becoming a fully relational database at least right from the beginning that probably wouldn't be a good lift. But if you think kind of about that frame of negotiation with the market of what features are required I think that there are a lot of semi-relational capabilities that are really easy for Cassandra to gain. So if you look at APIs like DynamoDB which aren't fully relational but which do allow for some cross-table activity or cross-partition activity people have been very successful in building on top of that API. So if you look at distributed transactions as features that allow you to enforce things like referential integrity constraints across tables or the possibility of a cross-table join if we were to move to ordered partitioning in the future I think that people can express a very high degree of traditional relational applications in the database. That's a bit different from having a full ANSI SQL grammar that's capable of common table expressions and 14-way joins and aggregation that you might have in a more traditional Oracle style database. That's probably not a good goal for Cassandra but I think it gives us at least a path to move a little further up into the right. 50% of the relational market, maybe by volume. We've got about 30 seconds for one more question. One other feature that's new to Apache Cassandra that people may not know and it's pertinent to this is Vector Search. Absolutely, thank you for mentioning that. There's so much that's in 5.0 and coming after in 5.1 that it was difficult to get all in one presentation. Vector Search I think is a really great example of Cassandra building upon capabilities like SAI to evolve features that are coming and needed by new markets like artificial intelligence. Thank you all so much. We've just hit our time but I would be happy to connect with any of you in the hall and would love to chat with you at this conference. Thanks again.


This 2014 Ram 1500 Crew Cab Short Box with the Ram Box is stock number 11949ZA. We're here at Summit Automotive in Fond du Lac, Wisconsin, you're new and used light duty truck and Ram headquarters. This 2014 Ram 1500 has the 5.7 liter V8 Hemi motor. This truck has been fully safety and inspected by our service shop. It has a fresh oil and filter change, all the fluids have been checked and topped off per the state of Wisconsin inspection process. It has four brand new tires and this truck is 100% ready to go. Bright white clear coat is the color we shoot all of our videos in 1080p 60 frames per second. So if you have HD capabilities on your computer, tablet, smartphone or television, turn them on right now because it is definitely your best way to check out the quality and condition of the truck before seeing it in person. And if you like the video and want to check out more of our videos in the lower right hand part of the screen is a link to subscribe to our channel. Click that and then click the bell notifications and you'll get updated every day we do videos here at Summit Auto of our amazing new and used inventory. So this one's a big horn but it comes with the very nice polished aluminum 20 inch rims. And it has brand new Goodyear Wrangler SRA 27560R20 tires. We put these on in our safety inspection. You can still see the little wear knobs right there. So brand new tires all the way around, front fenders in excellent condition. I didn't see any dents or dings on that. Headlight lenses are nice and clear and the front bumper is in really nice condition as well. I didn't see any major dents or dings on there. You get the chrome trimmed grille and the hood is in pretty nice shape. It's pretty good. Passenger side front fender, no dents or dings on there. And the passenger side rim, no major scuffs or scrapes. This tire is also brand new. And as you go down this side, the truck, take note of how clean the body is, how reflective and mirror like that paint is. We take these HD videos so if you are far away or even if you're close by and just cannot make the trip down but you're still interested in purchasing the vehicle you can see the truck, hear the truck and have confidence in what you're looking at before you even get here. So when you do get here there's absolutely no surprises and you can make a smart and informed decision from the comfort of your own home. Those doors look pretty good. Back rim is in nice shape. Back tire is brand new as well. And it comes with the plastic wheel well liners which is nice because it keeps your family and other body looking pretty good. And for a seven year old truck, not too bad. Little rockers do have just a little bit of corrosion on the edge there but it looks just like surface rust. Does come with the ram box, has this nice storage bins in here and it's been used. It's a truck and you do get plugs down there for draining so you can put ice and drinks in there. You have two coolers wherever you go. Coming around to the back rear bumper looks pretty good. It does have the full towing package which includes the receiver hitch four pin and seven pin wire and you do get the chrome tipped dual rear exhaust. The tailgate is in pretty nice shape. Does have the locking tailgate and back up camera. Has a linex sprain bed liner and that is in nice condition. You do get the side box rail system and you can get cleats for those and tie downs and whatnot. Tailgate has got a couple little scuffs and scrapes but nothing too bad. Down the driver's side box looks pretty good for full disclosure this back rim, no major scuffs or scrapes on there and that back tire is brand new as well. Down the rest of the side of the driver's side looks pretty good. You get heated power mirrors with the built in directional signals inside the big horn package gives you the gray cloth interior. There are no rips or tears on the seats they're in pretty nice shape. Power driver's seat with lumbar, factory floor mats throughout, auto headlamps, power windows, power locks, power mirrors and these mirrors do power fold in. I always like showing both sides that they're working because on a used vehicle you never know. We'll hop inside take a look at the ignition and the radio. You can see that this one has 94,618 miles you do get the 7-inch LCD display, digital speedometer, outside temp, compass, range to empty and a gain for your brake controller. Comes with the heated leather wrap steering wheel that's in really nice shape, cruise controls and gear selector on the right, Bluetooth and information center controls on the left. Comes with the 8-speed automatic transmission push button 4-wheel drive comes with the 8.4 3C radio with the factory navigation system. You do get AM, FM and serious satellite radio capabilities. You can also do your heated seats and steering wheel buttons right there. This one does have the Alpine premium sound system so you get the speakers in the ceiling as well as the subwoofer and back factory brake controller. They're your more tactile climate controls. You can do your climate controls down there or you can do them up here on the radio and this is also where your backup camera shows up when we start the truck. I'll show you that. 115 volt, 150 watt plug-in. Carpeting is very nice and clean. Passengers side format and seat are in nice condition as well. No rips or tears on the seat. Headliner is in pretty nice shape and there are those speakers in the ceiling. You do get map lights, power side and rear window button, home link buttons for your garage door security systems and lighting systems and 911 and assist buttons in that rear view mirror. We'll take a quick look at the back seats and then we'll start it up and take a look under the hood. Back seats are in pretty nice shape as well. No major rips or tears back here. It does have the latch child safety system for any child car seats you may have. Power sliding rear window. Get that factory floor map back here as well.  If you've got muddy boots or tools, put them on there. You're not going to get your seats all dirty. And if you've got pets, you can put both sides down and they have a nice flat place to lay. You also get storage underneath the load floor there. And you get in-floor storage on both sides with removable containers. You can put ice and drinks in there and then you have even more coolers to haul around. Child safety locks on the back doors. Bottoms of the doors look pretty good. And we'll start it up and take a look under the hood. Starts right up. No check engine lights or anything like that. Does have the backup camera right there. I would personally like to thank you for checking out the video today. And hopefully from this HD video you've gotten a really good idea of the overall condition and quality of this truck. Under the hood we have the 5.7 liter V8 Hemi motor. Engine bay is very clean, runs very smooth. Once again this truck has been fully safety and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off. See the shocks are doing a nice job holding that hood up. There's your emissions sticker. It has four brand new tires. And this truck is 100% ready to go. To see more pictures of this truck or one of our other 450 new and used cars, trucks, SUVs, minivans, Wranglers, halftons, recorder tons, wontons, you name it. You've got to go to that website right there at www.summitauto.com, full pictures and descriptions of every single vehicle from two locations all at www.summitauto.com. And if you'd like to check out more HD videos you can go to www.youtube.com slash www.summitauto.com. Remember to like, subscribe and share on this video and all the videos that you see there. And click the bell notifications to get updates on the videos we do each and every day. In fact in a second you will see a link to subscribe to our YouTube channel in the upper left, a link to more Ram 1500 truck videos like this one in the upper right. Link to this vehicle on our website in the lower left and a link to one of our latest YouTube videos in the lower right. Click those check us out and we're super excited to help you with this ultra clean 2014 Ram 1500 Crew Cab Short Box Ram Box Big Horn in bright white clear coat. Thanks again for checking out the video.


Alright guys, this is Matt Beck from freesaloneducation.com, and we are on the road with Millennium Systems International, right? So we're gonna discuss the name change from, it was Harm Software, right? Yes, it was Harm Software, yeah. So now we're Millennium Systems International, with John Harms, founder, and Bob McConie. And we're gonna discuss Bob's official position. I'm not here to tell you what that is, so we're gonna, what I want to talk about first is, I want to thank you guys for having me here, and we talked about it on the podcast this morning. We do a podcast for hairdressers called Splitting Hares, and we do it every week. And we just sit around, we talk about celebrity hair changes and all kinds of stuff. So we did talk about some things that are coming up with Millennium, so I want to go over that real quick during this time, and then, yeah, we'll go from there. But let's start off, and I guess I'll kind of toss this towards both of you, but I want to talk about when you, I guess John first, when you were first thinking about creating software, right? Was that something that you were passionate about from the beginning, or how did it develop? Yeah, basically the passion for software happened when I got my hands on a computer, and back then didn't have internet. Yeah, I was gonna say, what did that computer look like? Yeah, well, it hooked to the television, yeah, it hooked to the television, first of all. And then you would go to the library and copy down lines of code, because you didn't go on Google, there was no Google. So I'd write down all these lines of code, go back, crank them into my computer, see what they did, watch what would happen if I changed things on that code, and I just fell in love with it. So yeah, I was about 16 when I started teaching myself how to code. Okay, and then, so basically for hairdressers out there, coding is just what tells the computer, right, what to do. Yeah, writing a bunch of gibberish that then makes cool things happen. So everything cool that they're playing with their iPhones, everything, it all comes from words, right? Words and software, and when you get down to the basics, one's and zero's, that's it. Okay, so tell me about, so you developed, you decided to develop software, why was that? So basically to pay for college, I mean I was coming, I was a senior in high school, was gonna be, I got a partial scholarship to college for computer science. My sister was a stylist, and long story short, they needed software, and that was the first salon I ever wrote software for, it was called the Village Salon in Tannersville, Pennsylvania, and helped pay for one semester of college. Nice, so tell me, so your sister was a hairdresser, I remember when I first started the salon, I worked at 10 years ago, we didn't have software, and I begged and begged for them to get software, and the owner was like, I don't even know how I can deal with that.  I can imagine if it was coming from a sibling, you'd be more into it than, just some young stylist telling the owner to get. Not really, yeah, I would love to say that, no, I mean she knew that I was pretty capable and was excited about me starting to write software for the industry she was in, but honestly, if you think back to 1987, which is the year this would have been, very few people were computerized at all, there wasn't even Excel really yet, there wasn't next to anything, so the thought of doing any appointment booking or color formula tracking on a computer was pretty out there, believe it or not at that time, so she really knew, probably didn't even fully understand what I was gonna go there and do, to be honest with you. Well that's what is so interesting to me, I guess, because I love creating some kind of company, so I look at the fact that in 1987, people didn't even have computers in their houses, let alone software in their salon, so what in the world in your mind was thinking, yeah, I'll create salon software and maybe we can get computers into salons and then we can get software, so I can only imagine, so my next question would be, and I know anybody starting a company or a salon or anything when they're looking at doing that, in the first year, the second year, it's all a struggle, so was it a struggle, what made you keep going through it and to develop what you have millennium today? The great thing is I was 18 years old, I was young, there was no thought in my head that I couldn't do this or that everybody in the world wouldn't want what I was gonna create and that's the beauty of being young, I can't imagine doing what I did 25 years ago today and taking that risk, so for me it wasn't even risk, it's something I loved and the thought, I remember thinking how amazing it would be that I could actually do something I loved and make money, and you start small, I hope it can help pay for college, I hope it would help me buy a house someday and then you hit a point, which we'll get to in a second on why we changed the name of the company when it really becomes more about everybody else than yourself, but at the beginning it's just about, man I just want to be able to eat and have a house. All right great, so Bob, so let's get into Bob here, so Bob came along when, so in 1996 and he actually was one of the early adopters back when I was building this even though he wasn't using salon solutions it was called at the time, he was actually an early adopter to computers in the salon which was very unusual. Salon solutions was what you were calling it? The first product I wrote was called Salon Solutions. I was automated for about two or three, maybe three years prior to meeting John, but an old DOS system which was really limited in its capabilities but that's how I got into it.  I remember that because I remember going there as a kid and eating donuts waiting for her to get out of the classes. I was excited to go, that's how far back my memory goes with that, but it was interesting. But yeah, she, as we grew up, there's three, I had two other brothers, she raised all three of us on the beauty. She was kind of alone, so she went to school, got a degree in style, I got her license and started working and that's how I got involved little by little.  Yeah, I got married and my mother at, and my wedding didn't really give us a wedding gift. She says, don't worry, I'm going to take care of you. And then a little while later on, she had built, she was in the process of building salons in New Jersey and she built a really big one down south Jersey called Shampoo. Okay. And then she said, here's your wedding gift. And she gave me an old senior citizen in Washington, brown paddling, four station, the big beehive type dryer. And I'm in construction. I don't know anything about running a business in this salon. My wife's just getting out of cosmetology. So that's how, yeah, I'm sure you're, you were super excited about it, but look what it was scary. It was scary going into a business. I knew nothing about it. I was at the time and little by little, I started going to trade shows and I got a software and then then I met John. Okay. So then John, why, when did you change the name to Millennium from Salon? What was it? Salon Solutions. So Salon Solutions is the first product that I originally wrote 100% on my own. Okay. And that was until 1999. And then with the new Millennium coming, we needed, we, I started to write with a couple other people collaborating now to create something even bigger and better than Salon Solutions. So I decided to call Millennium because it was coming to the year 2000. Everything was about, you know, the new Millennium. Okay. So that's, and I also wanted to get away from anything that specifically spoke to only a certain industry because I knew we were going to be selling to spas, and medical spas, and, you know, even though salons have always been our sweet spot, you know, people that in a spa don't want to buy something called Salon Solutions necessarily. So it was a generic name that allowed us to really hit the beauty industry as a whole. Nice. And then what do, so let's talk about, you changed the name. So I wanted the name of the company, the name of the company, right? So it's still Millennium, but now it's Systems International. Well, the company was Harm Software. And so the real story behind that is I started talking about it about four or five years ago is, you know, as we went from 10 people to 30 people to 50 people to 100 people, and keeping that culture tight that's so important to us and trying to make it a place that I'd still want to come to work at if I didn't own it. Right. It was really important to me. So as we continue to grow, I realized that this Harm Software really started to bother me because I wrote Salon Solutions all on my own, you know, Millennium. I wrote half of it probably. And the new system that's coming out Mevo, I wrote next to nothing in it. Okay. So it's really about the team. And I wanted to portray that. So and everybody started to know us as Millennium, Millennium, Millennium anyway. So I said, it's not about harms. It's not about me. It's about the company. So we changed the name to Millennium Systems International. And that's the thing that I've always loved about hanging out with everyone from Millennium, because I feel like I've been to the experience a couple times, which we'll talk about in a little bit. But I just feel like that was kind of it's my thought process as well as why I never named my salon, the Map X Salon or anything I do you don't really see my name on it so much, because I feel like it is about it takes more than just one person. I'm not the only one here today, you know, and it's just there's a whole team behind it. So I loved it. You guys have a company like that. And that's what has become especially after as it's growing. It's like it's growing and it's gotten to this big. And now you're like, you know what, I'm going to take harms out of it because it's huge. Yeah. You know, normally they'd make their name bigger on it. So I think that that's it's really all about everybody else here that works so hard. And and you know, again, early on with Bob coming on board, you know, just the relationships he's been able to build, you know, I'm a software guy. I always joke around that I'm schizophrenic because I can actually really hang out with hairdressers and understand them to the right brain. Right. The left brain. I write code. So, you know, I write software. So that's impressive.  Well, I know in every event I've been to I see Bob and he's always mingling with everyone. So yeah, it's cool. Yeah.  Bob Harms. And they go right by me. I love your company. What you're doing with it. He's like, it's my company. No, I don't ever say that. But the Bob Harms part, Bob Harms, that is fun. We get mail address to Bob Harms. Yeah, nice. He loves that. Oh, that's great. So I guess last couple of questions. This one's important to me because I have I have a young kid. And I know that you have children and you have your children are here. And so tell me throughout this this venture, how did you find the balance between the career and being at home or or just all that stuff? I think everybody's gonna that's listening to this is going to have that same thing even as a hairdresser, the hours that you got to do Saturdays are your best day. So it's tough sometimes. Definitely early on, my wife was very understanding. She used to we were just joking around. She used to bring broccoli and gavadillos to the office at 10 o'clock when we were there and I'm coding and he's testing and eating. So you know, I think with even for the hairdressers and the owners out there, it's we all do the best we can do. And I think the thing that's best for me is to involve my family in it to an extent where, you know, the only thing is is my wife will tell you that dinner becomes kind of boring, because now it's all about the company sometimes. Yeah, you know what that's like. But um, but that's that, you know, the balance is important. But finding time for my family, anybody that knows me knows I'm all about my family.  So it's cool. Okay, last couple of questions. What excites you the most about technology? And I actually have a really good idea that I want to pass along to you. But I don't know if I should tell you in private, I was telling that on the way up. I'm like, maybe we don't want other people to know this idea. But what what excites you the most about what's happening with technology now? Okay, so technology is changing in a really cool way, especially for the beauty industry, because if you think about the way software used to look, you know, you look at spreadsheets and you just look at these kind of gray looking screens, they actually call the battleship gray, you know, the old windows. And what's exciting is the tools that they're offering up to developers now allow like a graphics designer to create something absolutely absolutely beautiful. And then we code around that. So what's great and exciting and technology for me is the cloud and begin to pull all these different things we used to do in 20 different spots, including accounting and social media and marketing and and running my business into one solution. So that's exciting. But the most exciting part of it for what we do here is the beauty of what we're able to create now. Right. Absolutely. I agree 100% with the way we're creating our new software with the Mevo. I got I got a chance to play with it. I just took it to a show just to debut it. And it's just amazing, beautiful product that people want to touch it. Actually, you want to come up to it and just start touching it. Well, anymore, it's more it's it's probably, I would say 70% about the look of it. And then then the functionality. And what I like is that you guys haven't this was two years ago, I know you were talking about Mevo and doing a kind of a soft launch of it. And it was it's you're perfecting it.  I mean, I my favorite thing is I've had companies contact me about software. Obviously, I won't name who that is. But you know, I'll start asking them questions because they'll get me on the phone. And they just don't they don't understand the guts of what software is. It's about education. It's about teaching your because who cares if you can put a frequency of visit number in your software or if you can't teach people what it is and what it's all about. Then it doesn't matter. So very, very cool. Oh, and my idea is if you have so Google Glasses, right? So I'm thinking, well, what if I had Google Glasses on my client walks and I can totally tell who she is, what her formula is, and it's all telling me right in my glasses, right? Yeah, you know, it's funny. I'm everybody thinks like I would just be like that total technology guy. Yeah, I don't have a Facebook. I I write my no no pads, like little sticky pads, right? Like, and I will never wear Google Glasses. I won't either. I'm just what that is a very cool idea. And and the watch stuff that's happening. You know, for me, though, I think I think I even have my limits. You know, at the end of the day, I'm more in love with the business of beauty than the technology to be quite honest. And I think that's been part of our success as well. Exactly. We recently graduated to your calendar on your phone. I actually just in the last couple of weeks, actually, I'm using outlook on my smartphone now. Okay, yes. All right, I'm advanced. Okay, so let's what's coming up with Millennium Systems International? Anything big? You want to talk about? Our big thing is really the whole company is revolving around Evo. I mean, and you're right. If you look at what happened with the healthcare.gov and all the stuff, if you rush this stuff, yeah, you can fail. And that's just not an option for us. So we've had this thing in testing. We've we've been, you know, building the product, adding to it, making it faster, making it better. And so we're really excited about the full blown launch of it in one month. Okay, so in one month, it'll be out and and we'll have full specific date on that March 1. Oh, yeah, we're boarding people and it's for real. All right. Very, very cool. Okay, so so that's exciting.  So do you want to just talk about what's going to be really cool there? Well, Bob's going to be the keynote. We didn't tell him. Okay, so congratulations. Bob loves to speak. Bob Harms will be up there. All right. See somebody faint on stage. Have me. Yeah, we might actually do that as an opener. That would be great. So see, Bob's Bob's good one on one with people. I'm good in front of a lot of people. I'm not good. Well, I'm the opposite.  Yeah, yeah, exactly. I've done it once. So experience. We're very excited about it. We do it every year as you know. And people go not knowing really what it's about. It really is the probably the in my opinion, one of the most well rounded events in our industry where you're getting the the business side of it, the fun side of it, hair shows, people like yourself that are speaking. We don't bring in people that talk that don't understand our industry.  And and I think the reason our software is as good as it is in our companies where it's at is we listen to our customers. So when we're at the experience also, as much as we're giving, we're listening and getting back and making the product better. So the experience for us is something we looked we we look forward to. But at the same time, it's just so much to put on that kind of an event that you guys have a busy few months. But yeah, it's exciting. So yeah, we I was telling everybody on our podcast this morning that every time that I've been there, the thing that I love about it most is not a hair it's not a hair show of 5000 people where you can't get close to the artist. It's a very intimate, you know, 1000 people very intimate. Everyone feels we're all having lunch together. And I just love I love everything about the event with a lot of new friends. Exactly. And a business mind. And I'm pretty proud of the caliber of people that go if you think about the people that go there. It's really the people that want to learn more about the business of beauty and the hair side of it to and listen to somebody like you. But what you're what's great about you and I'll give you a plug though is what I love about when Matt said our conferences that, you know, he's cutting hair, he's explaining the stylist side of it. But at the same time, talking about retention, frequency of visit. So that's what our conference is really about. Yeah, that's awesome. And we and it's funny because your conference is the first one I've been to where it's out of resort. And at noon, you go to the pool, and no one's there. Yeah. It really is like they're actually loaded in the classes. So I'm excited to see what's going on this year. And I'm sure there'll be more to come from that.  It's June. I'd have you plug your Facebook. Oh, yeah. 20 seconds to the 24th. We'll be posting it all over the millennium experience. I'll put a big, big huge ad on the front of our website and everything. So thank you guys so much. I always I love being here. Honestly, I just got away from the salon so that I could be here. Well, we love when they tell us you're coming. Everybody gets excited. It's funny. So thank you guys so much. Check out millennium si right.com. Okay, I thought so. I didn't want to mess it up this morning, but millennium si.com. Check them out on Facebook as well. Follow us on Facebook, free salon education. And that's it. Great. Thank you. On the Facebook or the Twitter. Yeah, I don't I don't have it. All right, guys. Thank you so much for watching and we'll see you on the next episode. Today, everything changes. Hello, world. Meet Mevo.


case study of Pakistan, specifically in context of terrorism and the topic we are going to discuss and we are going to understand that what type of Pakistan, what type of challenges Pakistan is facing for the last so many years. A wave of terrorism, which Pakistan had to face specifically, its root causes, we see that the developments in the world, they influence the Pakistan's social fabric. And how they have influenced the social fabric of Pakistan, because the terrorist activities in the world were said that they match some ideological factors within the factors existing in Pakistan. So, if we look at that space, what were the ideological factors? Definitely, it is a debate that has been propagated internationally and its implications have come from the society of Pakistan. So, we can say that in the case of Pakistan, to fight against an unseen enemy is unknown for the opponents. In Pakistan, especially after 9-11, a theme of war and terror was introduced. So, in the minds of many people, this was the question of who we have against the war, that who is the enemy. So, when a war is fought against an unseen enemy, its implications, its complications are specifically raised in the social fabric of Pakistan. Because Pakistan, like other societies, was not fully equipped to counter this war. Because, like the whole world was not ready in the case of Pakistan, we were not fully equipped for this nature of war. So, it took time to have preparation and to make counter-narrative against terrorism. So, we also took time to prepare and to counter the philosophy of terrorists used to create a situation even in the case of Pakistan. So, Pakistan is also a country that had to face a lot of consequences. And we also faced a lot of sacrifices, military-related people, civil society, which was common in our society. We also faced a lot of losses, not only in the name of the life, in the name of the casualties, but also in our overall society. There was a phase that was not created in that way, which was before the specific entrance of this war on terror or 9-11. We are from a representing and heterogeneous society. We have a lot of variety of groups. These groups have their own ethnic identities. We have religion and Islam. But the sects that exist in these areas have been living here for centuries. But as a result of this war on terror and specifically the groups that used it and influenced Pakistan's society and its consequences, within the Pakistani society, the further deviant of our society, and we have endured a lot of losses. As we can say, we endured the loss of our lives. Along with that, we also had to face the loss of Pakistan today. Along with that, our social context changed completely. The society in which people used to live, but now especially because of their identity. Especially those who had to leave their homes and migrate. And then after that migration, their behavioral pattern changed. And that behavioral pattern is actually pausing a serious challenge nowadays to the society of Pakistan. So we can say that Pakistan's case specifically with related to terrorism and its implications, it is a quite interesting case study for the students of political sociology to understand that how terrorism and counter-terrorism efforts has influenced the Pakistani society.


Hey, this is Brett and this 2019 Ford Mustang GT Premium GT Performance Package is stock number 13979Z. I'm here at Summit Automotive in Fond du Lac, Wisconsin, you're new and used sports car headquarters. This 2019 Ford Mustang has the 5-liter V8 Coyote engine. It puts out 460 horsepower. This car has been fully safety and inspected by our service shop, has a fresh oil and filter change, all the fluids have been checked and topped off. It has 4 brand new tires and it is 100% ready to go. I'm going to go all the way around inside under the hood in the trunk, show you the options, start it up and just give you the most accurate representation of the car that I can. Magnetic gray metallic is a color if you like the video, you can subscribe to my YouTube channel which is youtube.com slash summit auto. Click the bell notifications, you'll get updates on the videos I do each and every day as well as having access to one of the largest catalogs of vehicle and specifically sports car walkarounds on YouTube, 8,000 videos and counting. This one comes with the painted black alloy wheels and it has the Brembo brakes part of the performance GT performance package and it has brand new Waffen 25540 ZR19 tires on here. Put those on in our safety inspection, still have the little wear knobs on there. So they are brand new. Front fender is absolutely perfect, get the LED headlamps, LED running lights, LED fog lamps, we'll turn all those on at the end of the video so you can see just how nice and bright they are. Front bumper and lower valance are in really nice shape. The hood is absolutely perfect, no dents or dings in there, passenger side front fender, looks really good as well and the passenger side front wheel, no major scuffs or scrapes on there. Magnetic, metallic, one of my favorite grays on the Ford's got a lot of metal flake to it, a lot of silvers, a lot of blacks, really a good looking color. And as you go down this side of this 2019 Ford Mustang, take note of how clean that body is, how reflective and mirror like that paint is. Take these HD videos, so if you are far away or even if you're close by and you just cannot make the trip down but you're still interested in purchasing the vehicle, you can see the car, hear the car and have confidence in what you're looking at before you even get here. So when you do get here, there's absolutely no surprises. You can make a smart and informed buying decision from wherever you're at. If this video helps you do that, let your salesman know it, just saw the video, it was helpful and that Brett sent you. On the back we have 27540 ZR19s and these are brand new tires as well. And around to the back of the vehicle, you'll note that you get the LED tail lamps, the backup parking sensors, the quad tipped dual rear exhaust. The rear fascia looks good, there's a nice spoiler on it. Back storage area is in nice condition as well, and you do get a tire inflator kit back here. Shocks are doing a nice job holding that trunk lid out and that shuts nice and solidly. Coming down the driver's side, just as clean as that passenger's side, no dents or dings on the rear quarter. And for full disclosure, this back wheel is in excellent shape as well. Back pillar looks good. And the driver's side door is in really nice condition as well. Has blind spot wiring, built in directional signals.  Both these seats are heated, both these seats are cooled. No rips, no tears on those seats, power driver seat with lumbar, factory floor mats, auto headlamps, power windows locks and mirrors, and memory driver seat. Take a quick look at the back seats, they're in excellent condition as well. And they do fold down and you get the latch child safety system for any child car seats you may want to try and put back there. We'll hop inside, check out the miles, the radio, and everything that this car has to offer on the interior. You get that big 12 inch screen and you can see that this one has 18,766 miles on it. You get the digital speedometer on that side, a tack on the left. Instrument cluster is very nice and clean. Outside temp, radio, compass comes with the leather wrapped steering wheel. Bluetooth and information center controls on the right, cruise controls and audio controls on the left. You get the paddle shifters on the back. This one comes with the sync eight inch radio. Get your factory navigation system on here. There's highway 41, so that is working nicely, AM, FM, and, there we go, AM, FM, and Sirius XM radio capabilities.  So this is a heated steering wheel. Up here you get your oil pressure PSI and your vacuum gauge. That's all part of that GT performance package and you get the machine finished dash trim.  So you get Sport Plus, Track, Drag Strip, Snow Wet, and Normal up there. Then your automatic transmission. Believe this is a 10 speed automatic keyless entry with remote start and you get the ambient lighting and the cup holders. It smells very clean inside this car. Passenger side format and seat are an excellent conditional rips or tears on there and the headliner is absolutely perfect. You do get home link buttons right there for your garage door security systems and lane systems and map lights. We'll start it up. Take a look under the hood. Listen to that exhaust. Check out those LED lights. They'll be all set to go. Starts right up. No check engine lights or anything like that. The exhaust isn't very loud. I would personally like to thank you for checking out the video today and hopefully from this HD video you've been able to verify the quality condition options and of course cleanliness of this car all the way around inside and out. This thing is just about as nice as they get. All those lights are super bright and working nicely. Under the hood we have the 5 liter V8 Coyote engine, 460 horsepower engine. It's very clean, runs very smooth. Once again, this car has been fully safe and inspected by our service shop, has a fresh oil and filter change. All the fluids have been checked and topped off. Get the strut tower brace there. Has four brand new tires. There's the emissions sticker. And this one is 100%. Ready to go. I would highly recommend this car from a quality and condition standpoint. I shipped this one to California, Texas, New York, Florida, whoever's going to get it's going to love it. I'd sell it to a family member. I'd buy it myself. That's how nice it is. And the Seymour pictures of this car are one of our other 550 new and used cars, trucks, SCVs, minivans, Wranglers, sports cars, Mustangs, GT500s, Camaros, Challengers, Chargers, Corvettes, you name it. We've got to go to that website right there, summitauto.com, full pictures and descriptions of every single vehicle all at summitauto.com. And if you'd like to check out more HD videos, you can go to youtube.com slash summitauto. Click the bell notifications to get updates on the videos they do each and every day. As well as having access to one of the largest catalogs of vehicle and sports car walk-arounds on YouTube. In fact, in a second you'll see a link to subscribe to my YouTube channel on the upper left. A link to more Mustang videos are done in the upper right, a link to this vehicle on our website on the lower left. And a link to one of our latest YouTube videos on the lower right. Click those checks out. We're super excited to help you with this Ultra Clean 2019 Ford Mustang GT Premium, GT Performance Package and Magnetic Gray Metallic. Thanks again for checking out the video. Remember to like, subscribe and share on the YouTube channel. I really appreciate it. Thanks again.


What's up everybody, Jason here for jaskierscaseballs.com. Happy new release day guys. 2023 P&E Certified Football just sold out. This is a four box break. Pick your teams number one. So here we go guys. Here's the customer names. And Chris got the Eagles last bomb ojo. Good case. So obviously we're doing four box breaks guys. One, two, three, four. Firewall five or six was just re-rollin' again. You wrote the far left. All right, let's see how that looks. AJ Brown certified stars. Omar Jackson, then we got our relic here. Jaren Hall for the Vikings. A-A round with the Vikes, 10.99. Immortals. We got a Jared Goff relic, certified ballers to 149. That is Lyons going to Alec. Justin Fields there, franchise foundations, insert. And a Michael Parsons to 275. Oh man, looks great dude. Certified stars. There's a Jack Campbell for the Lyons rookie to 325. We got a Cedric Arner, Johnson Gold team. And how about that? All right guys, the Eagles have a great checklist. I'm a little Randall Cunningham, seven out of 35. I have a Trey Tucker for the Raiders RPA. Got Immortals, Joe Thomas at 249. George Pickens to 149. A nice Jordan Addison to 199. Insert for the Vikes. Well, the base RPAs are going to look like that.  We got a Bijan Robinson, certified stars, insert. As well as a Josh Downs to 249. Lucas Van Ness. B&B Packers. Devon Weatherspoon. And Joe Cleckl for the Jets to 99. Omar with the Jets. And another Trey Tucker. Raiders. Jerry. Justin Herbert to 249. Frances Foundation with the Josh Allen to 199. Miles Murphy for the Bengals. There you go. So we have the same RPAs for the last two boxes, but still gonna be something nice hiding guys. Remember just 16 box cases. So obviously kind of just like Ordin's, we might see some dupes. But like I said, we don't hear nothing crazy in these next two boxes. That obviously better odds for the next couple of picker teams we have. Aguars to 75. Chris with the Jags. We got a goal team out of 10. CJ Garner Johnson for my Eagles. And then Felix Anduke Ozama for the Chiefs. We got a nice eight and a con of two color patch to 99. We'll love us to 325. And a clean two to 349 for the Cardinals. And we got a Tyler Lockett Addison to 75. Excuse me. Vikings A-A-Rome. We got a Patty Mahomes to 275. Three boxes down. Two more to go. Another certified stars. And nice little Derek Stingley Jr. to 149 for Houston. Houston is Dan. We got a little Christian Watson to 199. We got a Relic Cedric Tillman to 399 for the Browns. And a Patrick Davis. Yonte Banks for the Giants. And a certified star to 75. That's Delvin Cook. Minnesota Vikings. We got a Relica Tank Bigsby for the Jags. Then we got a Tremaine Ediments to 10 for the Burrs. We got a Antonio Gates Immortals. And then we got a Tajae Spears to 249. Well, as an junior at 325, should have one more number of card. Luvante David for the Bucks. Alrighty guys, there you go. Those were the first four boxes. Again, some nice stuff. Definitely do feel like there's a lot better, definitely hiding. We have not got a case hit. We haven't hit a big RPA. Still feel like there's a lot of nice stuff. And again, obviously, we did get a couple hits for a couple teams, right? Like Tajae Spears, RPA, the Jordan Addison, and then two of those same Raiders player. Again, don't be surprised if they hit it again guys. Like I said, it is 16 boxes. So it's gonna be like Origins where you might get some dupes, whether it's a rookie autograph only instead of a patch autograph. And obviously we did get some cool vets including like this round in Cunningham. But like I said, it is a 16 box case. We're only doing a one fourth case break with a four box break. So definitely feel like there's still a lot hiding for every single team. But including some big rookies and some case hits potentially. So I appreciate it guys. The next ones are in the store already halfway there. If you guys wanna run it back, jaspyscasebreaks.com.


Man, a full day of bending things over and drilling holes. It's not as fun as it sounds. I think I'll finish the rest of this tomorrow. Okay, had some good dinner, some good rest, got up this morning, get some morning exercises, bit of other stuff, and now I'm ready to get back to the rest of these pieces. All right, I need to drill holes in the ends of all of these, and I have almost all of the parts made. I still have to make those pieces that hook into these things. And that, yeah, just these, these and those things. All right, all right, ORIG, that means this is the original one of these so I can measure the holes on all of the other nine from this one. It's always important to keep one original because if you start measuring from one to the next to the next to the next, your errors build up and then you end up with a mess. So you always, anytime you're measuring from a piece, not from a tape measure, you have to keep track of the one you're using to measure and always use the same one. I actually know a guy, Joe, who had a situation at a job once where he did that wrong. It's a good lesson though. Okay, I'm gonna have to find more of this stuff somewhere. I need eight more of these. See, oh, right here. If I'm lucky, yes, if I cut that right down the middle, I should be able to get two pieces. Doesn't matter, this is a little bit shorter, that's fine. That's just what gets riveted in. All right, I should be able to get eight out of that. Two, four, six, eight, with a bit left. Let me just check something here. Ooh, that's just barely wide enough. If I use the whole thing, now if I cut with a circular saw down, I'm gonna lose a bit of material in the middle and they're not gonna be the same size as these. However, if I cut it with my shear, I can cut a zero line that takes off no material right down the middle. So maybe I'll cut them into pieces like that first, and then I'll just have a little cut to do with the shear. Yeah, that should totally work. Come on marker, figure the marker line is about the same thickness as the saw blade-ish. Although these don't even have to be perfect. Just a rough size is good. I guess it's a good thing I bought a whole box of these markers. It is really nice, I don't know. Ooh, that should be good enough. Yeah, good enough. I should probably explain what's going on with these connections. All right, I've got quarter inch rivets. I don't want them to go all the way in like a normal rivet would. I want them to stick out. So the way I do that is first I drill a quarter inch hole in the material I'm going into. And it needs to be a nice snug hole. So I want the rivet to fit in there pretty tight. Next I need to put a washer on the rivet and this washer needs to fit real tight too. Now if I use a washer that I get out of my box of washers it's too loose for this. So I have to drill my own washer that fits, really snug. And I can put it in there and I can put the loose fitting washer at the other end because that'll be fine over there. And I leave it sticking out about that much. Clamp my washers just to make sure they're not moving. And then get my rivet puller and do the thing. I always keep these basically a stainless nail which is a useful thing to have. Okay, now I'm just gonna cut the end off of this and I want all that sticking out. I'll hammer it down a little bit and I'll hammer this down a little bit so it's not crooked. But what happens here is the rivet pulls the nail thing inside, up inside here which expands this metal and that's how the rivet grabs on. So that gets too fat to fit through the washer, right? But then this side also expands. It just doesn't expand as much. However, with a snug washer on this side the whole thing ends up being real tight. And then I cut the back of that off and I can just hammer it a bit to make sure that's nice and flared out. And then this is a little crooked so I want to hammer that side to get it down that way. And the reason I'm not just gonna bend it, I don't want it to become looser. If I hammer it, it'll actually become tighter if I press it that way. Ah, good enough. All right, I have a lot of parts. There's one more thing I need to make. These attached to the roof and I want to have something under them. I'm just using pieces of PVC. Yeah, as soon as I get these cut that means I can start assembling things. Well, I thought while I'm operating on these solar panels I may as well clean them. And I don't know if it's showing up on the camera. These things are filthy. So I've cleaned up to here right now.  Blocking my solar power. I'm gonna have to clean them all really good. Yeah, man, this was yellow when I started. That's gonna make a big difference. Well, I got five panels on there and they are looking great. And I'm about to lose my son. So I'll just get that last one tomorrow. One over there. It's all ready to go. It's got all the stuff on it. I just need to bring it up. Yeah, I don't feel like doing it in the dark.  I didn't skip lunch today, which is excellent. Feeling pretty energetic. All right, I had to go make some food. Oh, I gotta jump in the ocean. Oh, I'm going to jump in the ocean. Man, I bet I could have gotten that six solar panel up today. But I spent half an hour talking to some girl online today. Yeah, that's probably worth it.