jQuery

jQuery

Application and Data / Libraries / Javascript UI Libraries
Frontend Developer at atSistemas·
Needs advice
on
UIkItUIkItBulmaBulma
and
BootstrapBootstrap

I'm building, from scratch, a webapp. It's going to be a dashboard to check on our apps in New Relic and update the Apdex from the webapp. I have just chosen Next.js as our framework because we use React already, and after going through the tutorial, I just loved the latest changes they have implemented.

But we have to decide on a CSS framework for the UI. I'm partial to Bulma because I love that it's all about CSS (and you can use SCSS from the start), that it's rather lightweight and that it doesn't come with JavaScript clutter. One of the things I hate about Bootstrap is that you depend on jQuery to use the JavaScript part. My boss loves UIkIt, but when I've used it in the past, I didn't like it.

What do you think we should use? Maybe you have another suggestion?

READ MORE
8 upvotes·439.1K views
Replies (6)
Recommends
UIkIt

I have used bulma in several projects. We could not customize with the websites very well. Also when we need "quick solutions" Bulma is not suitable (I mean basic animations, to-top buttons, transparent navbar solutions etc. For these solutions, you need extra js codes).

Everybody knows about Bootstrap (heavy but popular).

Now we start a new project with UI kit, I like it. Pros: It is fast and lightweight and imho it has very good UI. Cons: Small community. Documentation.

Check this link for kick-off. https://github.com/zzseba78/Kick-Off

Maybe it is helpful.

READ MORE
7 upvotes·291.9K views
Front End Web Developer ·
Recommends
Bulma

Been checking out Bulma, myself, and really dig it. I like that it's a great base level jumping off point. You can get a layout going with it, pretty quickly, and then customize as you want. It definitely sounds like it's the one you're leaning towards but a big factor would be who will be using it most? Your boss, yourself, others? Whichever you like best, you'll prob be most productive with but if in the end your boss says it has to be UIkit, then best to be open-minded and give it another shot. Sometimes you may not jive with new tools in your stack, at first, but then they can become tools you learn to love. Best to you in your decision! Take care & keep safe.

READ MORE
6 upvotes·291.7K views
View all (6)
Needs advice
on
Vue.jsVue.js
and
ReactReact

I am working on a new project and need advice on which front-end technology to use. The back-end is all written in C# MVC and Microsoft SQL Server databases. In the current project, we are using the same technology stack for the front-end; we are using cshtml (razor) with jQuery.

READ MORE
6 upvotes·44.8K views
Replies (7)
Recommends
Vue.js

If you are used to use JQuery, Vue.js more similar to Jquery because you only can import a CDN and start to work. Vue is really flexible and you can use it wherever you want.

In other hand, if you have time to learn and install a new framework as React, use it. React works with a standard and several conventions in his code, then is really easy integrate new libraries and plugins .

READ MORE
6 upvotes·1 comment·1.3K views
Alex Spieslechner
Alex Spieslechner
·
July 22nd 2020 at 7:39AM

this is not entirely correct. just like vuejs, reactjs can work with just the referenced script (tag). so you dont need a build pipeline in either. you massively miss out on features and DX though.

the notion that react has several conventions / a standard is also slightly incorrect. out of all choices, react is the least opinionated. its as close to "true" javascript, as it gets. there is no official state-management, routing, etc. so this is all your choice.

vuejs on the other hand takes some decisions off you (benefitial to new developers). there is an official routing library, an official state management lib: vuex, and an official way to approach styling. you get the point.

·
Reply
Software Engineer ·
Recommends
Vue.js

both are absolutely great choices. while you'll find more resources and a larger community with react, vuejs typically does some quality of life "magic" for you. its pure taste.

if your html markup comes from razor, I'd recommend globally registered Vue components though. I've successfully used this stack for 4 years. (content from sitecore cms rendered through razor, enriched with vuejs components)

