We can start by first breaking down each of the terms:
SaaS refers to Software As A Service. So Gmail, Google Docs, Google Slides, Dropbox are all examples of SaaS products.
RESTful services are more vague, but generally represent systems that “talk” over the internet and “exchange state” via “restful” calls. So if your app uses GET/POST/PUT requests to get, update “state” it could be considered restful. If for example every time you use a GET request in your app, you delete something, your app isn’t using REST requests. I personally believe the term has kinda gotten out of control, and is more buzz-wordy, but generally if you hear something is using “REST” requests the same general idea applies, where you “change” the state of the app with these sorts of requests.
Data Serialization is pretty generic as well, and you mentioned the two things that come to mind, streaming/buffer apps and stuff like JSON/XML. You could dig more into this, but assuming they aren’t looking for basic understanding, its possible to utilize other context such as “large data volumnes” to assume they mean either massive REST requests, or some kind of streaming platform (??) I have limited experience in this aswell, so I couldn’t offer my insight.
Now when I hear “large data volumes” I think of big data use-cases. So data analytics over huge data-sets (not your run of the mill SQL query, more like terabytes of data) and performance over such situations usually comes to mind. If you aren’t sure your working with “large data sets” then you probably aren’t. For example, searching over all all the users of a system vs searching over all the server logs.
Now I personally haven’t done most of the FCC courses due to life being in the way, but I have heard about most of them and I would say FCC does teach you how to build a full-stack REST app, but I don’t think it covers any of the other topics.
- Building a SaaS product is different than building a full-stack app in that you need to build entire “service” part of the product, IE, billing, scaling, ops, security, etc. Lots of devils in the details.
- Not sure what they mean by serialization, but again if they mean something beyond JSON/XML I don’t think FCC goes over that. (if I’m wrong please correct me )
- Large data volumes are probably partial covered (data vis courses?) but without more info on what they mean when they say “large data volumes” it depends.