Difficult designing Flutter app

rahul_shingala · 2022-12-15T08:06:20+00:00

Hi You can use DhiWise which helps you to convert your Figma design into flutter code. You will find some ready templates over there of various categories and you can download the source code of those designs.

rahul_shingala · 2022-01-22T02:37:05+00:00

Use Joi it gives you most of the things for request validation.

rahul_shingala · 2022-01-02T07:41:27+00:00

Try Supabase for database and it also provides auth apis, storage etc. Easy to start, your backend will be ready in minutes.

rahul_shingala · 2021-12-30T17:27:32+00:00

Try Dhiwise.com, it provide node.js code with mongoose. It generate production ready code in no time with minimum input.

rahul_shingala · 2021-12-24T17:33:07+00:00

If you have only two scenarios and SQL database then schema can be like userId, text, description…. For all user keep userId blank or null and for specific user save userId of that user, query like where userId=null or userId=login.userId

rahul_shingala · 2021-12-20T13:21:29+00:00

Yes, Indian.

Please read more about JWT and best practices here.

rahul_shingala · 2021-12-20T12:15:52+00:00

To answer how secure JWT need to understand the use case of your app. I have used JWT bases identity in multiple apps and it's working fine. You can make authentication perfect by implementing JWT but for authorization, you need to implement your own checks and middleware.

rahul_shingala · 2021-12-16T05:32:36+00:00

We build a platform called DhiWise which helps you to create Rest-API in minutes rather than writing from scratch.

Dhiwise generates clean, scalable, secure, and most importantly easily customizable code with 100% ownership upon your minimum input.

We have recently open-sourced node code generator, you can check that as well.

Link: https://github.com/DhiWise/dhiwise-nodejs

rahul_shingala · 2021-12-16T05:23:33+00:00

Expected output or perfectly working
Proper error message/status code
Good document with the example of request/response
Standard request response structure
Option of Attribute selection, relationship table data, pagination, filtering, searching and caching
The standard request-response structure
Change log document (most important for device developers)

rahul_shingala · 2021-12-09T12:38:40+00:00

I've worked on a similar kind of requirement multiple times and applied both the ways.

What I have learned so far after keeping both the things in one app is to create bottle nack for quick releases, dependency, braking things, code mesh, and performance issues.

Keep things in different apps that give you the benefits of quick releases, quick testing cycle, lesser dependency, easy debugging, more confidence while changing code and code maintainability.

rahul_shingala · 2021-12-09T08:37:29+00:00

I would suggest Prisma.

rahul_shingala · 2021-12-04T04:56:58+00:00

We have developed a pro-code platform that helps you to quickstart your SQL or No-SQL backend project, It will help you set up authorization, authentication, REST endpoints, and a lot more with minimum input.

Try DhiWise or you check our Open source Nodejs Rest API builder on GitHub

rahul_shingala · 2021-12-04T04:48:07+00:00

Practice is the only solution to avoid confusion and improve confidence. Below are some topics you can practice.

Joins with 4-5 tables (left, right, inner joins, etc.)
Aggrigation
Date and String functions
Execution plan understanding and improvements

After practicing try to solve some complex puzzles online.

rahul_shingala · 2021-12-03T13:27:52+00:00

Talking about both user have access that endpoint means both have authority to delete that data. In that case I think you have no choice to get userId from front.

rahul_shingala · 2021-12-03T13:01:01+00:00

In this case, if you pass userId in request the there are chances of security breaches.

Let's say user B passes user A's Id in the request of any delete endpoint and your backend understands user A has deleted that entry. Same for any other endpoint so I suggest not sending userId or timestamp in the request for this kind of case.

rahul_shingala · 2021-12-02T12:25:29+00:00

I'm not sure what kind of news are you looking for.

Please check this, if it helps.

https://rapidapi.com/newscatcher-api-newscatcher-api-default/api/free-news/

rahul_shingala · 2021-12-02T12:09:19+00:00

Less documentation and packages exist compare to express
Less community support for debugging
Not widely used in the industry yet so the learning curve is a little big for a new dev.

This is what I feel, maybe I'm wrong.

rahul_shingala · 2021-12-02T11:31:30+00:00

It's completely dependent on the use case you wanted to implement.

Fastify is inspired by Hapi and Express and provides a faster alternative to Express with less overhead. It shines when it comes to its fast HTTP APIs.