in any case, you will want to try to remove jQuery, if you pick a frontend library, as you should not mix two ways to modify the DOM. it wont break but its unnecessary bloat.

READ MORE
4 upvotes·1.3K views
View all (7)
Needs advice
on
Node.jsNode.js
and
LaravelLaravel

I would like to share my stack in Web/Mobile application Development for Mid Sized Applications.

Project-1 : Laravel + jQuery + Android Java + IOS Swift

Project-2 : Node.js + React + React Native + Electron.

This is my current Stack, Can you comment on my selection and add your thoughts if my choice is a perfect match? Thanks

READ MORE
4 upvotes·154.6K views
Replies (2)
Software Engineer at CircleYY·
Recommends
Node.js

I would say go for Node.js since you probably would only build a REST API that would talk to the frontend and some communication with the database.

On the other hand, Laravel is a much heavier framework that follows MVC pattern. Since you don't need the V in the MVC of Laravel. You can go for a straight Express that just handles the API request and return a response.

READ MORE
5 upvotes·126K views
Fullstack Developer at Alpsify·
Recommends
Flutter
at

Hello Varun S,

Project-1 : If the Laravel part is an API, you should check Flutter or Quasar Framework for your frontend in order to reduce the development time and process.

READ MORE
3 upvotes·1 comment·130.7K views
Varun S
Varun S
·
September 26th 2020 at 12:56PM

Thanks for your comment, I like Flutter for some extend.

but not quasar since I am not a big fan of vue.js due to lack of much community support. Thanks

·
Reply
Fullstack Web developer ·
Needs advice
on
Spring BootSpring BootLaravelLaravel
and
ExpressJSExpressJS

Hello, I am a fullstack web developer. I have been working for a company with Java/ Spring Boot and client-side JavaScript(mainly jQuery, some AngularJS) for the past 4 years. As I wish to now work as a freelancer, I am faced with a dilemma: which stack to choose given my current knowledge and the state of the market?

I've heard PHP is very popular in the freelance world. I don't know PHP. However, I'm sure it wouldn't be difficult to learn since it has many similarities with Java (OOP). It seems to me that Laravel has similarities with Spring Boot (it's MVC and OOP). Also, people say Laravel works well with Vue.js, which is my favorite JS framework.

On the other hand, I already know the Javascript language, and I like Vue.js, so I figure I could go the fullstack Javascript route with ExpressJS. However, I am not sure if these techs are ripe for freelancing (with regards to RAD, stability, reliability, security, costs, etc.) Is it true that Express is almost always used with MongoDB? Because my experience is mostly with SQL databases.

The projects I would like to work on are custom web applications/websites for small businesses. I have developed custom ERPs before and found that Java was a good fit, except for it taking a long time to develop. I cannot make a choice, and I am constantly switching between trying PHP and Node.js/Express. Any real-world advice would be welcome! I would love to find a stack that I enjoy while doing meaningful freelance coding.

READ MORE
9 upvotes·334.6K views
Replies (10)
Recommends
Spring Boot

Hi Eva, As you have solid experience with Spring already, you should jump into freelancing with that. It would be quite stressful to start freelancing with a tech stack you don't know well. Then in the background you can keep learning/practicing an alternative and switch over when you are confident enough (eg. 0.5-1 year later). I think you should learn Laravel as you already like it and find it easier. Express has better performance but that is not required for most of the small freelancer projects.

READ MORE
17 upvotes·1 comment·287.4K views
Eva Maciejko
Eva Maciejko
·
July 31st 2020 at 6:50PM

Thank you for your honest advice !

·
Reply
Recommends
ExpressJS

Looking at current technological trends and rise of JavaScript, you cannot go wrong with JavaScript. - There's an abundance of libraries to get most things done - You can use JavaScript for both the frontend and the backend - this allows you potentially share your logic/models/code across both stacks - A dynamic/interpreted language such as JavaScript is great for serverless (there's somewhat of a trend towards serverless aswell - especially in modern projects) - If you like/need static typing, you can always migrate seemlessly to Typescript - VueJS is a lightweight framework (compared to Angular), it has more GitHub stars and most would argue it's easier to work with (beginner friendly). Additionally most modern webapps do not use JQuery anymore (even though a lot of legacy projects continue to do so). You don't need JQuery if you use Vue/Angular/React

