Member Avatar for praveendesilva

Hey we are developing a centralized device management application via a web console so i am currently doing a research on the feature we can work on so your ideas will be helpful for me to build a better application with better features.currently we have incooperated features such as deployment to PCs n embedded devices simultaneously..and some other features..your feedback will be helpful..

  • 3 Contributors
  • 2 Replies
  • 61 Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by ithelp

Dani AI

Generated

Good direction, . Start by defining a small set of core operator features that actually get used: reliable discovery and inventory with tagging, secure remote actions and file transfer, staged provisioning and firmware/OS updates with artifact signing, integrity verification, and automated rollback, policy-driven configuration management, continuous health and alerting with immutable audit trails, and a clean REST API for automation. Those features make a console an operational tool rather than just a control panel.

On the architecture side, separate control-plane work (commands, policies) from data-plane traffic (telemetry, file transfer). Use durable queues and an event bus to survive bursts and partial failures. Keep telemetry in a time-series store (for example, Prometheus) Prometheus docs and configurations in a transactional store so rollbacks are safe. For constrained or flaky devices design resumable/delta updates and A/B partitioning so devices always have a fallback. Enforce signed artifacts, use TLS 1.2+ (prefer TLS 1.3), and require MFA-backed operator authentication. Bake canary and percentage rollouts plus pre and post checks and automated rollback triggers into the deployment flow.

Make the UX and ops story strong: API-first, webhooks for integrations, dynamic grouping/tagging, bulk operations with dry-run, and a plugin adapter model for new device types. Test in labs that mimic low bandwidth, intermittent power, and scale, and measure recovery time and update success rate. Good points from and — lean on mature open-source projects for design ideas but adapt them to your constraints. Post device classes, expected connectivity, and scale and tailored stack recommendations can be provided.

Recommended Answers

All 2 Replies

Member Avatar for DimaYasny

multiplatform support - windows and *nix.

Member Avatar for ithelp

Use opensource stuff like openNMS ,etc.

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.