{"id":8109,"date":"2019-03-25T09:00:53","date_gmt":"2019-03-25T07:00:53","guid":{"rendered":"https:\/\/kodingtech.com\/?p=8109"},"modified":"2019-03-25T09:00:53","modified_gmt":"2019-03-25T07:00:53","slug":"k-fs","status":"publish","type":"post","link":"https:\/\/kodingtech.com\/en\/k-fs\/","title":{"rendered":"Storage. Back to the future. Coding version."},"content":{"rendered":"

An article in the "IT made simple" series - from Koding<\/strong><\/h2>\n

Very often, in the discussions we have with our clients, we come to the discussion about the server.
\nWe decided to decode, since we are only at Koding, what people (in the exercise of the function) understand through the server.
\nThere are several angles. Some imagine a big, black box, which most often makes a deafening noise and which is used to store the company's common documents. In many organizations, the "Common" folder is, as its name suggests, common. Most of the requests for servers for small companies actually encode another need: that of a common place, distributed among several employees, where to keep and find documents when we need them. Some ask for a server with Windows, others with Linux. Some want NAS-type solutions or regular computers running an (open source) version of Linux built for file management. Regardless of their cycle on the scale of understanding technology, this type of requirement is, I know you don't expect it?, common.
\n\"K-FS
\nAnother segment of our customers, I understand that the server is a box that costs quite a lot and with which the company's applications run.
\nThere are a few more clients for whom the server is the service they pay for monthly. And, I know from my technical colleagues, it is located in a datacenter in Bucharest. Or Bra\u0219ov. Or Cluj. It also depends on where the tectonic fault was placed in the \u201crisk management\u201d documents of the parent company?.
\nThere are a few more philosophical approaches to servers, however, and we also like the angle of our friends at Bunnyshell. They understand by their own server any kind of virtual machine (or container) located in a cloud solution. Public or private. That matters even less. Whether it runs in AWS, Azure or AzureStack, this instance is a server.<\/p>\n

Why do we write?<\/strong><\/p>\n

Because we want to solve pain points like: \u201cwe need to change our server\u201d, \u201cwe need a new server\u201d, \u201cwhere the hell are those documents\u201d, \u201cI need a VPN to edit the document\u201d, and others like that, we have good news. The majority (overwhelming, we would say) of our customers use Office 365 as a centralized solution for collaboration. The document storage part, whether private or for the entire team, works very well. We do it too. And we like it. Other great solutions are offered by Google (G Suite) or Dropbox. However, a good part of users prefer the classic solution. A \u201cfolder\u201d that everyone can see, and each of them can organize their files and folders in the classic (tree) mode.
\nIt's true, many common functionalities are missing in 2019: versioning, check in, check out, granular rights,\u00a0AIP\/RMS<\/a> or others. On the other hand, we know that many of you don't use them anyway. Long live \u201cadoption reporting tools\u201d?. So, we have good news: why receive Ferrari cars, if you don't have a driver's license yet?! Koding has an effective solution: K-FS<\/strong>. The acronym of\u00a0Coding File Server<\/strong>.<\/p>\n

It doesn't take up space, doesn't require initial investment, doesn't have a long adoption period, doesn't cost a fortune. Implementation doesn't take 3 days (you can also read in the register 3 weeks), and scalability is (almost) unlimited. For those who are passionate, we also have a technical description. We didn't reinvent the wheel, we just simplify the technology and use our knowledge to find creative solutions suitable for various needs.<\/p>\n

How we do it: we use distributed storage on cloud platforms (Microsoft Azure<\/a> or Microsoft Azure Stack), we use an authentication and connection interface dedicated to each client and we take care of configuring the stations (notebook, desktop, workstation) of each user (manually, automatically or through a self-service guide). Finally, we do a short training, then you can start working. To protect this type of file server, we also recommend a backup product, which protects the data from a logical perspective (in case it is deleted by someone within the company, we can recover it from the backup configured for each client). If your organizational culture is based more on trust, there is no need for backup. The data is written simultaneously in 6 different locations of the same datacenter and this level of protection is sufficient for some.
\nAnother cool thing: it doesn't matter what operating system you use. Whether you have Windows, like Apple, or are a Linux user, K-FS works for you too. All you need is a computer and an internet connection (quite simple and cheap in Romania, don't you think?).
\n\"K-FS
\nSounds good, but have you started thinking about budgets and other crazy things? We consider that, from a price perspective, the solution is super efficient for small data volumes. It starts at 19.99Eur\/month (without any other cost) for a capacity of 100GB and includes both remote installation services for a maximum of 25 users. If you have more than 25 users, we can build you a personalized plan. And if you are among the first 5 customers, we also give you a discount of 50% for the first 3 months of the contract.
\nIn conclusion, we say that we have the ideal solution for a team, a project or an entire organization that needs shared storage and that's it. We invite you to learn more on the dedicated page, and, if it sounds good to you, you know where to find us: Contact page<\/a>. We take over from there (sales colleagues brag about having a lower SLA than technical ones). Test them!<\/strong><\/p>","protected":false},"excerpt":{"rendered":"

Un articol din seria „IT made simple” – de la Koding Foarte des, \u00een discu\u021biile pe care le avem cu ai no\u0219tri clien\u021bi, ajungem la discu\u021bia despre server. Ne-am decis s\u0103 decodific\u0103m, c\u0103 doar suntem la Koding, ceea ce \u00een\u021beleg oamenii (afla\u021bi \u00een exerci\u021biul func\u021biunii) prin server. Sunt mai multe unghiuri. Unii \u00ee\u0219i \u00eenchipuie o […]<\/p>\n","protected":false},"author":1,"featured_media":9202,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_breakdance_hide_in_design_set":false,"_breakdance_tags":"","footnotes":""},"categories":[6],"tags":[],"class_list":["post-8109","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-produse-koding"],"_links":{"self":[{"href":"https:\/\/kodingtech.com\/en\/wp-json\/wp\/v2\/posts\/8109","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kodingtech.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kodingtech.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kodingtech.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kodingtech.com\/en\/wp-json\/wp\/v2\/comments?post=8109"}],"version-history":[{"count":0,"href":"https:\/\/kodingtech.com\/en\/wp-json\/wp\/v2\/posts\/8109\/revisions"}],"wp:attachment":[{"href":"https:\/\/kodingtech.com\/en\/wp-json\/wp\/v2\/media?parent=8109"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kodingtech.com\/en\/wp-json\/wp\/v2\/categories?post=8109"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kodingtech.com\/en\/wp-json\/wp\/v2\/tags?post=8109"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}