Additionally it doesn't seem like performance is a hugely important metric in your scenario, so JavaScript would suffice.

Note: These are all my opinions and what I've seen in the current market when recently searching for jobs.

READ MORE
6 upvotes·1 comment·279.9K views
Eva Maciejko
Eva Maciejko
·
August 10th 2020 at 12:39AM

Thank you, very relevant advice. As someone who’s used to typed and compiled languages, I think I will enjoy Typescript. Already tried it in VS Code editor and it’s great!

·
Reply
View all (10)
Front End Software Engineer ·
Needs advice
on
Next.jsNext.js
and
.NET.NET

Building a website for a company to display information, Pictures, links, multiple pages. - info page display no extravagant features. -current stack is mvc .NET Core with html css jQuery

READ MORE
2 upvotes·3.7K views
Junior Fullstack Developer ·
Needs advice
on
TypeORMTypeORMSequelizeSequelize
and
ElectronElectron

Hey! I am actually in internship and have an app to create for my structure. It will be an intern app which will allow crud dashboard actions with some data provided by the use of an API of one of the structure partner and make a correspondence to data contained in a private database. Since it's an intern app, I thought about Electron for a desktop app because I did a lot of web with Laravel and the structure goes more for the desktop app. But it will be my first occasion working with this tech.

Is Electron a good choice? Wich ORM should be more complete and adapted to this between Sequelize and TypeORM? (Database will be MySQL) Some charts will be displayed in the app. Is there a library (preferably without jQuery) that suits this stack?

Thank you !

READ MORE
5 upvotes·59.8K views
Replies (1)

Unless you're either using a local database or a backend server, you shouldn't choose either.

My recommendation would be having a NodeJS API on the backend that connects to the database and Electron connects to the API. Never give the database connection data to the end user, unless it's a planned move and it's to use on a local database.

I can recommend Sequelize because what I'm use the most on every project I need to create database connections. It supports TypeScript, and if you already have the database create you can use sequelize-auto to create the models, as easy as that.

I've only used Electron once and I liked it, but it's not a good comparison, since it doesn't offer any database access by default. I used React for the frontend part of the app, you can use whatever you want.

READ MORE
5 upvotes·2 comments·5.6K views
Dieudonné ALLOGNON
Dieudonné ALLOGNON
·
May 24th 2021 at 7:13AM

Thank you! That's what I finally decided. Your answer makes me sure that I am on the right track

·
Reply
Alexandre Desroches
Alexandre Desroches
·
July 25th 2021 at 4:41PM

If possible, avoid making an Electron App because the build process can be much more irritating and complex than making a web app. If you're able to use technologies like Firebase Firestore and a simple front-end to serve the data it will be hundred times faster than handling a full desktop app!

·
Reply
designer, programmer at Downdijk·
Needs advice
on
ReactReactjQueryjQuery
and
JavaScriptJavaScript
in

I use jQuery at the moment because I use it for a lot of years already, but now Bootstrap 5 decided to switch to JavaScript, I am thinking of switching to an alternative.

I use jQuery only for the DOM integration, animations and ajax calls because JavaScript calls to a class looks such a long call. I like the way of jQuery with $(document).on('click','.something',function() {});

By the way, I like to keep using HTML, PHP and Bootstrap as I do now.

READ MORE
10 upvotes·9.8K views
Replies (3)
Recommends
JavaScript

Hi Adan,

