5 ms·
Use exactly what you already know (angular + whatever you use on the backend). Unless of course the real "side-project" is learning a new stack[0], you want to
by sjs382 8y ago
Use exactly what you already know (angular + whatever you use on the backend).
Unless of course the real "side-project" is learning a new stack[0], you want to set yourself up for success by using what you're already familiar with.
[0] This can be completely valid and worthwhile—just be honest with yourself about whether your goal is to learn something new or to solve a problem or to create a business.
- woodpanel 8y agoThank you. My problem is: exactly what I know is not sufficient ;-) I know JS. The backend layer for me is unchartered territory, DBs I've shunned most of my career. So some learning curve can't be evaded. And from looking at the view-layer competitors to angular (vue and react) I'm not sure why not to give those frameworks a try, as Ionic seems to be less 'native' and more 'webView' oriented.
- zer00eyz 8y ago> DBs I've shunned most of my career. Database Design for Mere Mortals: https://www.amazon.com/Database-Design-Mere-Mortals-Hands/dp/0201752840 https://www.amazon.com/Database-Design-Mere-Mortals-Hands/dp... This is the book I recommend to everyone who is shy about DB's - I have owned several copies and given every one away. It breaks down not only functionality but how to create a good design in a sensible and easy to understand way. Worth every penny (and now somewhat cheap)
- dhruvkar 8y agothanks for this, bought. been looking for a recommendation in this space.
- woodpanel 8y agoThank you very much for recommending the book. Does it also provide a sense of when to use non-relational database systems, like NoSQL or GraphDBs (The book's description as well as "look inside" function at Amazon didn't yield any results for those two) ?
- zer00eyz 8y ago> Does it also provide a sense of when to use non-relational database systems, like NoSQL or GraphDB I always thought of the NoSQL movement as encompassing document, KV, and GraphDb's and each can be a major departure from RDBMs thinking. These technologies aren't always "replacements" for RDMB's and often live alongside them, Redis (or memcache) and Solr/Lucene (or elasticsearch) are ones that I have personally used the most. As you move into other tools like Cassandra or a Graph DB they look shiny but you are making some major (and maybe worthwhile) trade offs. These sorts of decisions probably shouldn't be made based off of knowledge from a book but rather experience and more importantly testing (performance and use). As a side note, the last project I did ended up using a flat file as a back end because it was fast, simple and easy while meeting the needs for what it had to accomplish. Installing a DB was more work than needed.
- cafard 8y agoLong ago I read it, and found it frustrating. I don't remember all my objections, but I do remember one: the author spent about four pages almost but not quite defining 3rd Normal Form. Yes, jargon can be a barrier for beginners, but jargon also serves a purpose. It seems to me that Jim Melton's Understanding the New SQL was pretty good. Anyway, I'm pretty sure I read one of Melton's books when I was learning about databases.
- miguelrochefort 8y agoI think you can use Angular natively via NativeScript.
- akudha 8y agoDBs I've shunned most of my career. So some learning curve can't be evaded. Assuming you're doing a small application with standard features, you should be able to pick up the basics over a weekend. It is a different story if you have to scale to tons of users, improve performance etc, but for a normal application, designing a bunch of tables shouldn't be hard. The backend layer for me is unchartered territory This might take a bit more work than the DB. My you know JS, so maybe you could pick nodeJS for the backend?
- louisswiss 8y agoCould try something like Firebase/Firestore and Cloud Functions to replace any work you'd have to do on the backend?