sppn.info Laws Pro Drupal As An Enterprise Development Platform Pdf

PRO DRUPAL AS AN ENTERPRISE DEVELOPMENT PLATFORM PDF

Wednesday, July 24, 2019


In Pro Drupal as an Enterprise Development Platform authors Jamie Kurtz and Thomas Besluau Файл формата pdf; размером 13,00 МБ. Pro Drupal as an. Enterprise Development. Platform. Jamie Kurtz. Thomas Besluau . Chapter Software Development Best Practices with Drupal. □. Pro Drupal as an. Enterprise Development Platform (Expert's Voice in Web Development) PDF, you should follow the link below and download the ebook or.


Pro Drupal As An Enterprise Development Platform Pdf

Author:LOREN WICKENHAUSER
Language:English, Spanish, German
Country:Venezuela
Genre:Fiction & Literature
Pages:
Published (Last):
ISBN:
ePub File Size: MB
PDF File Size: MB
Distribution:Free* [*Regsitration Required]
Downloads:
Uploaded by: JAYSON

application development platform than Drupal 6, and it will fuel a lot of Drupal's large enterprises on all phases of their Drupal experience, from pre-planning. pro drupal as an pdf pro drupal as an enterprise development platformpro drupal development In Pro Drupal as an Enterprise Development Platform authors. In Pro Drupal as an Enterprise Development Platform authors Jamie Kurtz ISBN ; Digitally watermarked, DRM-free; Included format: PDF.

Drupal has a horrible reputation for painful upgrades. I would say that's largely an issue of the past -- most module maintainers provide decent upgrade scripts, upgrades tend to happen with no data loss and very little functionality change.

But as a highly commercial platform not proprietary, mind you, just used by lots of businesses customers need to pay to get modules updated to the new releases, since most of the development of contributed modules is done by companies like Freelock, who get paid to do the work. And as long as it's cheaper to roll out a D6 site, and few other compelling functionality reasons to upgrade to D7, not many clients are willling to foot the bill to get the job done. Abandoned modules Or worse, modules that get replaced by an entirely different approach.

In the early days of Drupal, most site building was done by people programming custom modules on top of the Form API and the various other parts of the Drupal internals.

Enough of these were generalized and shared back to the community that the next phase was characterized by thousands of single-purpose modules -- install exactly what you need for each feature you want to provide, and perhaps need over a hundred on your site.

Now the number of modules you need is getting far less -- we have more general purpose, extremely powerful modules like Views, Rules, Display Suite, Features, and Context. As a result, the single-purpose modules are becoming obsolete, and developers pretty much abandon them.

This is actually a good thing -- these power modules really let a site builder build exactly what they want. But they also each have their own learning curve -- it's not as simple to drop in and turn on the functionality you want, you generally need to configure the behavior you want after installing the power module. This makes the Drupal learning curve even tougher for people who just want a site -- if you don't know how to use the power modules effectively, you can easily get frustrated when you find exactly the module you want -- but it hasn't been updated for 2 years.

Or if you've been using a module for years, and it's no longer supported -- and there is no clear upgrade path to something else. This is where Drupal has turned professional. Site building in Drupal takes a lot of knowledge to do rapidly. And that's not knowledge even the best non-Drupal developers can get quickly -- so much of this knowledge is very specific to Drupal. Knowing which power modules can address the shortcomings of Drupal core, knowing when it's time to drop in a power module, knowing how to use the interface -- these you can figure out.

But how do you even know the power module exists? That's why good Drupal freelancers and shops are expensive -- they're in demand, and they can do amazing things very quickly.

We may have a high rate, but we know how to get the job done Caching Caching in Drupal is perhaps the biggest thing that mitigates the memory hogging, the performance issues, and so much more, making Drupal as fast as most any other platform out there.

But it's also a curse. In short, if your Drupal site is misbehaving, a surprising number of times clearing the cache fixes it. Drupal caches things at a lot of levels: during a request it caches every node it loads. Blocks and pages can be cached -- but by the time you reach the page level, you can no longer use caching if you have anything personalized on the page such as shopping cart contents.

Drupal also combines javascript and css into compact files. Then there's system caching. On some sites we set up file-based caches to skip Drupal entirely, or set up reverse proxies.

And then there's Memcache for yet another layer of caching.

The problem with caching is making sure it gets regenerated when something changes. Generally the system is pretty good about clearing out changed data, but there are definitely lots of cases where this doesn't happen correctly. Caching is really a band-aid for the poor performance of Drupal, the dark side of having so much programmer power. The upside is that it works surprisingly well, and makes Drupal competitive. But it takes knowledgeable system administration to get the maximum performance, or to scale to handle large traffic loads.

And it is a source of quirkiness, a bit of an X-factor that can make problems harder to identify and locate. Lots of people claim to develop in Drupal, but there's a huge range in the quality of the result you get, and it's very hard to tell without working with somebody a while whether they know the platform well, or whether they're going to be learning at your expense.

We are all going to be learning at your expense.

Drupal 7 Module Development pdf - EBook Free Download

Development is about solving problems -- once they've been solved, they don't need further development! This is largely a question of experience, but I think there's an element of talent as well -- the talent to see where the crux of a problem lies, and be able to sniff out the heart of the matter.

That's a talent, but more important is experience. We have learned a ton by making mistakes. We know how to roll out changes to production sites without breaking them or at least keeping the broken time minimal.

We know how to undo our changes if something goes awry.

User account menu

And things go awry in complicated systems more often than we would like. Experience has taught us to build systems to protect every move, much like a rock climber scaling a tough wall -- while there are a few "rock star" climbers who may free-solo El Capitan, most people who attempt that end up dead. Smart climbers use protection so that if they make a mistake, the rope stops their fall.

On low-end commodity hosting, there may not be enough RAM available for the web server to load a large Drupal site. Generally we need to allow PHP to use at least MB per request, and on some large sites running lots of modules, even more. Fortunately, hardware is relatively cheap, and with the various caching strategies we typically use with Drupal, we can get sites speeding along. But this does mean you need quite a bit more hardware to run a large site than you would with a static site or a leaner, more efficient framework.

It's PHP. I actually really like coding in PHP -- it's easy to learn, easy to understand, and pretty powerful. But it has a number of flaws. Historically it has had a slew of security problems due to a bunch of convenience things that went so far as to conveniently include remote code in every request, if you passed a certain GET parameter!

But PHP has kept the reputation for having shoddy security baked in Lack of long-running threads, worker threads, or other things along those lines means that a huge percentage of the Drupal framework needs to get loaded on every request -- it can't just sit there in RAM waiting to get called.

Drupal does not really have a way of registering functions that implement hooks -- it does cache many of them, but not all. The Unicode issue almost seems criminal. This is supposed to be fixed in PHP 6, but for the time being, this means doing much localization work in PHP involves having your own string management functions. So our assessment: Security issues are no longer worse than most other available languages, caching can mitigate some of the lack of threading and it does make it a lot easier to program , and Drupal works around the lack of UTF-8 support with its own functions but why should it have to?

Version wars. Drupal 7 has been out for 10 months now. Drupal 8 is in development.

Drupal 5 is no longer supported. And we're still building most of our sites in Drupal 6. Anybody who has built a Drupal site starts out with the big question: what version should I use? Drupal 7 isn't yet the slam-dunk answer. The reason? There are still a ton of very useful modules that are not yet available for Drupal 7 -- and many that are not even close.

Drupal 7 is a far better platform to develop on.

However, there is so much already done on 6 that we can roll out D6 sites much quicker for our clients, at much lower cost, for all but the most simple brochure sites. We have done 2 D7 sites so far, and over 50 D6. D7 isn't even faster it turns out -- the main reason for going to D7 is that D6 is going to get left behind when D8 gets rolled out -- but at the current rate that's still a couple more years.

Drupal has a horrible reputation for painful upgrades.

I would say that's largely an issue of the past -- most module maintainers provide decent upgrade scripts, upgrades tend to happen with no data loss and very little functionality change. But as a highly commercial platform not proprietary, mind you, just used by lots of businesses customers need to pay to get modules updated to the new releases, since most of the development of contributed modules is done by companies like Freelock, who get paid to do the work.

And as long as it's cheaper to roll out a D6 site, and few other compelling functionality reasons to upgrade to D7, not many clients are willling to foot the bill to get the job done. Abandoned modules Or worse, modules that get replaced by an entirely different approach.

In the early days of Drupal, most site building was done by people programming custom modules on top of the Form API and the various other parts of the Drupal internals. Enough of these were generalized and shared back to the community that the next phase was characterized by thousands of single-purpose modules -- install exactly what you need for each feature you want to provide, and perhaps need over a hundred on your site.

Now the number of modules you need is getting far less -- we have more general purpose, extremely powerful modules like Views, Rules, Display Suite, Features, and Context.

As a result, the single-purpose modules are becoming obsolete, and developers pretty much abandon them. This is actually a good thing -- these power modules really let a site builder build exactly what they want. But they also each have their own learning curve -- it's not as simple to drop in and turn on the functionality you want, you generally need to configure the behavior you want after installing the power module.

Beginning Drupal 8

This makes the Drupal learning curve even tougher for people who just want a site -- if you don't know how to use the power modules effectively, you can easily get frustrated when you find exactly the module you want -- but it hasn't been updated for 2 years. Or if you've been using a module for years, and it's no longer supported -- and there is no clear upgrade path to something else.

This is where Drupal has turned professional. Site building in Drupal takes a lot of knowledge to do rapidly. And that's not knowledge even the best non-Drupal developers can get quickly -- so much of this knowledge is very specific to Drupal. Knowing which power modules can address the shortcomings of Drupal core, knowing when it's time to drop in a power module, knowing how to use the interface -- these you can figure out.

But how do you even know the power module exists?

Kurtz J., Besluau T. Pro Drupal as an Enterprise Development Platform

That's why good Drupal freelancers and shops are expensive -- they're in demand, and they can do amazing things very quickly.Greg Dunlap's work with core API documentation has many times ferreted out particularly hard-to-find bugs. And the reason is that the next upgrade will clobber your changes. Development is about solving problems -- once they've been solved, they don't need further development!

A lot of our business comes from cleaning up the messes left by developers who did not build in a future-proof way.

There are still a ton of very useful modules that are not yet available for Drupal 7 -- and many that are not even close. This book focuses on why Drupal makes a particularly strong choice for the majority of developers.

There are safe ways of changing just about anything you need to do -- but "Drupal developers" who are just trying to get your site launched and don't care about long term consequences don't bother with doing it correctly. System Configuration Kurtz, Jamie et al. Now the number of modules you need is getting far less -- we have more general purpose, extremely powerful modules like Views, Rules, Display Suite, Features, and Context.