Javascript has changed quite a bit in the recent years and lot of it was inspired from jquery. Now almost all modern browsers support javascript syntax everything that jquery does with few elaborate / sometimes better alternatives. So, if you like to switch, find the equivalents of what portions of jquery you use and replace those parts. Btw, jquery is still nicer sometimes with its method chaining and a lot simpler syntax - the equivalent in js may not be that sugary syntactically.

READ MORE
10 upvotes·1 comment·9.4K views
Adan van Dijk
Adan van Dijk
·
August 10th 2021 at 4:05AM

Thank you for the explanation and i think ill switch to plain JS.

·
Reply
Front-End Developer at Potfolio·
Recommends
React
JavaScript

I was like you two years ago, used to jquery and didn't want to switch, but if you're willing to use js frameworks in your projects(React, Vuejs...), I advise you to switch asap, and get used to normal javascript, because in the end, it's the core language, but there are some new ways in it (especially in ES6) that will make your life easier, like you can replace the document.querySelector() with $() and document.querySelectorAll() with $$(), using this line of code: const $ = e => document.querySelector(e), $$ = e => document.querySelectorAll(e); then you can select a p element just by writing: $('p'), and multiple p elements like that: $$('p'). I hope my advice helped you in any way.

READ MORE
4 upvotes·1 comment·988 views
Charley Kline
Charley Kline
·
November 12th 2021 at 3:35AM

Um, those jQuery-like calls like`$()` and `$$()` work ONLY in the dev tools console. You cannot incorporate them into the scripts that your browser itself runs. If you try that, you'll get a ReferenceError because `$` is not a defined variable.

They are handy when poking around in the DOM by hand in the console, though.

·
Reply
View all (3)
Needs advice
on
SvelteSvelteFaunaDBFaunaDB
and
DenoDeno
at
()

I run a music-based website (eatnoise.com) which was built ~ 7 years ago. It was built using the jQuery framework, using PHP and MySQL in the backend. The site wasn't successful business-wise, so the site is more or less dormant. Now, I am learning web development myself via structured, online tutorials from Udemy. After working as a band-booker for several years, I want to pivot the site to include band-booking and ticketing features. I have two options: Engage the web developers who built the site initially and pay them to make the upgrades, even though there are improved technologies that have come onto the market since to increase performance, security, and SEO, OR build the site myself to my specifications using technology clearly on the ascendant. The first option means I get to market much quicker, albeit the technology will be redundant sooner and comes at a performance cost. The second option means it could be a year before I am proficient enough at coding to build the product myself and would take months to build, but I have the latest in technology to make a good PWA, but I'd be able to debug and make changes to the site myself. I'm looking for the advice of experienced developers who might be able to suggest the best way forward.

READ MORE
6 upvotes·2.5K views
Replies (2)
CTO at Dee Flex·

First of all, thank you for reaching out and asking the community a question like this, because I think there are a lot of people in this boat.

TLDR; The short of it is - if you are interested in building other sites further down the road, then you would be wise put the work in and build the booking site yourself. It will take time, so you will definitely need to think about long term implications. However, if you are not really interested in building other sites, or you have other really pressing concerns that need your time, it would be best to engage the original web developers to see if they can update the site which would free up your time. The flip side is they might say the whole site needs an overhaul due to such and such not being secure anymore, or whatever their excuse might be, so it could take time and cost more than you expect. Watch out for ballooning costs and make sure you get a clear plan down before agreeing anything.

-

If it were me, I would build the site myself. But, there are a couple of things you need to consider (and this is coming from my experience working with on the web for around 26 years, and as a pro webdev for nearly 20 years).

This is a slightly long post (sorry, I truly did not mean to write an essay) but I hope that it will quell your concerns, encourage you, and help you on your journey as a webdev.

