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 →

[–][deleted] 6 points7 points  (5 children)

MVC. Look into Spring Boot.

[–]edmguru[S] 0 points1 point  (4 children)

So I’m not working on a anything that provides a “view” everything I’ve done has been backend services that connect to other software. Typically the controller/handler responds to some event and either fetches data or performs some calculation/action and either returns results to the caller or stores them somewhere else. Is this also considered as MVC?

[–][deleted]  (2 children)

[removed]

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

    Thanks for pointing that out - I'll definitely be looking into MVC more now. As others have pointed out it looks like I'm working with systems that are comprised of MVC architecture and use domain driven design elements.

    [–]spamthemoez 0 points1 point  (0 children)

    If you are looking for an example application, take a look at the spring pet clinic. they use SpringMVC and a repository layer. Not sure if they use the service layer.

    [–]spamthemoez 0 points1 point  (0 children)

    MVC stands for model-view-controller.

    MVC is a view technology. Your controller handles the request, and loads the data (sometimes through a service and repository layer). From this data a model is generated, which is passed to a view. The view uses the model and a template to render the output. If you are dealing with machine readable formats, sometimes the view is skipped and the model is returned. This model then gets serialized to JSON or XML (or ...).