• Resolved janc76

    (@janciriack)


    Hey everybody,

    I am struggling a bit with the decision to integrate newsletter functionality into WordPress or not. MailPoet seems to be a great tool and offers a lot of what we need. Most of our newsletter content will be WordPress posts.
    I was a bit shocked about the size of the plugin though judging by the amount of database tables MailPoet creates. Blowing up the database about four times the size of the default WordPress installation seems a bit over the edge to me. I don’t have a specific argument, it just feels disproportional to me. I see the following options now:

    1. Use MailPoet within WordPress and live with the complexity. I guess there is no way to keep the amount of database tables smaller, is there?
    2. Create a second wordpress instance and install MailPoet in it. Find a way to synchronize the posts between the two WordPress instances.
    3. Use an external service and copy the post content into the external editor.

    I know this topic is a bit architectional, but I would be happy to hear any opinions or experiences about it.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hello @janciriack,

    Thanks for writing. We haven’t received many feedback about the size of our database tables. Most users have no problem using MailPoet with their current website. I’ve reached out our development team about your comments.

    Although there are no immediate plans to change our database architecture, our team is always looking for ways to improve our service. If you like to submit comments as a feature request (or see our roadmap) please go here https://feedback.mailpoet.com/

    We would certainly appreciate it.

    ?Thanks,
    Andy

    Thread Starter janc76

    (@janciriack)

    Hi Andy,

    thank you for your response. As I said I don’t have specific feature request or proposal of what to change yet. I rather wanted to reach out if there is an awareness of this issue. To me MailPoet is not like other plugins bringing a small piece of functionality into WordPress. It is more like a standalone application on the same level as WordPress core itself in terms of size.
    Software engineering teaches us to break complex systems down into smaller units respecting principles like seperation of concerns, loose coupling etc. Having MailPoet inside WordPress as it is today might not be a problem for most users, to me it seems like a step towards building a monolitic system.
    My concerns might be theoretic, but mabye it’s worth a second thought. I think I will go with the standard way for now, but also evaluate installing MailPoet inside a it’s own WordPress instance. (above option 2)

    Thank you, Jan

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘MailPoet and modular software systems’ is closed to new replies.