The first point is about time - if you ask this other team to update the site, you will have more time to do other things. If you have something else that is important to you, that you need to attend to, then it would make sense to ask that team to do the work. I suspect they will likely tell you the site needs to be totally re-written somewhere along the line, and it might turn out to take more time and money than you expect, but at least you would be free to pursue other things. The second point I would raise is that if you build the site, you have to maintain it. If you build the site well, you can sleep at night. If you don't, you might get a call at 8pm before you are thinking about finishing for the day saying there is some problem with the site. In fact, even if you build the site really well, you will still get edge cases where someone will inform you of an issue, with limited information, you may end up spending hours to work out what the issue is (and indeed, if there even is one). I've experienced this a couple of times over the years, fortunately it's very very rare, but it's always a possibility.

Considering the two points above, if you decided to build the site yourself, I would have the following suggestions: Build the site with SvelteKit, FaunaDB and CloudFlare (Workers and CDN). There are a LOT of tools around, and there are always new ones just around the corner, but working with the above tools has been a game changer for me. This is all serverless based. It has the capacity to serve hundreds of thousands of simultaneous users in a way that PHP/MySQL could only dream of (and PHP/MySQL has been my bread and butter for most of my webdev career).

  1. It does this at a controlled cost : (CloudFlare Workers) In quiet times it scales down, you pay almost nothing to keep things going, and when the site is busy it scales to support the users, however as many as there are. Many firms have made this claim over the years about various tech, but I think that with Cloudflare Workers it really is true. Performance is fast, reliable, it scales smoothly, and cost is kept in check. I notice you have put Deno in your stack which is a V8 runtime (I think this is pretty much the same as Cloudflare Worker’s V8 runtime, though someone correct me if I am wrong). I have no experience with Deno though.

  2. Less time is needed to maintain servers : I have a few sites on a hosting provider in the US where they manage the servers, I’m also using AWS where I have to maintain the servers. The reason I use AWS is because I needed sites served in Japan, on a fast backbone, and because I was PHP/MySQL based they seemed to have everything I needed (I looked at a lot of other TRADITIONAL hosting options here in Japan, but AWS reliability, scaleability and functionality simply beats them all, even if it is not the cheapest). There are some issues though. If you have a site that is going to be potentially very very busy (even for short periods of time) you need to set up load balancing. There are various ways of doing this on AWS, trying to figure out the best reliability/performance/cost path is not easy - I read so much documentation I started dreaming about it. If you have load balancing in place, and the site is not busy, you are burning money. On the other hand, if it cannot support the current number of users, you have to scale up quickly, preferably before you get into that situation otherwise you are going have a poor user experience (which I truly dislike) and will lose customers. Of course, for best performance (and control of costs), you would probably set up your own server via EC2. You have to maintain that server. I’ve never had a server go down, fortunately, but it’s certainly a possibility. You have to maintain that too. This all takes up valuable time. It’s not a marketing thing, it’s a real down to earth problem that is solved going the severless route. It really truly does. Which is why I recommend Cloudflare.

  3. Why Svelte? (or, how did I get here) : I’ve written several large web applications from scratch over the years. I amassed a large library of my own modules that I have refined over the years including tools to support the development process itself (performance, trace, logging, etc). For about a year or so, a decade ago, I used Drupal 6/7 (which was a nightmare for many different reasons, and caused lock-in). I built several sites with it, but it always seemed to require more work and had a lot of issues with maintainability later on (I bring this point up, because I have experienced the ‘promise’ of new tech several times, Drupal was one of them). After this I ended up building my own framework from scratch in PHP because I wanted to make sites I built as fast and lean (yet fully featured) and be the least memory intensive as possible - in order to serve as many concurrent users as possible. Full user account management, security with roles, forms that build themselves (pretty much) because the system knows how tables are related (I was really proud of this because I could build a form programatically with just a few lines of code, fields are protected from invalid input, user access controlled view/edit, etc.) I designed the whole stack setting up my servers on AWS, tuning Apache and PHP to be as fast as possible. Memory use for building a fully constructed page was under 2mb, and generation took a millisecond or so (actually can’t recall the exact number, but it is VERY fast).

