To date there have been almost 4 million Raspberry Pi’s sold, which has made them a commercial success in addition to an educational platform.
That caused some uncertainty and frustration, especially when somebody was planning to rely on this hardware platform to build and run commercial software. This community is providing great support and many resources so every Raspberry Pi user.ĭuring the first few months of its release, production couldn’t keep up with demand. Amateur makers, Linux enthusiasts, and so many others have crowdsourced bug fixing, OS patching, and software and hardware support.
The direct result of the Raspberry Pi’s popularity is the huge community that has been built around it. And while they were painting the rocket, it suddenly took off to the benefit of the maker community, coding education, and hardware startups. The success of Raspberry Pi is one of those stories where the inventors were building what they thought would be a useful platform to launch young students into programming, but they ended up building a launch pad with a rocket on it. Having used the Raspberry Pi for more than two years in a commercial enterprise product ( NetBeez), I would like to outline my experience developing on this platform to deliver a high-quality product. You can read this excellent article on Network World by Scott Hogg. When the Raspberry Pi (RPi) came out, many of them found the ideal platform for their distributed probes. We have spoken to many of them, and the most adventurous ones started building their own homegrown monitoring tools based either on old laptops, unused workstations, or even virtual machines. There are many network engineers that have been looking for a network monitoring tool that uses remote probes to implement distributed network monitoring. Distributed Network Monitoring with Raspberry Pi
0 kommentar(er)
