Securely connects distributed apps and services across public cloud, on-premises, and edge environments. Utilizing Infrastructure as Code, App Connect provisions resources and maintain uniform policies across multiple sites.
N/A
.NET
Score 8.5 out of 10
N/A
Microsoft's .Net is an open source, freeware application infrastructure.
I thought F5 Distributed Cloud App Connect worked great to bridge the gap between our gcp environment and on prem. We were lacking in cloud funtionality for native load balancers but XC really connected the dots. We would most likely need a hybrid environment until the irules functionality improves for a few of our apps but most could be migrated over the XC.
If you need to build anything from a quick-and-dirty GUI utility to a full-fledged desktop application, .NET is the way to go. It doesn't require extensive knowledge of the languages as Visual Studio is extremely helpful in its autocomplete, refactoring, and prompts, and lets you build out your solution easily without worrying about the details of [the] setup and boilerplate.
Ease of use - standing up a new site took very little time, less then an hour.
Connecting the dots - the ease at standing up a load balancer and advertising it on CEs was simple and straight forward. Once you get familiar with the field layout it's very comparable to BIG-IP
More of a unified experience as Gartner released their latest sort of sassy trends. A lot of consumers are looking at a more unified experience and that's the sort of compilation of both management and data planes into a single things like single UI, easier management experience for the corporations.
.NET is heavily Microsoft Windows oriented, and while .NET core tried to resolve that with MacOS and Linux support, .NET Core is still waiting for wider adoption.
While free for small projects, additional features for big projects can be a little expensive.
Can be resource-heavy upon deployment. We continuously have our more senior staff optimize the code of our junior developers for performance. Other languages are a little bit more forgiving in comparison.
At this point it has become too focal to our operations. An entire department could collapse if we dropped it now or in the near future. My experiences as mentioned in the previous questions tell of its gravity
.NET frameworks are fantastic overall. There are no limitations to what you can accomplish with it. The most important part is that you'll have access to developer community support and that .NET is always being improved every month. Be it in web applications, back-end servers, or integrations, .NET enables developers to do it all.
From what we have been able to test load/responsiveness is quick and when we've tested out reporting and troubleshooting modules they have pulled the correct information in quick timeframes. We haven't been able to test out any software integration with Splunk of other software on our system since we are still in early POC stages but from what we've been told we should be able to implement that in our environment
As Microsoft Gold Partners, we do have access to a lot of additional information and support from Microsoft. Still, the availability of "open and free" documentation, community, and enthusiasts of the platform is vast. Added to that, the quality of resources provided for all the Microsoft ecosystem is very impressive.
-F5 Distributed Cloud App Connect provides more granular security policies with features like DOS, WAF etc and others lack -F5 Distributed Cloud App Connect provides high performance global network and other rely on public internet and impact is latency and it gives F5 Distributed Cloud App Connect a better user experience
If it was up to me, I'd rather use something like Node.js hands down. Things are simpler, there is no gigantic convoluted class hierarchy to learn like there is with .NET. Also Node is really fast and lightweight. I find .NET these days to be a totally solid product and it certainly has its place - but it seems a bit dated and boring to me now.
We are slowly switching from a dying programming language to .NET because it was too expensive to hire developers for the old programming language. There are way more .NET developers around and an amazing community which has allowed us to keep our costs low.
Our development time has been greatly reduced because now we're not developing applications for each OS platform. We do it once and deploy accordingly.
.NET Core has been a big mindshift in terms of how to program. The learning curve has been quite high for existing .NET developers.