I spent over half a year last year working every day. I mean, truly, every day. I didn’t have a single day to stop and rest for over half a year because there just wasn’t time. Towards the end of last year the project got paused for various reasons. It was used for demos to clients, which was immensely important for our business, but was not put into full production as it wasn’t 100% finished. I took a break. Worn out, and pretty disappointed. I bring this up because when you put a lot of hard work into something, you don’t usually want to let it go. There has to be a damn good reason to take another path after that.

Over the years I looked at many different frameworks, CMs, and other curiosities - each time wondering "would it be worth investing time in this?" After being burned by Drupal many years ago, I had pretty strong reservations about locking myself into someone else's code base.

Earlier this year I started on a new project - I had all my tools I had already built. I could build the new site in around two months with all the existing tech I had, and I would probably have much free time to myself. Having designed the new system, prepared the database, I starting thinking about improving the page design and better user interaction (of all things right?) I looked at various javascript frameworks. My thinking was - I’ve got the server side down, I’ve got the content management down, let’s see what more we can do with the front end. And I discovered Svelte. I saw Richard’s demo from back in 2017. My world exploded from that moment on (where the hell had I been?)

It needs a serverless server (I’d heard of these and it didn’t make much sense to me way back when - losing control of the servers, who would possibly agree that was a good idea?) However, I looked into it more, and ‘saw the light’ so to speak. While there are a lot of options I decided that ultimately Cloudflare made the most sense to me. And the journey began.

The point of all of the above post is that I am not one to jump ship. I am not interested in the latest fad. There needs to be something truly substantive for me to decide to invest the time needed to move to a different stack.

I still haven’t answered the question - why Svelte? You might wonder - why on earth would I change after all that hard work I had already done for my PHP based framework (which actually has a Javascript side with lots of modules for different things as well), to using Svelte? Because it is, in my opinion: the future of webdev. Yes, there might be a new framework years down the line that could take over (never say never) but right now it is so well thought out, so well put together, and so forward thinking, it just doesn’t make sense not to invest time and use it. It’s similar to a few other frameworks (next, react, etc), but different enough, that it’s a totally different beast. The amount of code you have to write is lower, readability is better (this is REALLY important, and many programmers learn way late in the game how to write code that is readable - we often get stuck on performance; readability be damned). Code manageability is great, separation and modularity of code is pretty good, I’ve been very impressed with it.

Now that you can understand a bit of my background, and my journey here, I’m going to try to answer some of your other questions.

If you build the site yourself, you are not just committing to building the site, you are also committing yourself to building other sites later down the road (otherwise it is likely not worth the amount of time you will have to put in to building the booking site.) Given how functional the Svelte, FaunaDB, Cloudflare stack is, if you get the stack down, then future development time will be significantly reduced, and the sites you build will be fast and robust. The bonus is that you won’t have to keep an eye on them in quite the same way you would have to in a traditional non serverless hosting environment, costs are kept low, performance is good, and you can serve how ever many users you need to. Less stress, more time.

Both Svelte and FaunaDB are young. They are still developing, but I like the direction they are taking, and I think they are likely to take more and more market share of the webdev sphere - so having a good knowledge of them will most likely serve you well into the future.

There are a couple of holes in Svelte at the moment. Internationalisation for example is not really there, encrypted cookies with Svelte and Cloudflare was problematic for me as one of the usual Cookie modules for Svelte (not a standard inbuilt Svelte module, but something written by a contributor) uses an encryption module that is not compatible with Cloudflare (so this is really an issue with Cloudflare). Their VM is not 100% Node compliant, just so you know. Despite the issues I have had, I’m still steadfast in my belief that this is the right direction to take.

I hope that this post is useful to someone. If you have questions, just ask! Good luck with whatever you decide.

Edited to correct "CloudFlare (Works and CDN)"; and later to correct formatting.

READ MORE
4 upvotes·1.4K views
Recommends
Apollo

