DEV Community: kurisutofu

What's the best approach?

kurisutofu — Fri, 30 Jun 2023 14:19:02 +0000

Hi,

For a personal project that I hope could turn into a service I'll sell subscriptions for, I want to make sure what the best design should be.

In my previous jobs, I've only built monolith applications but now, I'm wondering if a modular approach would be better, especially thinking of maintainability, scalability, and security.

My question is general and so the service I want to build is irrelevant, I want to understand what the best approach is.

I thought if I went with a modular approach, it may be easier to update without too much impact on usability (updating the admin features, for example, would not impact the users' front end, etc).
Additionally, I thought it might be better to separate admin and user endpoints, as well as separate user data from everything else, especially from where users have access.

The idea was that if a user manages to hack into the system via the user endpoint and access the DB, it would not have access to users' private data.

But now, I'm wondering if I'm making it too complex for too little benefit.

Here is a graph to illustrate my idea:

Do you think I would be better off with a simple solution like below?

Or do you think something entirely different may be warranted?

Since the question is general, I don't think the tech I want to use is really relevant but I'll mention it, just in case.
I'm planning on using .Net Core (maybe .net MAUI later, for mobile apps).

Thank you in advance!

Age of programmers, have you experienced drawbacks?

kurisutofu — Mon, 22 Apr 2019 03:15:22 +0000

Recently, I've stumbled upon a company that seemed nice and with a good product.
I often bookmark those for the day I decide to really try to go back to a programming role and may decide to apply.

When I bookmark a company, I usually add notes about the position and what attracted me in the first place so I read the details.

I saw in the section "Preferred", listed with desirable skills, that the maximum age desired is 35 years-old.

I was a little shocked because I'm 37 years old and also because I thought and still think that older people can program as well as younger ones.

That was the only instance I saw but I was wondering, have you seen this kind of things in open positions at your company or other?

Do you think age is important?

I agree a younger mind could understand new things faster.
However, I think that a lot in programming comes easier with experience and if you'd need to update your knowledge, you can usually do it quick enough by drawing on what you've seen in the past.

Apollo server or client?

kurisutofu — Fri, 31 Aug 2018 14:32:53 +0000

I need to create a set of web tools for the company I started.
Since it's my company, I'm the one to decide on the technology to use and since it's a side-business for the moment, I'm not in a hurry to choose (within limits off course).

It's been a while since I've programmed in anything else than .net and C# or basic javascript with jQuery (anyone remembers this? :D) but I had the chance once to play with Node.js with PhoneGap and that made me want to try Node.js more.

I also recently tried Graphql and I loved it so now I want to use it.

After reading a lot of different things about Node.js and Graphql and all the solutions around them, I've come to the conclusion I wanted to create a solution combining Graphql + Apollo Server on the server side and Apollo Client + Vue.js on the client side.

I see the server side as an API and maybe even later use it with mobile devices application but that's for later.

As a test, I could create a quick API with graphql and Apollo Server but now that I need to create the client side, I'm a little lost on how to implement this.

I'm wondering ... Do I really need both version of Apollo?
I like having the flexibility of an API but would you recommend to go simply with Apollo Client + Vue.js + Graphql?

Also, in my current plan, would I lose the benefit of Apollo Client if I don't use it directly with Graphql?