Lesson 166 - Space Based Architecture

[@robinmathur5807]

Thanks Mark, I learned a lot from you.

[@markrichards5014]

glad you found the videos useful!

[@farrukhijaz]

Thank you Mark! You are great!

[@markrichards5014]

Thanks!

[@ignacioinnovo5308]

Your videos are great. You explain the concepts in a very clear way. Thank you for share your knowledge!

[@markrichards5014]

Glad you are enjoying them

[@pratikkhandale3127]

The way you explain each topics ❤❤ really appreciate your efforts

[@markrichards5014]

Glad you are enjoying the lessons!

[@robertmills8101]

Thanks Mark. I really appreciate this architecture series. This one seems more a design than architecture. Is it more than the database client caches data and sending it to the file store and maybe other clients. The architecture doesn't really come into play. Also, I''m wondering about fault tolerance if the database file system does fail. Many years ago I implemented replication and had to log the data locally before sending it on so it could be recovered. Thanks again.

[@markrichards5014]

Regarding the database failure, since the database is not involved in the transactional aspect of the system, it doesn't impact any of the services. The services are sending the data to a persistent queue or stream, therefore removing the database from the equation.

[@cookienyancloud]

Amazing journey, thanks

[@markrichards5014]

Glad you like the videos

[@jonatasfernandespimenta8566]

Awesome lesson! The way you explain is very very clear! I have a question about the data reader. Will the service only fetch the data from the database when a cold start happens? Or does the service have something like a CRON to fetch data from database from time to time just to make sure all data is updated? Thanks in advance!

[@markrichards5014]

Only on cold start or retrieving archived data (e.g., "give me my orders from 2017")

[@user-williamchen]

Thanks for keep sharing these great insights.

[@markrichards5014]

Glad you like them

[@SankaSenavirathna]

Amazing Mark, I noticed some similarities between the CQRS pattern and space-based architecture. How do you perceive this connection?

[@markrichards5014]

Tuple-space (Space-based Architecture) is a little different then CQRS, but I like where you see the similarity in the patterns in that writes are always async and eventual in tuple-space. You see, with SBA, yu still do writes to the cache, but the PERMANENT write is async to a database, so yes, in fact they are similar.

[@luramarchanjo9408]

WoW Thank y... this type of architecture is new to me!

[@markrichards5014]

Not many know about this architecture style...

[@thepancakestore]

Thanks so much for the informative video! One question I have however, how is this architecture scalable if it struggles with high transactional data volumes? If there is an increase in data volume that must be saved in memory and the system breaks down, doesn't this violate the scalability? Looking forward to hearing from you!

[@markrichards5014]

Indeed, the volume of data is an issue in Space-Based Architecture (every architecture has trade-offs). Space-based Microservices helps mitigate this problem because the more fine-grained a service, generally the less data it has. At times I've switched over to a distributed cache to address data volume and scalability issues.

[@rodrigomattioda12345]

Hello Mark, how are you? Where can I get more info on how to properly build such systems? I mean, maybe examples

[@markrichards5014]

Space-based can be implemented in any language, and the examples I have are from actual projects where I cannot share source code. However, our book "Fundamentals of Software Architecture" dives into a lot of details about this architectural style.

[@ren.oooooo]

Can you please cover the threshold adjust pattern at least in upcoming videos (reactive architecture is not there in the fundamental books, is it any other book?)

[@markrichards5014]

Great idea Reno - I just added those to my list for future videos.

[@juergenhildmann5921]

'Promo sm' 🤭