Member Avatar for eeeraser

First of all hi guys, sorry for not being that much active.

Lets get in the subject:
I'm planning to make a big application that will help me in my job.
I need first to define the requirements of my application a bit more:
* It will be UI Web-based.
* The application will be large.
* It will feature with some sort of "extension" feature (e.g. plug-ins).
* It will function over a network, and it is likely to be distributed/load balanced.
* It has big data base.
* Conneceted with with devices such as telephones.
* It reads some data from other programs. (These programs have PI link).
* Secure.
* Most likely Windows OS.
* Has the ability to interact with Windows Office.

These are the most important points.
So, I need guys your advice which language shall I use or which Langauges.

Sorry for dropping my thread here, couldnt find out where shall I put it.
if you need further information please send me a msg so we can chat/voice call on messenger.

Best Regards,

Edited by kvprajapati because: Email Snipped.
  • 2 Contributors
  • 5 Replies
  • 127 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by Stefano Mtangoo

Dani AI

Generated

— your constraints (Windows/Office interaction, a web UI, plugin/extension model, distributed/load‑balanced deployment, large DB and device/telephony links) point toward architectural choices more than a single "best" language. As noted, several ecosystems can work; pick one that matches the hardest integration points and the team that will maintain the system.

If Office/Windows interoperability is a strong requirement, lean on the Microsoft stack for the components that need deep Windows/Office integration (C#/.NET Core for services that must call Office APIs, or to host Windows-only SDKs). Avoid automating Office via COM on a server — use Office Open XML, Microsoft Graph, or server-safe libraries instead. For cross-platform enterprise services, Java remains a solid choice. For real‑time telephony gateways or low-latency event work, use a dedicated service (Node, Go, or a native SIP/WebRTC gateway) so the rest of the system stays clean and scalable.

Design for extensibility from day one: expose well‑versioned service contracts (REST/gRPC), define a plugin SDK with clear hooks, and run plugins in isolated processes/containers with strict signing and capability limits. Decouple communication with message queues (Kafka/RabbitMQ) and make core services stateless so they scale behind a load balancer. For the DB, choose based on access patterns: strong relational consistency (SQL Server/Postgres) with partitioning/replicas for analytic reads, or a NoSQL store for very high write/ingest throughput.

Practical next steps: build a small vertical slice (one service + DB + plugin host + a simple Office integration adapter), validate your PI/API integration and telephony flow, add metrics and automated tests, then iterate. Prioritize security (TLS, OAuth2/JWT, plugin signing) and keep the initial scope narrow so architecture decisions prove out before broad adoption.

Recommended Answers

All 5 Replies

Member Avatar for eeeraser

I'll be happy if anyone can give me at least a hint or something.
Please, I'm in need for your help if you do know the answer :).

Thanks in advance.

Member Avatar for eeeraser

Share with me your thoughts, it's Ok :)

Member Avatar for eeeraser

still waiting for a reply :(

Member Avatar for Stefano Mtangoo

I see 4 alternatives:
1. Java based
2. PHP/Frameworks
3. Python and Django/Turbo gears
4. Ruby (RoR)

See which language you are comfortable with and Go for it

Member Avatar for Stefano Mtangoo

I see 4 alternatives:
1. Java based
2. PHP/Frameworks
3. Python and Django/Turbo gears
4. Ruby (RoR)

See which language you are comfortable with and Go for it

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.