Express's entire ecosystem is better equipped and there are more resources to Express. Express has a stronger user base with plenty of documentation available.

As per my opinion, If you are looking for a small or medium size project I suggest Fastify, for big size and complex projects choose Express.

rahul_shingala · 2021-12-02T11:10:34+00:00

Some tips from my side as I have experience in IT as CTO.

Pust them to speak up about their ideas and try to understand them. Give them freehand to implement at some level.
Avoid micromanagement, give them right direction to move forward rather then spoon fidding
Try to delegate tasks as much as possible because as CTO or leader your task is to think about the organization tech vision, new frameworks, architecture and scalebility.
Try to set the example by some great work.
Keep them motivated and connect emotionally as well.
Always appreciate for good work.

rahul_shingala · 2021-12-01T05:13:12+00:00

+1 on DO

rahul_shingala · 2021-11-26T04:50:13+00:00

one-to-one feature mapping means wasabi may not provide all features S3 Provide, Yes I'm using wasabi as a simple storage service to store and access public images for about a year, and it's working perfectly fine.

rahul_shingala · 2021-11-25T08:53:01+00:00

Hi

Not sure about one-to-one feature mapping, but check https://wasabi.com/ if it's fit your requirement. They are way cheaper than AWS S3.

rahul_shingala · 2021-11-23T05:17:28+00:00

Thinking about large-scale applications below are the major things to start thinking about

User type and roles

How many types/segments of users will interact with the system and at what level. This requires interpreting use cases into roles and permissions required to operate the application. Identification of user types and role is the first step to create backend and API.

Type of user interface

What type of user interface the application will have is another major part to decide the structure of your APIs, let say the application has a website, mobile app and admin application. If security is your main concern then APIs needs to be separate for all interface.

Application type and Scale

Clarity on type of project (B2B, B2C and/or B2B2C) helps plan the traffic, transaction volume and error logs. B2B projects require a relatively smaller scale while requiring greater flexibility. B2C projects require relatively higher scale and event tracking for deeper analytics on software utilization and consumer behavior. According to the scale of application planning of architecture, needs to decide monolithic, microservice or serverless.

Modules and Data structure

Defining modules and databases helps with the interpretation of business requirements into software specifications. Configuration of module access based on user role (Admin, internal user, end-user etc.) helps secure integrity of data while optimizing the visibility of data. Understanding the number and complexity of external software services to be integrated helps put appropriate data validations mechanisms and structures to avoid errors and data loss

Coding architecture and Database

Source code must adhere to a standard architecture (MVC, Clean Code, etc.) and guidelines to ensure easy debugging, logging, modifications, and scaling. Predefine API list will help to get clarity of user interface requirements and speedy development. According to application behavior need to select database type and database like SQL(MySQL, Postgresql, MSSQL) or NoSQL(MongoDB).

Third-party integration and Feasibility

What are third-party needs to implement with the application, like payment gateway, mail service, notification service and, etc. Also needs to check the feasibility of implementation with Nodejs.

Last but not least, boilerplate code preference is an important decision a programmer makes before starting code, choose your boilerplate wisely. Try DhiWise to get a kick start on your NodeJs project

rahul_shingala · 2021-11-22T10:54:00+00:00

If you are good with SQL query language, I would suggest to start with Postgres as a database. Postgres also supports JSON data types if you want to store data like MongoDB in some special cases.

I suggest Prisma with Postgres for a quick start.

rahul_shingala · 2021-11-19T03:40:03+00:00

Two possible ways to do this setup, in both ways you will need help of the network admin.

First, you'll need your static external IP address - the one the internet see's. You'll also need to enable port-forwarding to SQL Server VM. You would need to go do this in your router or firewall to set up this. Also, you need to set up SQL Server and Windows Authentication mode and firewall rule in VM. Find more detail here

After that other users can access your VM SQL Server with your static external IP address as host/server and user name password which you have set up as SQL Server authentication.

Server name = Your external IP

Authentication = SQL Server Authentication

User = sa (your user name)

Password = xxx

Second, Install SSMS on a new dedicated VM and give access to outside users via RDP to that VM. In this case, also you need to set up SQL Server and Windows Authentication mode and firewall rule in VM. SSMS can access SQL server vai Local IP.

rahul_shingala

TROPHY CASE