By mwpowellhtx on

Hello,

Sorry I'm sure this has probably been covered at some level, but I've got a couple of specific questions where I'm currently at.

I am exploring Drupal, and DEFINITELY appreciate the need for planning. You don't dive in and expect to have a cohesive plan of action when you fail to think it through.

I was considering 'simple' ASP.NET MVC at first, then possible a SPA-Angular approach. But then I got to wondering whether CMS or Drupal might be a good fit.

Listening to a really interesting video, couple years old, but as far as I can tell, informative, and applicable even today. I am a bit further than absolute beginner, per se, apart from wrapping my head around the "drupal-way" and its opinions on how to abstract content, presentation, etc.

Okay, enough background...

I have the beginnings of a Model-Something-Something application I will want to deploy in the coming months. I am exploring connecting these modules, which are currently poised to get exposed at least through WebAPI, perhaps, via controllers, view models, and so on.

Some of the Drupal features sound interesting, some of the triggers, timers, and other features would be very interesting to connect with and just allow Drupal to handle administrative duties, so that the backend services. I would expect that requests are either timed or somehow coordinated with backend services, the engine runs, transparently or not, and state, content, etc, is updated and viewed via Drupal.

I expect it would be a paid site for advanced or continued participation, but these are topics for later times and/or that hasn't already been spoken about.

Thank you,

Michael Powell

⋅ Categories: Drupal 7.x

Comments

mwpowellhtx’s picture

mwpowellhtx commented

Couple of areas I think which may be possible but which present needing sussing out:

  • Drupal 7 can consume, or otherwise interact with, back-end WebAPI services? Ignoring, for the moment, whether that was an ASP.NET, Java, or other controller. Also ignoring, for the moment, just talking about consuming, not necessarily producing, API synthetic content.
  • And any concerns involved therewith? Such as to be aware of the serialization method? Xml versus Json, versus what else?
  • It also seems compelling to 'farm out' user authentication/authorization from the back-end service, and pass the OAuth user credential to/from for said purposes? That's just the user name? Or other id? Or there's a spec for what does get sent?

I'm not sure that's all for now, but these are a couple areas I'd like to get a better idea about as I explore Drupal 7 a little further and evaluate it's potential as a front-end head to my back-end, or third-party, WebAPI services.

Thank you...

Jaypan’s picture

Jaypan commented

This post is better suited to the 'Before you start' section of the forum. You can move the thread by editing the original post and choosing that section as the forum.