When I design and write software, one of the most important things to me is that it solves a real problem. This has been a theme with everything Project-FiFo has released so far, any system that we put out there solves a real problem.
FiFo itself was built out of the need to have a way to manage a SmartOS hypervisor, at that point, SDC was still proprietary and no other system existed at all. DalmatinerDB exists out of the need to have a clustered high-performance metric store, an area where it still excels despite all the movement in the field over the last years.
So where did FiFo.cloud come from? It comes from what the cloud ecosystem has become to be. It is no longer a monolithic place. It is no longer AWS or nothing. Today there is a myriad of cloud providers and users start to avoid putting all their eggs in one basket and home their provider miraculously is the one that does not have issues at one point or another. Couple this with the in-house hardware and the occasional co-located server and we end up with an infrastructure mess that is worse then what we had before the cloud area.
Project-FiFo itself uses four different cloud providers, has a test lab and some co-located systems. I’ll be blunt here, it’s no fun to deal with so many different things. Even with automation, it’s a mess, make sure everything is in sync, documented, different portals, ssh all over the place.
This is where fifo.cloud comes into play, what fifo.cloud allows you is to pull all those different hosts into one single place. Put a fifo.cloud agent on the host, or VM or hell the desktop under your desk and you can manage it from one location. It doesn’t matter anymore where the system sits, or how many different providers you use, if you have an in-house lab, or run dedicated servers in your own rack, it all is the same. Everything is reachable with just a few clicks.