For the past 20 hours, I have been trying to pick up Firebase Firestore and to build a queue system consisting only the View-layer of a typical MVC/MVT architecture, which is named ‘ ’. is a queue system that works similarly to the one we typically encounter in banks, government agencies, etc. However, instead of getting a small piece of paper with your queue number on it, you now capture your queue number from the screen. Schlange Schlange I build Schlange primarily for these purposes: to test if I could eliminate the web service or server layer by incorporating the logic into the View-layer and interact directly with the Data Store (Of course this is only applicable to insensitive data and simple logic); to test the usability of Firebase API; to test the real-time synchronicity of Firebase Firestore; and how feasible it is to integrate with Vue.js; Overview of Schlange There are 3 views of , a Display Panel view, an Agent view and a New Number Panel. The left window is the Display panel showing the queue to be served. The top right window is the Agent view for queue server and the top bottom right window is the panel for users to request for queue number. Schlange Whenever a new queue number is requested (by using the New Number Panel at the bottom right window), a read of latest next queue number is performed, the number is then enqueued into the ‘pending’ list. The ‘pending’ list is reflected in the ‘Next’ column of the display panel. Simple enough. My focus is not on the queue system but its architectural design. Architecture of Schlange In the case of , Vue.js is used as the View-layer framework. For real-time data store, I use Firebase Firestore. The users of interact with the 3 panels of and any IO operation to the data store is handled by the panels themselves. Schlange Schlange Schlange In , a new number request is a ‘creation of element’ in the ‘pending’ list. In Firestore, there isn’t any straightforward way to store a list. Instead, the ‘pending’ list is stored as a Firestore Collection. The real-time synchronicity of Firestore allows any changes to be reflected in no time. Since there is no complex logic in , the logic to perform this operation doesn’t have to be separated. Oh! It’s architecture! Schlange Schlange fat-client-thin-server Data Model of Schlange These are the data models of Schlange. "pending":{  1005: {    "number": 1005  },  1006: {    "number": 1006  }}"serving":{  1004: {    "number": 1004  },  1003: {    "number": 1003  }}"served": {  1002:{    "number": 1002  },  1001: {    "number": 1001  }} To enqueue, simply add a new Document into Firestore so the “pending” collection looks like: "pending":{  1005: {    "number": 1005  },  1006: {    "number": 1006  },  1007: {    "number": 1007  }} Whenever there is an update to the data store, it will be synchronized to the display panel. You can learn about the data model in Firestore from their documentation . How is Schlange Data-Centric? A data-centric application is an application that relies heavily on the connection to a database. is nothing different from many conventional systems dealing with data all the time. If there is a network failure, the disconnect of the data store is going to break the system. Therefore, the weakness of a data-centric is pretty obvious. Once the connection is down, the system is down. Schlange How is Schlange Serverless? According to , he describes a serverless application as an application that runs its logic in a stateless container or application that uses vast ecosystem of cloud accessible databases or services. He even exemplifies it with a client application that interacts directly with the data store. So, is one of it. Martin Fowler’s explanation on Serverless architecture Schlange How to Integrate Vue.js with Firestore? I will be posting this topic in near future and I will add a link here once it’s done. Stay tuned! 😊 What I’ve learnt? So, these are what I’ve learnt based on my purposes: to test if I could eliminate the web service or server layer by incorporating the logic into the View-layer and interact directly with the Data Store -> Yes, I could. But there is one caveat I have to take care of is the access permission of data. Good news is, it is enforceable by using Firestore Rules and incorporating Firebase Auth to test the real-time synchronicity of Firebase Firestore; -> The synchronicity is satisfying but the actual latency depends on how you integrate it with your application and how feasible it is to integrate with Vue.js; -> There is a way, but I suspect there is performance trade-off. I will look into it further to test the usability of Firebase API; -> Their JS API uses Promise extensively, a great mechanism to handle async calls. I have posted about promisifying callback API in a native way, you can check it out . here Demo You can find the demo at . http://schlangeplayground.herokuapp.com Your clap will definitely drive me further. Give me a clap if you like this post.

Google

Using Enum as Model Field Choice in Django

ES6: Promisifying The Native Way (with Strophe as example)

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

Building a Serverless Vuejs App with Firebase Firestore

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Parsing Terraform for Forms: Transforming Variable Types into JSON Schema for Frontend Apps

64 Stories To Learn About Firebase

A Useful Wrapper for MobX and Firebase Cloud Firestore

Access User Location with Permission Handler in Flutter

Adding Firebase Analytics to a Gatsby Project: A Beginner's Guide

Parsing Terraform for Forms: Transforming Variable Types into JSON Schema for Frontend Apps

64 Stories To Learn About Firebase

A Useful Wrapper for MobX and Firebase Cloud Firestore

Access User Location with Permission Handler in Flutter

Adding Firebase Analytics to a Gatsby Project: A Beginner's Guide

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps