• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
A Reasonable Architecture for Your Next Big Idea
 

A Reasonable Architecture for Your Next Big Idea

on

  • 1,179 views

Provides a couple alternatives for business founders who are looking to implement a Software as a Service solution. The context is when a technical founder is not present. The presentation covers ...

Provides a couple alternatives for business founders who are looking to implement a Software as a Service solution. The context is when a technical founder is not present. The presentation covers the smart questions and options that usually are not explored on day one when technical resources are outsourced.

Statistics

Views

Total Views
1,179
Views on SlideShare
1,127
Embed Views
52

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 52

http://blog.rgbdaily.com 52

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

CC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    A Reasonable Architecture for Your Next Big Idea A Reasonable Architecture for Your Next Big Idea Presentation Transcript

    • A Reasonable Architecture for Your Next Big Idea
    • Our Context
      • Sole proprietor
      • Limited capital
      • Limited technical resources
      • SaaS application
        • Online
        • End Users
        • This is all about version 0.1
    • Which Mark are You?
      • Are you a master salesman or a coding warrior?
      • Which is more valuable starting out?
      • What impact does social media have on business and technical roles?
    • The Value of Ideas
      • What generates value?
      • Results require execution.
      • What do you need to move from an idea to results?
    • So let's just start coding!
    • Which do you want?
    • Software Planning
      • Is the goal to build a prototype or launch a business?
      • Be ready for success
      • Temper duck tape immediacy with pragmatic planning
      • Today's latest technologies and solutions are scalable, solid and sexy; take the time to learn
      • Nailing the right solution will require effort
    • Why does architecture matter at the start?
    • A launch before social media
    • How will your users and clients find you?
    • In a post social media world success comes fast.
    • Success Requires Scale
    • Scaling Technical Resources
      • Human
        • CTO
        • Architects
        • Developers
        • QA
        • Operational Staff
      • At the start one person may be covering many of these roles.
      • Assets
        • Distributed Clients
        • Web front ends
        • APIs and Services
        • Application Servers
        • Structured Data Stores
        • Big Data
    • Your technical partner
      • Is your first developer CTO caliber?
      • Do you start with a team of consultants?
      • Who determines the architecture for your next big idea?
      • Who protects the future?
    • What about the Cloud?
      • The cloud can help
      • The cloud is composed of layers
        • SaaS
        • PaaS
        • IaaS
      • Which layer is appropriate for a lean startup?
    • PaaS with low latency IaaS
      • Amazon is still the best for across price / performance
      • Scalr on AWS is a flexible PaaS platform
      • Rackspace has the best LAMP PaaS
      • Engineyard is solid for Ruby
      • PaaS pure plays
        • Google App Engine
          • Cumbersome extensions
        • Heroku
          • Extensible third party API model
          • Adhoc service integration still cumbersome
    • Which language?
      • Understand the needs of your application/service
      • Is the service web scale along any significant dimensions?
      • Invest in Java early.
    • PHP (LAMP)
      • PHP is by far the easiest to find resources for
      • Most people in operational folks have experience scaling LAMP hands on
      • Dev resources up and down the talent stack
      • Use a mature framework like Kohana or CakePHP for the actual software development
      • Long running daemons are harder to write in PHP, you'll need a backup (Python or Java)
    • Ruby
      • Ruby is powerful and the PaaS solutions are advancing the fastest
      • Rails is the de-facto architecture
      • JRuby and Java make a powerful pair for implementing backend services
    • What about big data?
      • Store images and unstructured data in AWS S3
      • If fully committed to Rackspace, go with Cloudfiles
      • That's it
    • And structured data?
      • MongoDB is becoming the MySQL of Web 3.0
        • Backed by a real company (10gen)
        • Has built in automatic sharding
        • Powerful queries
        • BSON – Binary Javascript Object Notation == Universal
      • Membase
        • Covers memcache use case
        • Auto scaling
        • Simple and easy integration
    • What to build and when?
      • Backend services
      • Web site
      • Public APIs
      • Mobile Web
      • Outsource native mobile clients
      • Twitter and Facebook both followed this rough model
    • Bring It
    • How to reach me
      • Travell Perkins
      • Founder / CEO
      • www.rgbdaily.com
      • @travellperkins
      • [email_address]