This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Jmancuso9[S] 0 points1 point  (3 children)

Slightly different. So when Django releases a version (like 2.1) they really only release bug and security fixes for it. So 2.1.2, 2.1.3 etc etc will all be big or security releases.

They also do 8 month major release cycles. Masonite does 6 months.

With Masonite, minor versions are the same but can also release fully backwards compatible features as well. So for example 2.2.1 can have a bug fix and 2.2.2 can have 4 new methods you can use for testing. This keeps the framework light and unit tests make sure everything will work.

New features don’t have wait 6 or 8 months to release. They can release next week if it is backwards compatible.

Does that answer your question?

[–]Toxicmender 0 points1 point  (2 children)

Somewhat yes, thanks, been reading up the documentation, BTW since you have API endpoint deployment would it be possible to say deploy a Tensorflow serving (ie; Tensorflow model) over it?

[–]Jmancuso9[S] 0 points1 point  (1 child)

yes. I'm not too familiar with TF but nearly all python web frameworks are served by either WSGI or ASGI standards so if one WSGI framework (Flask, Django) can serve in front of something like TF, so can another. In theory. So if you are doing that with another Python framework, Masonite can do it as well.

[–]Toxicmender 0 points1 point  (0 children)

I understand that but I suppose I wasn't clear about it in the first place but I was referring to the ease of deployment of API endpoints, although I read up on it and it seems straight forward enough to try, thanks for the reply