Your stack of choice

[Wut]

Pure ES6 Javascript backend on Cloudflare workers with Durable Objects for data storage. Then React front-end on Cloudflare pages. The infrastructure costs are basically free and the speed is incredible as it's all globably distributed via Cloudflare's CDN.

 

[MagNorthDigital]

Pure ES6 Javascript backend on Cloudflare workers with Durable Objects for data storage. Then React front-end on Cloudflare pages. The infrastructure costs are basically free and the speed is incredible as it's all globably distributed via Cloudflare's CDN.

Now we're talking. Except I'd forego react if it really is just CRUD.

It's an extra 300kb on the frontend and webpack + babel that might not be needed.

Ship it as static as possible until the client wants to pay more.

 

[kolaval]

which UI in nuxt?

Ive played a bit with quasar but have not had the opportunity to use vue properly yet.
Always stuck in backend.

 

[wcm]

FastAPI - backend
Vue - front end
Postgresql db in most cases
AWS deployment

 

[Benedict A55h0le not]

Blozor for UI
Azure Serverless Functions for API and background work
CosmosDB for data
Azure Storage for data and queues

 

[konfab]

Pure ES6 Javascript backend on Cloudflare workers with Durable Objects for data storage. Then React front-end on Cloudflare pages. The infrastructure costs are basically free and the speed is incredible as it's all globably distributed via Cloudflare's CDN.

That looks super interesting

 

[Mystic Twilight]

Heap is better than stack, oh wai...

 

[MagNorthDigital]

This really depends on what the app is, how it will be used, and what level of security / infra you want.

How sensitive is the info you're handling, do you need to have ice cold backups from 2019, are you doing analytics / ml on the data, the users, do you have to report on it.

Do you need error tracking? CD/CI? Are you going to spin this out as a service.

In it's purest form, every solution / stack would work nicely. Some heavy, some expensive, most pretty awesome.

The C stack would be the fastest thing on Krypton, but you would need to be superman to build and maintain it.

Rad question.

 

[notayoba]

Pure ES6 Javascript backend on Cloudflare workers with Durable Objects for data storage. Then React front-end on Cloudflare pages. The infrastructure costs are basically free and the speed is incredible as it's all globably distributed via Cloudflare's CDN.

I think you might have shown me the way of the future.

 

[blaaislaai]

C#
.NET Core
PostgreSQL
Hosted on Azure/AWS

 

[InvisibleJim]

The Ada stack would be the fastest thing on Krypton, but you would need to be Chuck Norris to build and maintain it. And then Chuck would compile from source in his head and execute by typing into a hex keypad. In realtime.

IFTFY

 

[icarusza]

Ruby on Rails, MySQL, Nginx

 

[DA-LION-619]

And free cell on the other screen while you wait for your workbook to calculate.

Now I remember why the intelligence team doesn't like me, because I suggested connecting to SQL Server from Excel.

Pure ES6 Javascript backend on Cloudflare workers with Durable Objects for data storage. Then React front-end on Cloudflare pages. The infrastructure costs are basically free and the speed is incredible as it's all globably distributed via Cloudflare's CDN.

I have yet to find a use case for Durable Objects, I've offloaded a bunch of miscellaneous things to Workers and the $5 is worth it.

Deploying to the edge is blissful.

 

[Wut]

I have yet to find a use case for Durable Objects, I've offloaded a bunch of miscellaneous things to Workers and the $5 is worth it.

Yep, It's only been a pleasure using Workers. No more worrying about infrastructure although there was a learning curve at first. Decided that the best way forward was to forget most of what I was used to using ExpressJS and just build everything using pure JS without any plugins.

I've been using DOs in a combination with their WebSocket integration for a few of the real-time functions in an education app of ours. Whiteboard and Chat actions are logged to DOs for later playback should students wish to watch a complete recording of the lecture later on.

 

[_kabal_]

Yep, It's only been a pleasure using Workers. No more worrying about infrastructure although there was a learning curve at first. Decided that the best way forward was to forget most of what I was used to using ExpressJS and just build everything using pure JS without any plugins.

I've been using DOs in a combination with their WebSocket integration for a few of the real-time functions in an education app of ours. Whiteboard and Chat actions are logged to DOs for later playback should students wish to watch a complete recording of the lecture later on.

Would be really keen to see how this is managed from a team and CI/CD perspective.

I assume you have 10s of if not 100s of workers, work in a team, and use a mono repo?
I assume there is no way to run this locally, so all development is done using unit tests?
And then front end developers are building and integrating into remote API environments?

 

[Wut]

Would be really keen to see how this is managed from a team and CI/CD perspective.

I assume you have 10s of if not 100s of workers, work in a team, and use a mono repo?
I assume there is no way to run this locally, so all development is done using unit tests?
And then front end developers are building and integrating into remote API environments?

From a team perspective, we use GitHub as usual and the production branch is published to Cloudflare using Wrangler.

DOs are linked to a single Worker's namespace and cannot be accessed from other Workers unless you make API Fetch calls to those other Workers. So we tend to keep all DOs in a single worker and use other workers for functions that don't access those DOs directly.

You can test 100% locally using Miniflare (https://miniflare.dev), which is what we use until Cloudflare's version 2 of Wrangler gets released.

Correct, the frontend script (which we host on Cloudflare pages) then connect to the Workers as they do with regular APIs.

 

[DA-LION-619]

Would be really keen to see how this is managed from a team and CI/CD perspective.

I assume you have 10s of if not 100s of workers, work in a team, and use a mono repo?
I assume there is no way to run this locally, so all development is done using unit tests?
And then front end developers are building and integrating into remote API environments?

Workers are flexible, you could build an entire app or in my case take over certain http routes.
On hobby stuff, I also use them as an API Gateway to aggregate/cache requests.
My workers mostly do one thing so it’s deploy and forget, I haven’t touched some in over a year.

DO is a new option for storage that is consistent, the only prior option was the KV Store which is eventually consistent.
Not forgetting you also have your Zone cache in CF.

The KV Storage works well, I’ve implemented it as a distributed cache in .Net Core to preload items in the backend instead of an end-user having a cache-miss.

 

[Y'all Qaeda]

Probably something like Carrd or whatever landing page tool works, call that my front end.
Run it with a zapier or power automate "integration layer".
Google spreadsheet "backend".

Then constantly ask for more money to "scale"...
Have uncontrollable breakdowns, cry a lot, waste a lot of time. Generally be a valuable middle manager.

 

[DA-LION-619]

Probably something like Carrd or whatever landing page tool works, call that my front end.
Run it with a zapier or power automate "integration layer".
Google spreadsheet "backend".

Then constantly ask for more money to "scale"...
Have uncontrollable breakdowns, cry a lot, waste a lot of time. Generally be a valuable middle manager.

 

[Y'all Qaeda]

"I can't understand why we have such high staff turnover...."