Skip to main content

Backoffice

When developing Web and/or mobile applications, it is common to have the concept of a Backoffice, the data management layer.

In other words, it is a layer usually on the web where business management users enter an interface that allows them to perform interventions on data.

The following requirements are quite common:

  • User Management;
  • User Group Management;
  • Manipulation of database records adapted to business rules;
  • Logs to record what users did and when;
  • Restrict access; depending on the group or user, they may not be able to change or even see certain data;
  • Allow access via browser and mobile devices;
  • Generate management reports;
  • Dashboard tailored to the business with relevant information, which may present charts and tables;

For these and other reasons, developing the Backoffice often takes as much or more work than developing the final application.

In addition, it is also common for the Backoffice to provide the REST API with web services that enables business data communication with the final application, or frontend.

Backoffice.

Netuno provides a powerful Backoffice engine where, without code, it is possible to create the data structure, generating forms integrated with the database for the most common manipulations, such as create, search, edit, and delete.

It also provides user and group management and access controls with log records.

With low-code, it allows creating dashboards, reports, and the REST API (web services) integrated with JWT (JSON Web Token).

Because Netuno provides all the most common features ready to be shaped according to the business model, the effort to develop a custom Backoffice is drastically reduced.

Backoffice for New Projects​

When developing new projects, especially when they are applications for external clients, it is common to penalize the Backoffice budget, that is, the time invested in its development and in designing the interfaces is penalized.

This is because it will not be visible to the target client, so it can be left for later.

Furthermore, decision-makers' objective is more about achieving the final result and not the internal management layers, especially when it involves significant costs.

However, during development and especially during testing, having a Backoffice interface allows for better validation of data consistency.

Because Netuno facilitates building the data model and automatically provides responsive forms in a web interface for data management, simply use Netuno during the data structure modeling phase and you will automatically get the Backoffice interface. Quite simple!

Then you can choose to evolve further to develop dashboards, reports, and web services all in Netuno.

Or, due to some type of limitation or requirement, you can develop the web services and the entire REST API with any other technology; for that, simply consume the database generated by Netuno.

In any case, you will have Netuno as an option to meet Backoffice needs.

Backoffice for Existing Applications​

In existing applications where a Backoffice has not been developed, or even where one exists and has limitations.

Netuno can be used both to expand the existing Backoffice or the Backoffice that is missing.

Since the effort to create a Backoffice with Netuno is quite small, either an entire Backoffice can be built in Netuno or just some modules.

It is up to the person to decide the direction of the technological options to use and their imagination; one thing is certain, there is no need to complicate much if you think of the modular Backoffice being developed and growing over time to suit you.

Normally, developing in modules is very complex, but since Netuno also simplifies this process by allowing multiple applications to be developed on the same database, it is also an excellent solution for developing independent auxiliary modules to extend an existing Backoffice without impacting the existing Backoffice.

Since Netuno easily integrates and can manage multiple databases in the same application, it becomes easy to import and export information to another database.

Thus, it is possible to better separate the complexity of the Backoffice from the Netuno applications that are like additional "modules" to the existing Backoffice.

Conclusion​

Undoubtedly, one of Netuno's main objectives is to simplify Backoffice development as much as possible and to integrate it into both existing projects and new projects, where it can integrate well with other technologies.

Netuno is not a closed platform where all development must be done in Netuno; quite the opposite, Netuno can be used simply to meet specific needs and overcome limitations of:

  • Cost
  • Time

Allowing it to be integrated with any other technology.

So, if the problem is a lack of money or a delivery date that is too tight, and on top of that there is a lot of complexity and several integrated technologies, Netuno should be seen as one more technology that will solve cost and time problems to make life easier.