Which back end server technology in the Apple Ecosystem is very much like ASP.NET MVC?

#1

Hi All, :wave:

I’m new here so if this question doesn’t belong in this forum, do let me know and I will move it. :smile:

I am a .NET Developer for more than 10 years now and know ASP.NET MVC very well.

I absolutely love :smiling_face_with_three_hearts: it because it helps me make a website that is fast and responsive and is easy to program using HTML. It is also flexible to use whatever front-end we want, e.g. ReactJS, Angular, etc.

Just recently I got to know about Apple’s eco system of programming using the SWIFT language.

This left me wondering :thinking: what kind of server side technology does Apple have that is comparable to Microsoft’s ASP.NET MVC Technology using the .NET Framework.

Question is, does Apple even have a Server Side Technology like that of Microsoft? :thinking: :thinking: :thinking: :face_with_monocle:

Would love to know more about this from anyone who knows.

Thanks very much in advance! :blush: :blush: :blush:

Neo

#2

I don’t know for certain, but I don’t think Apple has anything server related.

My understanding is that Swift and SwiftUI is primarily used for Apps (i.e. user interfaces and on device storage) and any server needs are handled with backends written however the devs like. The API the app connects to might be Rails, or PHP, or Node, or Golang, or Rust or whatever.

1 Like
#3

It’s extremely uncommon for OSX to be used server-side (machines for remotely building iOS apps are the only practical use I can think of), so there’s not really any need for an OSX-specific web framework. Deploy targets for web apps are just going to be Linux 99% of the time. So whatever server tech, can just use .Net. Alternatives like Python, Ruby, PHP, JS or whatever are not quite the same in terms of being a complete platform, but they’re what’s used. Java ecosystem I guess is closest if you don’t use .Net

1 Like
#4

Thanks for the reply. Interesting to note that Apple doesn’t have anything like MS.

#5

Thanks! This helps my understanding! :smile:

1 Like
#6

It’s just not used as a server OS very much. Definitely not as a general purpose server for arbitrary web applications (there’s no point, you’d gain nothing over using it instead of Linux). I guess it’s kinda useful if you have an organisation that runs exclusively on Macs and needs access to Mac-specific stuff (accounts, keychain, calendars etc), and it’s very useful if you need to build iOS apps remotely (ie run XCode on a server). There used to be a standalone server version of OSx but it was discontinued in I think 2016, now there is a server app that matches the version on each OS release. But as I say, using OSx as a server OS is not common at all. There are very specific usecases, but it’s very much a consumer OS, not a server or enterprise OS.

Linux is by far and away (orders of magnitude) the most common server OS, and Mac handles Linux stuff absolutely fine, so as I say, if you want to use .Net, use .Net. There’s no issue here, it’ll work absolutely fine; afaik Core is basically feature parity now and all MS efforts seem focussed on it. It’s agnostic as to what OS you code applications in (MS want as many people as possible developing in it, so makes sense to not limit it to Windows OS). It’s just that you’re deploying to a server on a Linux machine, rather than to an IIS server on a Windows machine (and so you don’t get things like Microsoft Access or anything like that, which is not to do with .Net, but is a major reason for using Windows servers)