Skip to main content
SpringerLink
Log in

Development Environment and Workflow

  • Chapter
  • First Online:
Microservices From Day One

  • 2089 Accesses

Abstract

Software engineering in a microservices environment requires a specific mindset, as well as tools to make development and deployment simple. Any friction caused by a high number of deployment units will put a damper on overall productivity.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 49.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    A collaboration tool that enables remote pair programming. https://screenhero.com/

  2. 2.

    See Chapter 9 for an explanation of component tests.

  3. 3.

    See “Comparison of open-source configuration management software,” Wikipedia; https://en.wikipedia.org/wiki/Comparison_of_open-source_configuration_management_software

  4. 4.

    See https://github.com/pivotal-sprout for an overview of Pivotal Sprout tools and recipes.

  5. 5.

    Linux containers, a way to virtualize multiple, isolated Linux systems on top of a single Linux host machine. See https://en.wikipedia.org/wiki/LXC

  6. 6.

    For a description of how to set up Pull Request templates in your repository, see https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/ .

  7. 7.

    See http://rspec.info/ , https://cucumber.io , and http://jnicklas.github.io/capybara/ ; more details on how to use these frameworks will be presented in Chapter 9.

  8. 8.

    See https://github.com/thoughtbot/guides/tree/master/style/testing for the full test style guide at Thoughtbot.

  9. 9.

    For a full list of plugins, see https://github.com/guard/guard/wiki/Guard-Plugins

  10. 10.

    See the “Typical Rails app" section at https://github.com/guard/guard-rspec#typical-rails-app

  11. 11.

    Code Climate analysis can be added for free to any open-source project.

  12. 12.

    See the next chapter for further notes on exploratory testing.

  13. 13.

    Chapter 9 offers insights into frameworks for this purpose, such as pacto, in the sections on contract testing.

  14. 14.

    Evan Phoenix, "Microservice Development - Who Runs What Where", April 17, 2016. http://phx.io/posts/microservice-dev/

  15. 15.

    For more details on the Swagger UI, see the "The Swagger User Interface" section in Chapter 5.

  16. 16.

    See Chapters 6 and 9 for more information on the Consul tool.

Author information

Authors and Affiliations

  1. Hollywood, Florida, USA

    Cloves Carneiro Jr.

  2. Broomfield, Colorado, USA

    Tim Schmelmer

Authors
  1. Cloves Carneiro Jr.
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Tim Schmelmer
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Cloves Carneiro Jr. and Tim Schmelmer

About this chapter

Cite this chapter

Carneiro, C., Schmelmer, T. (2016). Development Environment and Workflow. In: Microservices From Day One. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-1937-9_8

Download citation

Publish with us

Policies and ethics

Search

Navigation