Whenever choosing a tech stack start with the simplest solution. WordPress might be a simple solution for all your problems with little development experience. However the booking feature with backing database may require more coding. If that is the case, a PWA is not a bad choice. I have not personally used svelte but it looks to be primarily a prebuild static site generator. This may make some runtime elements difficult like logins or reactive behaviors. I don't think you need those heavily so Svelte might be a good fit. If you need something more heavy duty based on React, consider Gatsby. I have found it is a good combination of SPA and static site features and can still be hosted on a CDN like Cloudflare. Svelte is newer to the game (but newer is not always better). Regarding the backend API, I have heard good things about FaunaDB. However, if you want to use the sql database you already have you could drop an Apollo server right in front of it to add the graphql features you crave. GraphQL is a great modern way to build an API. I endorse it. All my APIs are GraphQL. Regarding Deno, it is very new to the game... very new. I am excited to move all my stuff off nodeJS to Deno someday, but be aware as it's new it may have gaps and cause some headaches where NodeJS will just work and has the best package ecosystem in the world, NPM. For example, to use Apollo Server you'd have to use NodeJS instead of Deno. Overall, your choices are cutting edge so I think it would result in a sleek app, but know that with the newest comes the most change and learning difficulty. Also, I endorse using cloudflare for static site hosting. It is awesome. If you have any questions, don't hesitate to reach out for more specifics.

READ MORE
4 upvotes·2 comments·640 views
Paul Vardy
Paul Vardy
·
November 29th 2021 at 9:31AM

Just to add to Jim Hill's comment:

“I have not personally used svelte but it looks to be primarily a prebuild static site generator. This may make some runtime elements difficult like logins or reactive behaviors.”

It is the exact opposite. Dynamically updating different parts of a page based on user interaction with the page, along with elegant and performant animation is very easy with Svelte.

Dynamic websites are Svelte’s bread and butter - with reactivity that is better than React’s.

Regarding Gatsby - my understanding is that Gatsby is a static site generation (SSG) solution built on top of React.

There is of course also Next.js, a static-site rendering (SSR) solution also built on React.

Svelte is really a compiler that compiles a site ready for the server to put the pieces of a page together based on the incoming call to the web server (such as a Cloudflare Worker).

SvelteKit is for Svelte, what Gatsby and NextJS are for React. An opinionated framework built on top of Svelte that allows you to create SSR (and SSG) websites and applications.

I’ve read of devs moving from Gatsby to Sveltekit and being able to leverage the performance advantages it has over it. Personally though I have never used Gatsby, so that’s anecdotal, but it does seem to be a recurring pattern.

* GraphQL

Fauna supports both FQL (which to me feels like the serverless version of SQL - I found it very easy to pick up) and GraphQL. They are fully implemented database servers.

As Jim Hill mentions, Apollo Server can provide GraphQL endpoints, meaning your web app can talk to the server in GraphQL - the Apollo server can then talk to your existing (My)SQL server using the Sequelize plugin (for example). This is very useful if you are not able to move your database or simply want to keep it where it is - but it’s not performant.

Using Fauna reduces all these different components, simplifying the architecture, and provides significantly better load handling. That said, Apollo is an immensly useful service if you need it.

Regarding Wordpress - yes you could use it for that - but it would take quite a bit of work. I had some experience using Wordpress a few years back setting up a simple website for my Dad. It’s working fine for him. I will say though that it will bring with it lots of issues that you will have to deal with down the line. Much like Drupal.

It may well be perfectly useable for the OP, but you will be fighting the constraints of the CMS at some point. Since the OP does seem to be interested in writing the site rather than attempting to build it with a CMS - I can’t really recommend it.

·
Reply
Jim Hill
Jim Hill
·
November 30th 2021 at 3:58AM

Thanks for the clarification. I will definitely check out Svelte more. I really believe in compile time optimization which it appears Svelte may have taken to the next level beyond React or Gatsby (on top of React).

·
Reply